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 2/3] i2c: tegra: Add logic to support different register offsets
Date: Fri, 27 Mar 2026 15:15:57 +0100 [thread overview]
Message-ID: <acaRFEjSEJsQ86iT@orome> (raw)
In-Reply-To: <20260324055843.549808-3-kkartik@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1584 bytes --]
On Tue, Mar 24, 2026 at 11:28:42AM +0530, Kartik Rajput wrote:
> Tegra410 use different offsets for existing I2C registers, update
> the logic to use appropriate offsets per SoC.
>
> As the register offsets are now defined in the SoC-specific
> tegra_i2c_regs structures, the tegra_i2c_reg_addr() function is no
> longer needed to translate register offsets and has been removed.
>
> Signed-off-by: Kartik Rajput <kkartik@nvidia.com>
> Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
> Tested-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> Changes in v9:
> * Do not remove dvc_writel() and dvc_readl() calls.
> Changes in v8:
> * Replace usage of dvc_writel() with writel_relaxed().
> * Remove dvc_writel().
> Changes in v7:
> * Fix Tegra256 reg offsets, change it to tegra264_i2c_regs as it
> supports SW mutex.
> Changes in v6:
> * Do not remove dvc_writel().
> * Keep DVC registers defined as a macro.
> * Correct Tegra20 DVC register offsets.
> * Remove sl_cnfg, sl_addr1 and sl_addr2 registers for DVC and VI
> as they are not used.
> Changes in v2:
> * Replace individual is_dvc and is_vi flags with an I2C variant.
> * Add tegra20_dvc_i2c_hw and tegra210_vi_i2c_hw in a separate
> patch.
> * Use calculated offsets for tegra20_dvc_i2c_regs and
> tegra210_vi_i2c_regs.
> * Initialize registers only if they are used on the given SoC.
> ---
> drivers/i2c/busses/i2c-tegra.c | 359 ++++++++++++++++++++++-----------
> 1 file changed, 237 insertions(+), 122 deletions(-)
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 [this message]
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
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=acaRFEjSEJsQ86iT@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.