From: Kartik Rajput <kkartik@nvidia.com>
To: Andi Shyti <andi.shyti@kernel.org>
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 1/4] i2c: tegra: Introduce tegra_i2c_variant to identify DVC and VI
Date: Wed, 21 Jan 2026 14:41:00 +0530 [thread overview]
Message-ID: <c3cdece5-1bf6-46eb-a668-2ee2a4358a88@nvidia.com> (raw)
In-Reply-To: <aXCVSqvkK5PW55t9@zenone.zhora.eu>
Hi Andi,
Thanks for reviewing the patch!
On 21/01/26 14:30, Andi Shyti wrote:
> External email: Use caution opening links or attachments
>
>
> Hi Kartik,
>
> ...
>
>> @@ -323,12 +334,13 @@ struct tegra_i2c_dev {
>> bool atomic_mode;
>> bool dma_mode;
>> bool msg_read;
>> - bool is_dvc;
>> - bool is_vi;
>> + enum tegra_i2c_variant variant;
>
> why do we need this extra step in this patch and we don't add
> "variant" directly in tegra_i2c_dev->hw?
>
Since we are also introducing match data for DVC and VI variant, I
decided to split this into two patches.
If you prefer, I can squash following into a single patch:
* "i2c: tegra: Introduce tegra_i2c_variant to identify DVC and VI"
* "i2c: tegra: Move variant to tegra_i2c_hw_feature"
Thanks,
Kartik
next prev parent reply other threads:[~2026-01-21 9:12 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 [this message]
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 ` [PATCH v7 0/4] Add I2C " Andi Shyti
2026-01-21 14:40 ` 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=c3cdece5-1bf6-46eb-a668-2ee2a4358a88@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