From: James Hilliard <james.hilliard1@gmail.com>
To: devicetree@vger.kernel.org
Cc: "James Hilliard" <james.hilliard1@gmail.com>,
"Pierluigi Passaro" <pierluigi.p@variscite.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Marek Vasut" <marex@denx.de>,
"Frieder Schrempf" <frieder.schrempf@kontron.de>,
"Stefan Wahren" <stefan.wahren@chargebyte.com>,
"Michal Vokáč" <michal.vokac@ysoft.com>,
"Philippe Schenker" <philippe.schenker@toradex.com>,
"Marcel Ziswiler" <marcel.ziswiler@toradex.com>,
"Christoph Niedermaier" <cniedermaier@dh-electronics.com>,
"Li Yang" <leoyang.li@nxp.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 1/3] dt-bindings: arm: fsl: Add VAR-SOM-MX6 SoM with Custom Board
Date: Wed, 26 Jul 2023 06:37:39 -0600 [thread overview]
Message-ID: <20230726123747.4097755-1-james.hilliard1@gmail.com> (raw)
Add support for Variscite i.MX6Q VAR-SOM-MX6 SoM with Custom Board.
Cc: Pierluigi Passaro <pierluigi.p@variscite.com>
Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
---
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 2510eaa8906d..76bb098605e7 100644
--- a/Documentation/devicetree/bindings/arm/fsl.yaml
+++ b/Documentation/devicetree/bindings/arm/fsl.yaml
@@ -385,6 +385,12 @@ properties:
- const: toradex,apalis_imx6q
- const: fsl,imx6q
+ - description: i.MX6Q Variscite VAR-SOM-MX6 Boards
+ items:
+ - const: variscite,mx6customboard
+ - const: variscite,var-som-imx6q
+ - const: fsl,imx6q
+
- description: TQ-Systems TQMa6Q SoM (variant A) on MBa6x
items:
- const: tq,imx6q-mba6x-a
--
2.34.1
next reply other threads:[~2023-07-26 12:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 12:37 James Hilliard [this message]
2023-07-26 12:37 ` [PATCH v7 2/3] ARM: dts: imx6qdl: Add Variscite VAR-SOM-MX6 SoM support James Hilliard
2023-07-26 12:54 ` Fabio Estevam
2023-07-26 12:37 ` [PATCH v7 3/3] ARM: dts: imx6q: Add Variscite MX6 Custom board support James Hilliard
2023-07-26 12:54 ` Fabio Estevam
2023-07-26 18:23 ` [PATCH v7 1/3] dt-bindings: arm: fsl: Add VAR-SOM-MX6 SoM with Custom Board Krzysztof Kozlowski
2023-07-26 18:26 ` Conor Dooley
2023-08-07 16:03 ` James Hilliard
2023-08-07 16:03 ` James Hilliard
2023-08-08 7:45 ` Conor Dooley
2023-08-08 7:45 ` Conor Dooley
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=20230726123747.4097755-1-james.hilliard1@gmail.com \
--to=james.hilliard1@gmail.com \
--cc=cniedermaier@dh-electronics.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=marex@denx.de \
--cc=michal.vokac@ysoft.com \
--cc=philippe.schenker@toradex.com \
--cc=pierluigi.p@variscite.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefan.wahren@chargebyte.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.