[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250226151529.GA2338510-robh@kernel.org>
Date: Wed, 26 Feb 2025 09:15:29 -0600
From: Rob Herring <robh@...nel.org>
To: Svyatoslav Ryhel <clamor95@...il.com>
Cc: Krzysztof Kozlowski <krzk@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
Peter De Schrijver <pdeschrijver@...dia.com>,
Prashant Gaikwad <pgaikwad@...dia.com>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Georgi Djakov <djakov@...nel.org>,
Dmitry Osipenko <digetx@...il.com>, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-tegra@...r.kernel.org,
linux-clk@...r.kernel.org
Subject: Re: [PATCH v1 6/9] dt-bindings: memory: Document Tegra114 External
Memory Controller
On Tue, Feb 25, 2025 at 04:34:58PM +0200, Svyatoslav Ryhel wrote:
> Document External Memory Controller found in the Tegra 4 SoC.
This all looks very close to tegra124. Could have missed something, but
I see 1 property difference and 'nvidia,emc-configuration' is slightly
different. I'd just add tegra114 to the existing schema. For
'nvidia,emc-configuration', I would just list the range for the length.
It's just a list of magic register values, so we can't really do any
validation of it. And I don't care what register is which entry. If you
really want to document that, then keep the existing list and put 0
value entries for any registers that don't exist on tegra114 and put new
registers on the end of the list.
>
> Signed-off-by: Svyatoslav Ryhel <clamor95@...il.com>
> ---
> .../nvidia,tegra114-emc.yaml | 431 ++++++++++++++++++
> 1 file changed, 431 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra114-emc.yaml
Powered by blists - more mailing lists