From: Andi Shyti <andi.shyti@kernel.org>
To: Kartik Rajput <kkartik@nvidia.com>
Cc: ldewangan@nvidia.com, digetx@gmail.com, 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
Subject: Re: [PATCH v7 0/4] Add I2C support for Tegra410
Date: Wed, 21 Jan 2026 10:04:16 +0100 [thread overview]
Message-ID: <aXCWCYR-DRF9urhl@zenone.zhora.eu> (raw)
In-Reply-To: <20260113165929.43888-1-kkartik@nvidia.com>
Hi,
On Tue, Jan 13, 2026 at 10:29:25PM +0530, Kartik Rajput wrote:
> 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
Can I have someone from nVidia acking on this series? Laxman?
Dmitry?
Thanks,
Andi
next prev parent reply other threads:[~2026-01-21 9:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 16:59 [PATCH v7 0/4] Add I2C support for Tegra410 Kartik Rajput
2026-01-13 16:59 ` [PATCH v7 1/4] i2c: tegra: Introduce tegra_i2c_variant to identify DVC and VI Kartik Rajput
2026-01-21 9:00 ` Andi Shyti
2026-01-21 9:11 ` Kartik Rajput
2026-01-13 16:59 ` [PATCH v7 2/4] i2c: tegra: Move variant to tegra_i2c_hw_feature Kartik Rajput
2026-01-13 16:59 ` [PATCH v7 3/4] i2c: tegra: Add logic to support different register offsets Kartik Rajput
2026-01-19 21:01 ` Jon Hunter
2026-01-20 5:25 ` Kartik Rajput
2026-01-13 16:59 ` [PATCH v7 4/4] i2c: tegra: Add support for Tegra410 Kartik Rajput
2026-01-21 9:04 ` Andi Shyti [this message]
2026-01-21 14:40 ` [PATCH v7 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=aXCWCYR-DRF9urhl@zenone.zhora.eu \
--to=andi.shyti@kernel.org \
--cc=akhilrajeev@nvidia.com \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kkartik@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.