lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <06bc4b6b-e758-4e38-9520-c373646c7360@nvidia.com>
Date: Wed, 21 Jan 2026 14:31:43 +0000
From: Jon Hunter <jonathanh@...dia.com>
To: Kartik Rajput <kkartik@...dia.com>, ldewangan@...dia.com,
 digetx@...il.com, andi.shyti@...nel.org, thierry.reding@...il.com,
 akhilrajeev@...dia.com, smangipudi@...dia.com, linux-i2c@...r.kernel.org,
 linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v8 0/4] Add I2C support for Tegra410



On 20/01/2026 09:20, 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.
> 
> Kartik Rajput (4):
>    i2c: tegra: Introduce tegra_i2c_variant to identify DVC and VI
>    i2c: tegra: Move variant to tegra_i2c_hw_feature
>    i2c: tegra: Add logic to support different register offsets
>    i2c: tegra: Add support for Tegra410
> 
>   drivers/i2c/busses/i2c-tegra.c | 557 ++++++++++++++++++++++++---------
>   1 file changed, 401 insertions(+), 156 deletions(-)
> 

Series looks good to me in general. Unfortunately the commit message in 
3/4 is still not correct and now makes me wonder if we should even mess 
with the tegra_dvc_init() function?

Jon

-- 
nvpublic


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ