From: Kartik Rajput <kkartik@nvidia.com>
To: <ldewangan@nvidia.com>, <digetx@gmail.com>,
<andi.shyti@kernel.org>, <thierry.reding@gmail.com>,
<jonathanh@nvidia.com>, <akhilrajeev@nvidia.com>,
<smangipudi@nvidia.com>, <linux-i2c@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Kartik Rajput <kkartik@nvidia.com>
Subject: [PATCH v9 0/4] Add I2C support for Tegra410
Date: Wed, 21 Jan 2026 21:00:07 +0530 [thread overview]
Message-ID: <20260121153012.92243-1-kkartik@nvidia.com> (raw)
Add support for the Tegra410 SoC, which has 4 I2C controllers. The
controllers are feature-equivalent to Tegra264; only the register
offsets differ.
Kartik Rajput (4):
i2c: tegra: Introduce tegra_i2c_variant to identify DVC and VI
i2c: tegra: Move variant to tegra_i2c_hw_feature
i2c: tegra: Add logic to support different register offsets
i2c: tegra: Add support for Tegra410
drivers/i2c/busses/i2c-tegra.c | 534 ++++++++++++++++++++++++---------
1 file changed, 395 insertions(+), 139 deletions(-)
--
2.43.0
next reply other threads:[~2026-01-21 15:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 15:30 Kartik Rajput [this message]
2026-01-21 15:30 ` [PATCH v9 1/4] i2c: tegra: Introduce tegra_i2c_variant to identify DVC and VI Kartik Rajput
2026-01-21 15:30 ` [PATCH v9 2/4] i2c: tegra: Move variant to tegra_i2c_hw_feature Kartik Rajput
2026-01-22 17:32 ` Andi Shyti
2026-01-22 17:52 ` Kartik Rajput
2026-01-28 22:17 ` Andi Shyti
2026-01-29 5:30 ` Kartik Rajput
2026-01-21 15:30 ` [PATCH v9 3/4] i2c: tegra: Add logic to support different register offsets Kartik Rajput
2026-01-21 15:30 ` [PATCH v9 4/4] i2c: tegra: Add support for Tegra410 Kartik Rajput
2026-01-21 19:19 ` [PATCH v9 0/4] Add I2C " Jon Hunter
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=20260121153012.92243-1-kkartik@nvidia.com \
--to=kkartik@nvidia.com \
--cc=akhilrajeev@nvidia.com \
--cc=andi.shyti@kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=smangipudi@nvidia.com \
--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