From: <Varshini.Rajendran@microchip.com>
To: <robh@kernel.org>
Cc: <krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
<claudiu.beznea@microchip.com>, <Jerry.Ray@microchip.com>,
<Durai.ManickamKR@microchip.com>, <andrew@lunn.ch>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 49/50] dt-bindings: arm: add sam9x75 curiosity board
Date: Thu, 10 Aug 2023 05:59:25 +0000 [thread overview]
Message-ID: <82521b46-11b9-e62d-7d29-1a68f9de6f89@microchip.com> (raw)
In-Reply-To: <20230728192532.GA1169417-robh@kernel.org>
On 29/07/23 12:55 am, Rob Herring wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Fri, Jul 28, 2023 at 04:01:06PM +0530, Varshini Rajendran wrote:
>> Add documentation for SAM9X75 Curiosity board.
>>
>> Signed-off-by: Varshini Rajendran <varshini.rajendran@microchip.com>
>> ---
>> Documentation/devicetree/bindings/arm/atmel-at91.yaml | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/atmel-at91.yaml b/Documentation/devicetree/bindings/arm/atmel-at91.yaml
>> index dfb8fd089197..15b11feae46a 100644
>> --- a/Documentation/devicetree/bindings/arm/atmel-at91.yaml
>> +++ b/Documentation/devicetree/bindings/arm/atmel-at91.yaml
>> @@ -99,6 +99,12 @@ properties:
>> - const: microchip,sam9x60
>> - const: atmel,at91sam9
>>
>> + - description: Microchip SAM9X7 Evaluation Boards
>> + items:
>> + - const: microchip,sam9x75-curiosity
>> + - const: microchip,sam9x7
>> + - const: atmel,at91sam9
>
> Has this compatible been useful in prior use? Can s/w make some decision
> based on it? If not, I'd drop it.
Hi Rob,
There is no s/w decision depending on this compatible per se. But this
is how we have maintained different boards from the same SoC or SoC
family so far. So I would say, any decision on this would require
discussion internally.
>
> Rob
--
Thanks and Regards,
Varshini Rajendran.
prev parent reply other threads:[~2023-08-10 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 10:31 [PATCH v3 49/50] dt-bindings: arm: add sam9x75 curiosity board Varshini Rajendran
2023-07-28 19:25 ` Rob Herring
2023-08-10 5:59 ` Varshini.Rajendran [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=82521b46-11b9-e62d-7d29-1a68f9de6f89@microchip.com \
--to=varshini.rajendran@microchip.com \
--cc=Durai.ManickamKR@microchip.com \
--cc=Jerry.Ray@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.beznea@microchip.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.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;
as well as URLs for NNTP newsgroup(s).