From: Jerry Ray <jerry.ray@microchip.com>
To: Rob Herring <robh+dt@kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
"Jerry Ray" <jerry.ray@microchip.com>
Subject: [linux][PATCH v2 1/2] dts: arm: Adding docs for SAMA5D3-EDS board
Date: Mon, 22 Aug 2022 13:13:13 -0500 [thread overview]
Message-ID: <20220822181314.8325-1-jerry.ray@microchip.com> (raw)
Adding the SAMA5D3-EDS board from Microchip into the atmel AT91 board
description yaml file.
Signed-off-by: Jerry Ray <jerry.ray@microchip.com>
---
v1->v2:
- Added Device Tree documentation for Microchip SAMA5D3-EDS board
---
Documentation/devicetree/bindings/arm/atmel-at91.yaml | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/atmel-at91.yaml b/Documentation/devicetree/bindings/arm/atmel-at91.yaml
index 08efb259a947..635491aaeb0c 100644
--- a/Documentation/devicetree/bindings/arm/atmel-at91.yaml
+++ b/Documentation/devicetree/bindings/arm/atmel-at91.yaml
@@ -138,6 +138,13 @@ properties:
- const: atmel,at91sam9g20
- const: atmel,at91sam9
+ - description: Microchip SAMA5D3 Ethernet Development System Board
+ items:
+ - const: microchip,sama5d3-eds
+ - const: atmel,sama5d36
+ - const: atmel,sama5d3
+ - const: atmel,sama5
+
- items:
- enum:
- atmel,sama5d31
--
2.17.1
next reply other threads:[~2022-08-22 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 18:13 Jerry Ray [this message]
2022-08-22 18:13 ` [linux][PATCH v2 2/2] dts: arm: at91: Add SAMA5D3-EDS Board Jerry Ray
2022-08-23 7:28 ` Claudiu.Beznea
2022-08-23 11:16 ` Nicolas Ferre
2022-08-25 21:23 ` [linux][PATCH v2 1/2] dts: arm: Adding docs for SAMA5D3-EDS board Rob Herring
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=20220822181314.8325-1-jerry.ray@microchip.com \
--to=jerry.ray@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.com \
--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).