From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Sergiu.Moga@microchip.com, robh+dt@kernel.org,
Nicolas.Ferre@microchip.com, alexandre.belloni@bootlin.com,
Claudiu.Beznea@microchip.com
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH 3/3] dt-bindings: i2c: at91: Add SAMA7G5 compatible strings list
Date: Thu, 10 Mar 2022 12:05:09 +0100 [thread overview]
Message-ID: <2b271ddf-d054-522f-7897-cd842e935823@canonical.com> (raw)
In-Reply-To: <8f4cc7ad-6ce2-2c78-dab4-759d05761a64@microchip.com>
On 10/03/2022 11:42, Sergiu.Moga@microchip.com wrote:
> On 10.03.2022 09:22, Krzysztof Kozlowski wrote:
>> On 09/03/2022 13:07, Sergiu Moga wrote:
>>> Add compatible strings list for SAMA7G5.
>>>
>>> Signed-off-by: Sergiu Moga <sergiu.moga@microchip.com>
>>> ---
>>> .../bindings/i2c/atmel,at91sam-i2c.yaml | 38 ++++++++++++-------
>>> 1 file changed, 24 insertions(+), 14 deletions(-)
>>>
>>> diff --git a/Documentation/devicetree/bindings/i2c/atmel,at91sam-i2c.yaml b/Documentation/devicetree/bindings/i2c/atmel,at91sam-i2c.yaml
>>> index d4aadbbd1a11..661a679b98cf 100644
>>> --- a/Documentation/devicetree/bindings/i2c/atmel,at91sam-i2c.yaml
>>> +++ b/Documentation/devicetree/bindings/i2c/atmel,at91sam-i2c.yaml
>>> @@ -16,10 +16,15 @@ allOf:
>>> properties:
>>> compatible:
>>> contains:
>>> - enum:
>>> - - atmel,sama5d4-i2c
>>> - - atmel,sama5d2-i2c
>>> - - microchip,sam9x60-i2c
>>> + oneOf:
>>> + - items:
>>> + - enum:
>>> + - atmel,sama5d4-i2c
>>> + - atmel,sama5d2-i2c
>>> + - microchip,sam9x60-i2c
>>> + - items:
>>> + - const: microchip,sama7g5-i2c
>>> + - const: microchip,sam9x60-i2c
>> This looks not needed, because it contains microchip,sam9x60-i2c which
>> is mentioned earlier.
>>
> Hmm, I might have misunderstood the functionality. I thought it would be
> stricter, having to match all the strings of that compatible. I guess
> something like this should be enough then?
> oneOf:
> - enum:
> - atmel,sama5d4-i2c
> - atmel,sama5d2-i2c
> - microchip,sam9x60-i2c
> - microchip,sama7g5-i2
>
> Just adding the sama7g5 compatible seems to pass the check on my end.
Yes, that is also a good solution.
Best regards,
Krzysztof
prev parent reply other threads:[~2022-03-10 11:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 12:07 [PATCH 0/3] dt-bindings: i2c: convert i2c-at91 to json-schema Sergiu Moga
2022-03-09 12:07 ` [PATCH 1/3] ARM: dts: at91: sama7g5: Swap `rx` and `tx` for `i2c` nodes Sergiu Moga
2022-03-09 13:11 ` Tudor.Ambarus
2022-03-09 12:07 ` [PATCH 2/3] dt-bindings: i2c: convert i2c-at91 to json-schema Sergiu Moga
2022-03-09 22:20 ` Rob Herring
2022-03-10 7:21 ` Krzysztof Kozlowski
2022-03-10 10:33 ` Sergiu.Moga
2022-03-09 12:07 ` [PATCH 3/3] dt-bindings: i2c: at91: Add SAMA7G5 compatible strings list Sergiu Moga
2022-03-10 7:22 ` Krzysztof Kozlowski
2022-03-10 10:42 ` Sergiu.Moga
2022-03-10 11:05 ` Krzysztof Kozlowski [this message]
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=2b271ddf-d054-522f-7897-cd842e935823@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Sergiu.Moga@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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