From: Nishanth Menon <nm@ti.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Tero Kristo <kristo@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Suman Anna <s-anna@ti.com>, Sinthu Raja <sinthu.raja@ti.com>,
Hari Nagalla <hnagalla@ti.com>,
Sinthu Raja <sinthu.raja@mistralsolutions.com>,
Jan Kiszka <jan.kiszka@siemens.com>, Nishanth Menon <nm@ti.com>
Subject: [PATCH V2 1/4] dt-bindings: arm: ti: Add missing compatibles for j721e/j7200 evms
Date: Sat, 25 Sep 2021 15:14:27 -0500 [thread overview]
Message-ID: <20210925201430.11678-2-nm@ti.com> (raw)
In-Reply-To: <20210925201430.11678-1-nm@ti.com>
Add compatibles for j721e and j7200 evms to allow for newer platforms
to distinguish themselves.
While doing this, maintain support for older style of description where
the board compatibility was not required.
Signed-off-by: Nishanth Menon <nm@ti.com>
---
Changes in V2:
* Modified such that legacy style of compatibles (of just SoC alone) is
still valid
* Made the capability of providing a board specific compatible as an
alternate scheme
* No longer dependent on rproc cleanup and platforms hosted in
downstream trees remain compatible
V1: https://lore.kernel.org/all/20210915121937.27702-2-nm@ti.com/
Documentation/devicetree/bindings/arm/ti/k3.yaml | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/ti/k3.yaml b/Documentation/devicetree/bindings/arm/ti/k3.yaml
index c5aa362e4026..cefb06424a4a 100644
--- a/Documentation/devicetree/bindings/arm/ti/k3.yaml
+++ b/Documentation/devicetree/bindings/arm/ti/k3.yaml
@@ -28,12 +28,20 @@ properties:
- const: ti,am654
- description: K3 J721E SoC
- items:
+ oneOf:
- const: ti,j721e
+ - items:
+ - enum:
+ - ti,j721e-evm
+ - const: ti,j721e
- description: K3 J7200 SoC
- items:
+ oneOf:
- const: ti,j7200
+ - items:
+ - enum:
+ - ti,j7200-evm
+ - const: ti,j7200
- description: K3 AM642 SoC
items:
--
2.32.0
next prev parent reply other threads:[~2021-09-25 20:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-25 20:14 [PATCH V2 0/4] arm64: dts: ti: k3-j721e/j7200: Introduce EVM compatible Nishanth Menon
2021-09-25 20:14 ` Nishanth Menon [this message]
2021-09-27 14:24 ` [PATCH V2 1/4] dt-bindings: arm: ti: Add missing compatibles for j721e/j7200 evms Suman Anna
2021-10-04 17:52 ` Rob Herring
2021-09-25 20:14 ` [PATCH V2 2/4] dt-bindings: arm: ti: am642/am654: Allow for SoC only compatibles Nishanth Menon
2021-09-27 14:26 ` Suman Anna
2021-10-04 17:54 ` Rob Herring
2021-10-04 18:59 ` Nishanth Menon
2021-10-05 18:31 ` Nishanth Menon
2021-09-25 20:14 ` [PATCH V2 3/4] arm64: dts: ti: k3-j721e-common-proc-board: Add j721e-evm compatible Nishanth Menon
2021-09-27 14:27 ` Suman Anna
2021-09-25 20:14 ` [PATCH V2 4/4] arm64: dts: ti: k3-j7200-common-proc-board: Add j7200-evm compatible Nishanth Menon
2021-09-27 14:27 ` Suman Anna
2021-10-05 22:56 ` (subset) [PATCH V2 0/4] arm64: dts: ti: k3-j721e/j7200: Introduce EVM compatible Nishanth Menon
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=20210925201430.11678-2-nm@ti.com \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--cc=jan.kiszka@siemens.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=sinthu.raja@mistralsolutions.com \
--cc=sinthu.raja@ti.com \
--cc=vigneshr@ti.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).