From: Rob Herring <robh@kernel.org>
To: Varshini Rajendran <varshini.rajendran@microchip.com>
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: Fri, 28 Jul 2023 13:25:32 -0600 [thread overview]
Message-ID: <20230728192532.GA1169417-robh@kernel.org> (raw)
In-Reply-To: <20230728103106.267793-1-varshini.rajendran@microchip.com>
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.
Rob
next prev parent reply other threads:[~2023-07-28 19:25 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 [this message]
2023-08-10 5:59 ` Varshini.Rajendran
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=20230728192532.GA1169417-robh@kernel.org \
--to=robh@kernel.org \
--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=durai.manickamkr@microchip.com \
--cc=jerry.ray@microchip.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=varshini.rajendran@microchip.com \
/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).