From: Krzysztof Kozlowski <krzk@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] memory: tegra: Add Tegra264 support
Date: Wed, 9 Jul 2025 20:18:01 +0200 [thread overview]
Message-ID: <c80bf310-8cee-4a44-8e01-472bfee1933f@kernel.org> (raw)
In-Reply-To: <dnwxijowryyoaanvzcz4cfkpt2cejx4mnfu772utkt66fdrelk@n2prert7km4y>
On 09/07/2025 14:18, Thierry Reding wrote:
> On Tue, Jul 08, 2025 at 12:52:41PM +0200, Thierry Reding wrote:
>> From: Thierry Reding <treding@nvidia.com>
>>
>> This set of patches extends the DT bindings for the memory controller
>> and external memory controller for Tegra264 and add the necessary DT
>> headers with memory client and stream ID definitions.
>>
>> The driver changes in patch 4 are mostly an extension of existing code
>> and the bulk consists of the memory client table for the new chip as
>> well as the bandwidth manager calculations.
>>
>> Thierry
>>
>> Sumit Gupta (3):
>> dt-bindings: memory: tegra: Add Tegra264 support
>> dt-bindings: memory: tegra: Add Tegra264 definitions
>> memory: tegra: Add Tegra264 MC and EMC support
>>
>> Thierry Reding (1):
>> dt-bindings: memory: tegra: Add Tegra264 stream IDs
>>
>> .../nvidia,tegra186-mc.yaml | 65 +++-
>> drivers/memory/tegra/Makefile | 2 +
>> drivers/memory/tegra/mc.c | 5 +-
>> drivers/memory/tegra/mc.h | 9 +-
>> drivers/memory/tegra/tegra186-emc.c | 5 +-
>> drivers/memory/tegra/tegra186.c | 17 +-
>> drivers/memory/tegra/tegra264-bwmgr.h | 50 +++
>> drivers/memory/tegra/tegra264.c | 313 ++++++++++++++++++
>> include/dt-bindings/memory/nvidia,tegra264.h | 136 ++++++++
>> 9 files changed, 594 insertions(+), 8 deletions(-)
>> create mode 100644 drivers/memory/tegra/tegra264-bwmgr.h
>> create mode 100644 drivers/memory/tegra/tegra264.c
>> create mode 100644 include/dt-bindings/memory/nvidia,tegra264.h
>
> Krzysztof,
>
> There's a dependency between this series and a series adding device tree
> files for Tegra264 (both the driver and DTS files include the memory
> client IDs in dt-bindings/memory/nvidia,tegra264.h), so I think it'd be
> easiest for me to take the driver patches here through the Tegra tree as
> well.
>
> Let me know if that works for you or not.
Works for me. I don't have anything for Tegra memory controllers and
it's close to end of cycle. Let me look at the patches and ack/comment.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-07-09 18:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 10:52 [PATCH 0/4] memory: tegra: Add Tegra264 support Thierry Reding
2025-07-08 10:52 ` [PATCH 1/4] dt-bindings: " Thierry Reding
2025-07-09 18:19 ` Krzysztof Kozlowski
2025-07-09 20:36 ` Thierry Reding
2025-07-10 6:42 ` Krzysztof Kozlowski
2025-07-08 10:52 ` [PATCH 2/4] dt-bindings: memory: tegra: Add Tegra264 definitions Thierry Reding
2025-07-09 18:20 ` Krzysztof Kozlowski
2025-07-09 20:37 ` Thierry Reding
2025-07-08 10:52 ` [PATCH 3/4] dt-bindings: memory: tegra: Add Tegra264 stream IDs Thierry Reding
2025-07-09 18:21 ` Krzysztof Kozlowski
2025-07-09 20:39 ` Thierry Reding
2025-07-08 10:52 ` [PATCH 4/4] memory: tegra: Add Tegra264 MC and EMC support Thierry Reding
2025-07-09 18:23 ` Krzysztof Kozlowski
2025-07-09 12:18 ` [PATCH 0/4] memory: tegra: Add Tegra264 support Thierry Reding
2025-07-09 18:18 ` Krzysztof Kozlowski [this message]
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=c80bf310-8cee-4a44-8e01-472bfee1933f@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).