From: Krzysztof Kozlowski <krzk@kernel.org>
To: Charan.Pedumuru@microchip.com
Cc: lee@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, Nicolas.Ferre@microchip.com,
alexandre.belloni@bootlin.com, claudiu.beznea@tuxon.dev,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: mfd: atmel,at91sam9260: Convert to json schema
Date: Tue, 17 Dec 2024 06:31:23 +0100 [thread overview]
Message-ID: <4e4e8a02-5fc1-4b90-ad9d-9f9ec5c8bc61@kernel.org> (raw)
In-Reply-To: <92579055-5a46-4f20-b579-123188554a03@microchip.com>
On 17/12/2024 06:00, Charan.Pedumuru@microchip.com wrote:
>>
>>> + - items:
>>> + - enum:
>>> + - atmel,at91sam9260-matrix
>>> + - atmel,at91sam9261-matrix
>>> + - atmel,at91sam9263-matrix
>>> + - atmel,at91sam9rl-matrix
>>> + - atmel,at91sam9g45-matrix
>>> + - atmel,at91sam9n12-matrix
>>> + - atmel,at91sam9x5-matrix
>>> + - atmel,sama5d3-matrix
>>> + - const: syscon
>>> + - items:
>>> + - const: microchip,sam9x60-matrix
>>> + - const: atmel,at91sam9x5-matrix
>>> + - const: syscon
>>> + - items:
>>> + - const: microchip,sam9x7-matrix
>> So that's just enum with previous group.
>
> Yes, as both boards have 2 compatibles one after another, I defined them
> as two different groups to resolve dt_check warnings.
My comment stands. I understand your "Yes" means you will fix it.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-12-17 5:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 11:29 [PATCH] dt-bindings: mfd: atmel,at91sam9260: Convert to json schema Charan Pedumuru
2024-12-16 10:14 ` Krzysztof Kozlowski
2024-12-17 5:00 ` Charan.Pedumuru
2024-12-17 5:31 ` Krzysztof Kozlowski [this message]
2024-12-17 6:44 ` Charan.Pedumuru
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=4e4e8a02-5fc1-4b90-ad9d-9f9ec5c8bc61@kernel.org \
--to=krzk@kernel.org \
--cc=Charan.Pedumuru@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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