From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Peter Rosin <peda@axentia.se>, Andi Shyti <andi.shyti@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Doug Anderson <dianders@chromium.org>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: i2c: arb-gpio-challange: convert to DT schema
Date: Sun, 23 Jul 2023 08:50:09 +0200 [thread overview]
Message-ID: <7ad1f01a-4307-fdba-c79c-8a21c234f8b0@linaro.org> (raw)
In-Reply-To: <9e900507-bdc3-21af-4ee0-017c193d5c8c@axentia.se>
On 22/07/2023 12:50, Peter Rosin wrote:
>> + their-claim-gpios:
>> + minItems: 1
>> + maxItems: 2
>
> I don't think there should be a max here? There is no reason for not
> supporting more than 2 other masters. True, the current Linux driver
> happens to only support 1 other master. So if there should be a max,
> I guess it should be 1? But that feels like an implementation
> detail of the driver. The Linux driver bails out with an error if
> there are more than one other master, it's the only thing it does
> with that 2nd 'their-claim-goios' ref.
I will make it some higher number.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-07-23 6:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 9:57 [PATCH 1/2] dt-bindings: i2c: nxp,pca9541: convert to DT schema Krzysztof Kozlowski
2023-07-22 9:57 ` [PATCH 2/2] dt-bindings: i2c: arb-gpio-challange: " Krzysztof Kozlowski
2023-07-22 10:50 ` Peter Rosin
2023-07-23 6:50 ` Krzysztof Kozlowski [this message]
2023-07-22 12:07 ` Conor Dooley
2023-07-22 9:58 ` [PATCH 1/2] dt-bindings: i2c: nxp,pca9541: " Krzysztof Kozlowski
2023-07-22 10:50 ` Peter Rosin
2023-07-22 12:02 ` Conor Dooley
2023-07-23 20:23 ` 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=7ad1f01a-4307-fdba-c79c-8a21c234f8b0@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).