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 v9 2/4] i2c: tegra: Move variant to tegra_i2c_hw_feature
Date: Wed, 28 Jan 2026 23:17:10 +0100 [thread overview]
Message-ID: <aXqKnm3yR5G1I0Ut@zenone.zhora.eu> (raw)
In-Reply-To: <e0d498a4-ddfe-40b3-af45-f07d2c5c2e62@nvidia.com>
Hi Kartik,
> > > @@ -280,7 +282,6 @@ struct tegra_i2c_hw_feature {
> > > * @base_phys: physical base address of the I2C controller
> > > * @cont_id: I2C controller ID, used for packet header
> > > * @irq: IRQ number of transfer complete interrupt
> > > - * @variant: This represents the I2C controller variant.
> > > * @msg_complete: transfer completion notifier
> > > * @msg_buf_remaining: size of unsent data in the message buffer
> > > * @msg_len: length of message in current transfer
> > > @@ -332,13 +333,12 @@ struct tegra_i2c_dev {
> > > bool atomic_mode;
> > > bool dma_mode;
> > > bool msg_read;
> > > - enum tegra_i2c_variant variant;
> > > };
> > >
> > > #define IS_DVC(dev) (IS_ENABLED(CONFIG_ARCH_TEGRA_2x_SOC) && \
> > > - (dev)->variant == TEGRA_I2C_VARIANT_DVC)
> > > + (dev)->hw->variant == TEGRA_I2C_VARIANT_DVC)
> > > #define IS_VI(dev) (IS_ENABLED(CONFIG_ARCH_TEGRA_210_SOC) && \
> > > - (dev)->variant == TEGRA_I2C_VARIANT_VI)
> > > + (dev)->hw->variant == TEGRA_I2C_VARIANT_VI)
> > >
> > > static void dvc_writel(struct tegra_i2c_dev *i2c_dev, u32 val,
> > > unsigned int reg)
> > > @@ -1647,8 +1647,42 @@ static const struct tegra_i2c_hw_feature tegra20_i2c_hw = {
> > > .has_interface_timing_reg = false,
> > > .enable_hs_mode_support = false,
> > > .has_mutex = false,
> > > + .variant = TEGRA_I2C_VARIANT_DEFAULT,
> > > };
> >
> > in v8 I made a question at this point, could you please answer?
...
> Are you referring to the following question on v7 of this series, which I've already addressed?
> https://lore.kernel.org/linux-tegra/c3cdece5-1bf6-46eb-a668-2ee2a4358a88@nvidia.com/#t
I'm sorry, what have you addressed. It doesn't look addressed to
me. In the same series, I want to avoid adding something in one
patch and removing it in the next. It just adds noise.
Andi
next prev parent reply other threads:[~2026-01-28 22:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 15:30 [PATCH v9 0/4] Add I2C support for Tegra410 Kartik Rajput
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 [this message]
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=aXqKnm3yR5G1I0Ut@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®