From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bastien Curutchet <bastien.curutchet@bootlin.com>,
Peter Rosin <peda@axentia.se>, Andi Shyti <andi.shyti@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Peter Korsgaard <peter.korsgaard@barco.com>,
Wolfram Sang <wsa@kernel.org>
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
herve.codina@bootlin.com, christophercordahi@nanometrics.ca
Subject: Re: [PATCH 1/3] dt-bindings: i2c: gpio: Add 'transition-delay-ms' property
Date: Tue, 28 May 2024 09:49:04 +0200 [thread overview]
Message-ID: <23be345b-1c5b-4c34-aa08-e81897c90ebf@kernel.org> (raw)
In-Reply-To: <1cfef2c3-3b24-469d-b55a-377f2d42756b@bootlin.com>
On 28/05/2024 08:59, Bastien Curutchet wrote:
>
>> So just like RC binding, that's not a property of I2C mux. Maybe this
>> fits usage of GPIO RC / delay binding.
>>
>
> IMHO that’s more of a MUX property than an RC binding because every MUX
> needs some time to switch from one bus to another. It’s just that for
> the vast majority of MUXes, this time is so small that it doesn’t need
> to be described.
Hm, true, it's fine then.
However this probably should be microseconds not milliseconds to allow
greater granularity, just like gpio-delay.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-05-28 7:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 11:39 [PATCH 0/3] i2c: mux: gpio: Add 'transition-delay-ms' property Bastien Curutchet
2024-05-27 11:39 ` [PATCH 1/3] dt-bindings: i2c: " Bastien Curutchet
2024-05-27 14:38 ` Krzysztof Kozlowski
2024-05-28 6:59 ` Bastien Curutchet
2024-05-28 7:49 ` Krzysztof Kozlowski [this message]
2024-05-27 11:39 ` [PATCH 2/3] i2c: mux: gpio: Re-order #include to match alphabetic order Bastien Curutchet
2024-05-27 11:39 ` [PATCH 3/3] i2c: mux: gpio: Add support for the 'transition-delay-ms' property Bastien Curutchet
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=23be345b-1c5b-4c34-aa08-e81897c90ebf@kernel.org \
--to=krzk@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=bastien.curutchet@bootlin.com \
--cc=christophercordahi@nanometrics.ca \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=herve.codina@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=peter.korsgaard@barco.com \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wsa@kernel.org \
/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