From: Thierry Reding <thierry.reding@gmail.com>
To: Kartik Rajput <kkartik@nvidia.com>
Cc: ldewangan@nvidia.com, digetx@gmail.com, andi.shyti@kernel.org,
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 v10 RESEND 3/3] i2c: tegra: Add support for Tegra410
Date: Fri, 27 Mar 2026 15:16:11 +0100 [thread overview]
Message-ID: <acaRImyfWsNZfkkY@orome> (raw)
In-Reply-To: <20260324055843.549808-4-kkartik@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
On Tue, Mar 24, 2026 at 11:28:43AM +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.
>
> Signed-off-by: Kartik Rajput <kkartik@nvidia.com>
> Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
> Tested-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> Changes in v3:
> * Updated timing parameters for Tegra410.
> ---
> drivers/i2c/busses/i2c-tegra.c | 63 ++++++++++++++++++++++++++++++++++
> 1 file changed, 63 insertions(+)
Acked-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-03-27 14:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 5:58 [PATCH v10 RESEND 0/3] Add I2C support for Tegra410 Kartik Rajput
2026-03-24 5:58 ` [PATCH v10 RESEND 1/3] i2c: tegra: Introduce tegra_i2c_variant to identify DVC and VI Kartik Rajput
2026-03-27 14:15 ` Thierry Reding
2026-03-24 5:58 ` [PATCH v10 RESEND 2/3] i2c: tegra: Add logic to support different register offsets Kartik Rajput
2026-03-27 14:15 ` Thierry Reding
2026-03-24 5:58 ` [PATCH v10 RESEND 3/3] i2c: tegra: Add support for Tegra410 Kartik Rajput
2026-03-27 14:16 ` Thierry Reding [this message]
2026-03-26 22:46 ` [PATCH v10 RESEND 0/3] Add I2C " Andi Shyti
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=acaRImyfWsNZfkkY@orome \
--to=thierry.reding@gmail.com \
--cc=akhilrajeev@nvidia.com \
--cc=andi.shyti@kernel.org \
--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 \
/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.