linux-kernel - Re: [RFC PATCH V2 04/12] dt-bindings: misc: tegra-i2c: config settings

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: <hqlckp6hxvxwkkbiagdb5pm4eo5efu55hwuupdal6lojxj2xu5@5zibskqdbdju>
Date: Tue, 2 Jul 2024 12:29:25 +0200
From: Thierry Reding <thierry.reding@...il.com>
To: Rob Herring <robh@...nel.org>
Cc: Krishna Yarlagadda <kyarlagadda@...dia.com>, 
	linux-tegra@...r.kernel.org, devicetree@...r.kernel.org, linux-doc@...r.kernel.org, 
	linux-i2c@...r.kernel.org, linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org, 
	jonathanh@...dia.com, krzk+dt@...nel.org, conor+dt@...nel.org, corbet@....net, 
	andi.shyti@...nel.org, wsa+renesas@...g-engineering.com, ulf.hansson@...aro.org, 
	adrian.hunter@...el.com, digetx@...il.com, ldewangan@...dia.com, mkumard@...dia.com
Subject: Re: [RFC PATCH V2 04/12] dt-bindings: misc: tegra-i2c: config
 settings

On Mon, Jul 01, 2024 at 11:42:27AM GMT, Rob Herring wrote:
> On Mon, Jul 01, 2024 at 08:42:22PM +0530, Krishna Yarlagadda wrote:
> > I2C interface timing registers are configured using config setting
> > framework. List available field properties for Tegra I2C controllers.
> 
> How is I2C bus timing parameters specific to NVIDIA? Just because you 
> have more controls? No. That's no reason to invent a whole new way to 
> specify parameters. Extend what's already there and make it work for 
> anyone.

This may be applicable to a subset of this, and yes, maybe we can find
generalizations for some of these parameters.

However, we're also looking for feedback specifically on these config
nodes that go beyond individual timing parameters. For example in the
case of I2C, how should parameters for different operating modes be
described?

Would you agree with something along the lines provided in this series?
Do you have any better suggestions?

Thanks,
Thierry

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)