linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Stefan-Gabriel Mirea <stefan-gabriel.mirea@nxp.com>
To: corbet@lwn.net, robh+dt@kernel.org, mark.rutland@arm.com,
	gregkh@linuxfoundation.org, catalin.marinas@arm.com,
	will@kernel.org, shawnguo@kernel.org, leoyang.li@nxp.com
Cc: devicetree@vger.kernel.org,
	"Eddy Petrișor" <eddy.petrisor@nxp.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org, jslaby@suse.com,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 1/5] dt-bindings: arm: fsl: Add the S32V234-EVB board
Date: Wed, 16 Oct 2019 15:48:23 +0300	[thread overview]
Message-ID: <1571230107-8493-2-git-send-email-stefan-gabriel.mirea@nxp.com> (raw)
In-Reply-To: <1571230107-8493-1-git-send-email-stefan-gabriel.mirea@nxp.com>

From: Eddy Petrișor <eddy.petrisor@nxp.com>

Add entry for the NXP S32V234 Customer Evaluation Board to the board/SoC
bindings.

Signed-off-by: Eddy Petrișor <eddy.petrisor@nxp.com>
Signed-off-by: Stefan-Gabriel Mirea <stefan-gabriel.mirea@nxp.com>
Reviewed-by: Rob Herring <robh@kernel.org>
---
 Documentation/devicetree/bindings/arm/fsl.yaml | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml b/Documentation/devicetree/bindings/arm/fsl.yaml
index 1b4b4e6573b5..c211f4f82e25 100644
--- a/Documentation/devicetree/bindings/arm/fsl.yaml
+++ b/Documentation/devicetree/bindings/arm/fsl.yaml
@@ -335,4 +335,10 @@ properties:
               - fsl,ls2088a-rdb
           - const: fsl,ls2088a
 
+      - description: S32V234 based Boards
+        items:
+          - enum:
+              - fsl,s32v234-evb           # S32V234-EVB2 Customer Evaluation Board
+          - const: fsl,s32v234
+
 ...
-- 
2.22.0


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-10-16 12:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-16 12:48 [PATCH v7 0/5] Add initial support for S32V234-EVB Stefan-Gabriel Mirea
2019-10-16 12:48 ` Stefan-Gabriel Mirea [this message]
2019-10-16 12:48 ` [PATCH v7 2/5] arm64: Introduce config for S32 Stefan-Gabriel Mirea
2019-10-16 12:48 ` [PATCH v7 3/5] serial: fsl_linflexuart: Be consistent with the name Stefan-Gabriel Mirea
2019-10-16 12:48 ` [PATCH v7 4/5] arm64: dts: fsl: Add device tree for S32V234-EVB Stefan-Gabriel Mirea
2019-10-26 13:42   ` Shawn Guo
2019-10-16 12:48 ` [PATCH v7 5/5] arm64: defconfig: Enable configs for S32V234 Stefan-Gabriel Mirea
2019-10-16 13:17 ` [PATCH v7 0/5] Add initial support for S32V234-EVB Greg KH
2019-10-16 16:54   ` Stefan-gabriel Mirea
2019-10-26 13:26     ` Shawn Guo
2019-10-26 15:12       ` Stefan-gabriel Mirea
2019-10-26 13:44 ` Shawn Guo

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=1571230107-8493-2-git-send-email-stefan-gabriel.mirea@nxp.com \
    --to=stefan-gabriel.mirea@nxp.com \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=eddy.petrisor@nxp.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=will@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).