linux-kernel - Re: [PATCH v2 1/3] dt-bindings: i2c: gpio: Add 'transition-delay-us' property

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] [day] [month] [year] [list]

Message-ID: <26e9970c-7dbf-48ac-9832-58bf2952d350@bootlin.com>
Date: Wed, 5 Jun 2024 14:32:35 +0200
From: Bastien Curutchet <bastien.curutchet@...tlin.com>
To: Rob Herring <robh@...nel.org>, Peter Rosin <peda@...ntia.se>
Cc: Andi Shyti <andi.shyti@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, Peter Korsgaard <peter.korsgaard@...co.com>,
 Wolfram Sang <wsa@...nel.org>, linux-i2c@...r.kernel.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
 Herve Codina <herve.codina@...tlin.com>,
 Christopher Cordahi <christophercordahi@...ometrics.ca>
Subject: Re: [PATCH v2 1/3] dt-bindings: i2c: gpio: Add 'transition-delay-us'
 property

Hi Rob, Hi Peter,

On 6/3/24 17:58, Rob Herring wrote:
> On Wed, May 29, 2024 at 02:13:37PM +0200, Peter Rosin wrote:
>> Hi!
>>
>> 2024-05-29 at 11:17, Bastien Curutchet wrote:
>>> I2C MUXes described by the i2c-gpio-mux sometimes need a significant
>>> amount of time to switch from a bus to another. When a new bus is
>>> selected, the first I2C transfer can fail if it occurs too early. There
>>> is no way to describe this transition delay that has to be waited before
>>> starting the first I2C transfer.
>>>
>>> Add a 'transition-delay-us' property that indicates the delay to be
>>> respected before doing the first i2c transfer.
>>
>> The io-channel-mux has a property with very similar intent named
>> settle-time-us [1]. I think we should use the same name here.
>>
>> [1] Documentation/devicetree/bindings/iio/multiplexer/io-channel-mux.yaml
> 
> Agreed. I knew we had something and went looking... I only checked the
> base mux and i2c mux bindings.
> 

Ok I'll do this in V3, thank you.

Best regards
Bastien