From: Sumit Gupta <sumitg@nvidia.com>
To: <treding@nvidia.com>, <jonathanh@nvidia.com>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>
Cc: <tbergstrom@nvidia.com>, <bbasu@nvidia.com>, <sumitg@nvidia.com>
Subject: [PATCH v2 0/8] Support for Tegra264 and Tegra254 in CBB driver
Date: Thu, 3 Jul 2025 16:08:21 +0530 [thread overview]
Message-ID: <20250703103829.1721024-1-sumitg@nvidia.com> (raw)
This patch series adds support for Tegra264 and Tegra254 SoCs in the
Tegra CBB driver. It also includes a fix and some improvements to
make the driver more generic to add new SoC support.
The patches can be applied in sequence. Patch info:
- Patch 1: Fix.
- Patch 2: Change lingo from 'Master/Slave' to 'Initiator/Target'.
- Patch 3 & 4: Improvements.
- Patch 5: New feature for HW lookup.
- Patch 6 & 7: Tegra264 SoC support.
- Patch 8: Tegra254 SoC support.
---
v1[1] -> v2:
- patch 8: change name from GB10 to Tegra254.
- patch 6: added ACK from Krzysztof
Sumit Gupta (8):
soc: tegra: cbb: clear err force register with err status
soc: tegra: cbb: change master-slave to initiator-target
soc: tegra: cbb: make error interrupt enable and status per SoC
soc: tegra: cbb: improve handling for per SoC fabric data
soc: tegra: cbb: support hw lookup to get timed out target address
dt-bindings: arm: tegra: Add NVIDIA Tegra264 CBB 2.0 binding
soc: tegra: cbb: add support for cbb fabrics in Tegra264
soc: tegra: cbb: add support for cbb fabrics in T254
.../arm/tegra/nvidia,tegra234-cbb.yaml | 4 +
drivers/soc/tegra/cbb/tegra194-cbb.c | 34 +-
drivers/soc/tegra/cbb/tegra234-cbb.c | 758 ++++++++++++++----
3 files changed, 606 insertions(+), 190 deletions(-)
[1] https://lore.kernel.org/lkml/20250530133336.1419971-1-sumitg@nvidia.com/
--
2.34.1
next reply other threads:[~2025-07-03 10:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 10:38 Sumit Gupta [this message]
2025-07-03 10:38 ` [PATCH v2 1/8] soc: tegra: cbb: clear err force register with err status Sumit Gupta
2025-07-03 10:38 ` [PATCH v2 2/8] soc: tegra: cbb: change master-slave to initiator-target Sumit Gupta
2025-07-03 10:38 ` [PATCH v2 3/8] soc: tegra: cbb: make error interrupt enable and status per SoC Sumit Gupta
2025-07-03 10:38 ` [PATCH v2 4/8] soc: tegra: cbb: improve handling for per SoC fabric data Sumit Gupta
2025-07-03 10:38 ` [PATCH v2 5/8] soc: tegra: cbb: support hw lookup to get timed out target address Sumit Gupta
2025-07-03 10:38 ` [PATCH v2 6/8] dt-bindings: arm: tegra: Add NVIDIA Tegra264 CBB 2.0 binding Sumit Gupta
2025-07-03 10:38 ` [PATCH v2 7/8] soc: tegra: cbb: add support for cbb fabrics in Tegra264 Sumit Gupta
2025-07-03 10:38 ` [PATCH v2 8/8] soc: tegra: cbb: add support for cbb fabrics in Tegra254 Sumit Gupta
2025-07-09 12:31 ` [PATCH v2 0/8] Support for Tegra264 and Tegra254 in CBB driver Thierry Reding
2025-07-24 17:28 ` Rob Herring
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=20250703103829.1721024-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+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tbergstrom@nvidia.com \
--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;
as well as URLs for NNTP newsgroup(s).