From: Jon Hunter <jonathanh@nvidia.com>
To: Kartik Rajput <kkartik@nvidia.com>,
ldewangan@nvidia.com, digetx@gmail.com, andi.shyti@kernel.org,
thierry.reding@gmail.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 v4 2/4] i2c: tegra: Move variant to tegra_i2c_hw_feature
Date: Wed, 7 Jan 2026 09:37:28 +0000 [thread overview]
Message-ID: <ee422fec-d9a4-4c0d-9c42-433f06104ac0@nvidia.com> (raw)
In-Reply-To: <20260107042434.10587-3-kkartik@nvidia.com>
On 07/01/2026 04:24, Kartik Rajput wrote:
> Move the variant field into tegra_i2c_hw_feature and populate it for all
> SoCs. Add dedicated SoC data for "nvidia,tegra20-i2c-dvc" and
> "nvidia,tegra210-i2c-vi" compatibles. Drop the compatible-string checks
> from tegra_i2c_parse_dt to initialize the Tegra I2C variant. Also remove
> the redundant config checks from IS_VI and IS_DVC macros.
Thanks for updating, but now you need to drop the last line in the
commit message because this is no longer relevant.
Jon
--
nvpublic
next prev parent reply other threads:[~2026-01-07 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 4:24 [PATCH v4 0/4] Add I2C support for Tegra410 Kartik Rajput
2026-01-07 4:24 ` [PATCH v4 1/4] i2c: tegra: Introduce tegra_i2c_variant to identify DVC and VI Kartik Rajput
2026-01-07 4:24 ` [PATCH v4 2/4] i2c: tegra: Move variant to tegra_i2c_hw_feature Kartik Rajput
2026-01-07 9:37 ` Jon Hunter [this message]
2026-01-07 9:39 ` Kartik Rajput
2026-01-07 4:24 ` [PATCH v4 3/4] i2c: tegra: Add logic to support different register offsets Kartik Rajput
2026-01-07 4:24 ` [PATCH v4 4/4] i2c: tegra: Add support for Tegra410 Kartik Rajput
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=ee422fec-d9a4-4c0d-9c42-433f06104ac0@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=akhilrajeev@nvidia.com \
--cc=andi.shyti@kernel.org \
--cc=digetx@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox