U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: "Scholz, Kevin" <k-scholz@ti.com>,
	Neha Malcom Francis <n-francis@ti.com>
Cc: Francesco Dolcini <francesco@dolcini.it>,
	Franz Schnyder <fra.schnyder@gmail.com>,
	"trini@konsulko.com" <trini@konsulko.com>,
	"K, Santhosh Kumar" <s-k6@ti.com>, "Brattlof, Bryan" <bb@ti.com>,
	"Chawdhry, Manorit" <m-chawdhry@ti.com>,
	"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
	"Kumar, Udit" <u-kumar1@ti.com>,
	"Gujulan Elango, Hari Prasath" <gehariprasath@ti.com>
Subject: Re: [EXTERNAL] Re: [PATCH v2 5/7] arm: dts: k3-am69: ddr: Update to v0.12.0 of DDR config tool
Date: Thu, 21 May 2026 08:26:15 +0200	[thread overview]
Message-ID: <20260521062615.GB11963@francesco-nb> (raw)
In-Reply-To: <177934243083.132247.2472290729341549059.b4-reply@b4> <8d4936cd5b16494e9447d5f64d7b8e11@ti.com>

On Wed, May 20, 2026 at 09:52:09PM +0000, Scholz, Kevin wrote:
> Francesco,
> 
> My understanding is that the Aquila board was previously having
> intermittent boot failures, hence the comparison of the TI EVM
> register values vs. the Aquila board register values. My understanding
> is that since then, two unrelated issues were identified resulting in
> the observed behavior, and both have been resolved.

My question has nothing to do with Aquila, I think I was not clear.

> However in general, more than one IO setting can be adequate for a
> given design, and it is also acceptable to have different IO settings
> for different board designs and/or for different DDRSS on the same
> board. 

Again, nothing on my question relates to this. My question was

> > specific configuration for AM69A SK board in which only dram3 has ODT
> > enabled, and dram, dram1 and dram2 not. Is the layout/schematics of
> > DRAM3 different from the others? Why?

Why do dram3 is different from dram, dram1 and dram2 on AM69-SK ? Such a
difference implies that the layout is different, or something else. I am
interested in understand what's the reason.

The question is because I want to understand better the TI design.

On Thu, May 21, 2026 at 11:17:10AM +0530, Neha Malcom Francis wrote:
> On 2026-05-20 21:52:09+00:00, Scholz, Kevin wrote:
> Francesco, hope this justification on the IO settings are satisfactory.

There is no answer to my question.

> Tom, could we pick up this series in that case?

From my point of view you can merge the series. It was like that even
before, I just abused this thread to gather more understanding on the
topic. I see no reason to hold this patch because of this.


Francesco


  parent reply	other threads:[~2026-05-21  6:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03  7:10 [PATCH v2 0/7] ti: j7: Update to v0.12.0 of DDR config tool Neha Malcom Francis
2025-11-03  7:10 ` [PATCH v2 1/7] arm: dts: k3-j7200: ddr: " Neha Malcom Francis
2025-11-03  7:10 ` [PATCH v2 2/7] arm: dts: k3-j721s2: " Neha Malcom Francis
2025-11-03  7:10 ` [PATCH v2 3/7] arm: dts: k3-am68: " Neha Malcom Francis
2025-11-03  7:10 ` [PATCH v2 4/7] arm: dts: k3-j784s4: " Neha Malcom Francis
2025-11-03  7:10 ` [PATCH v2 5/7] arm: dts: k3-am69: " Neha Malcom Francis
2025-11-07 15:44   ` Franz Schnyder
2025-11-10  4:25     ` Neha Malcom Francis
2025-11-20  8:16       ` Francesco Dolcini
2025-11-20 14:23         ` [EXTERNAL] " Scholz, Kevin
2025-11-20 14:48           ` Francesco Dolcini
2026-04-21 10:10             ` Neha Malcom Francis
2026-05-20 21:52               ` Scholz, Kevin
2026-05-21  5:47                 ` Neha Malcom Francis
2026-05-21  6:26                 ` Francesco Dolcini [this message]
2026-06-09  4:25                   ` Kumar, Udit
2025-11-03  7:10 ` [PATCH v2 6/7] arm: dts: k3-j742s2: " Neha Malcom Francis
2025-11-03  7:10 ` [PATCH v2 7/7] doc: ti: k3: Add section for DDR configuration Neha Malcom Francis
2025-11-03 14:35   ` Romain Naour
2026-05-21  5:45     ` Neha Malcom Francis
2026-06-09 19:17 ` [PATCH v2 0/7] ti: j7: Update to v0.12.0 of DDR config tool Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260521062615.GB11963@francesco-nb \
    --to=francesco@dolcini.it \
    --cc=bb@ti.com \
    --cc=fra.schnyder@gmail.com \
    --cc=gehariprasath@ti.com \
    --cc=k-scholz@ti.com \
    --cc=m-chawdhry@ti.com \
    --cc=n-francis@ti.com \
    --cc=s-k6@ti.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=u-kumar1@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox