From: Sumit Gupta <sumitg@nvidia.com>
To: <krzk@kernel.org>, <treding@nvidia.com>, <jonathanh@nvidia.com>,
<robh@kernel.org>, <conor+dt@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<devicetree@vger.kernel.org>
Cc: <bbasu@nvidia.com>, <sumitg@nvidia.com>
Subject: [PATCH v2 0/3] memory: tegra264: Add full set of MC clients
Date: Mon, 18 May 2026 18:13:03 +0530 [thread overview]
Message-ID: <20260518124306.2071481-1-sumitg@nvidia.com> (raw)
Extend the Tegra264 MC dt-bindings header and tegra264_mc_clients[]
table to cover the full set of memory clients exposed by the SoC.
---
v1[1] -> v2:
- patch 1 (new): skip ICC requests if no .bpmp_id or .type.
- patch 2 (new): split dt-bindings into a separate patch.
- patch 3: update commit message to reflect entries sorted by SID
override/security register offsets (same as previous SoCs).
Sumit Gupta (3):
memory: tegra264: Skip clients without bpmp_id or type
dt-bindings: memory: tegra264: Add full set of MC client IDs
memory: tegra264: Add full set of MC clients
drivers/memory/tegra/tegra264.c | 568 +++++++++++++++++--
include/dt-bindings/memory/nvidia,tegra264.h | 287 ++++++++++
2 files changed, 823 insertions(+), 32 deletions(-)
[1] https://lore.kernel.org/lkml/20260515171911.1929868-1-sumitg@nvidia.com/
--
2.34.1
next reply other threads:[~2026-05-18 12:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 12:43 Sumit Gupta [this message]
2026-05-18 12:43 ` [PATCH v2 1/3] memory: tegra264: Skip clients without bpmp_id or type Sumit Gupta
2026-05-18 12:43 ` [PATCH v2 2/3] dt-bindings: memory: tegra264: Add full set of MC client IDs Sumit Gupta
2026-05-18 13:10 ` sashiko-bot
2026-05-18 17:51 ` Sumit Gupta
2026-05-18 12:43 ` [PATCH v2 3/3] memory: tegra264: Add full set of MC clients Sumit Gupta
2026-05-18 13:33 ` sashiko-bot
2026-05-18 18:01 ` Sumit Gupta
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=20260518124306.2071481-1-sumitg@nvidia.com \
--to=sumitg@nvidia.com \
--cc=bbasu@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=treding@nvidia.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