From: Lucas Stach <dev@lynxeye.de>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Fabio Estevam <festevam@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
"Lukas F . Hartmann" <lukas@mntre.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kernel@pengutronix.de
Subject: [PATCH v4 1/5] dt-bindings: arm: fsl: add Nitrogen8 SoM
Date: Mon, 14 Jun 2021 19:06:29 +0200 [thread overview]
Message-ID: <20210614170633.31638-1-dev@lynxeye.de> (raw)
Add compatible for the BoundaryDevices Nitrogen8 system on module.
Signed-off-by: Lucas Stach <dev@lynxeye.de>
---
Documentation/devicetree/bindings/arm/fsl.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml b/Documentation/devicetree/bindings/arm/fsl.yaml
index 297c87f45db8..15519cc2d2c0 100644
--- a/Documentation/devicetree/bindings/arm/fsl.yaml
+++ b/Documentation/devicetree/bindings/arm/fsl.yaml
@@ -730,6 +730,7 @@ properties:
items:
- enum:
- boundary,imx8mq-nitrogen8m # i.MX8MQ NITROGEN Board
+ - boundary,imx8mq-nitrogen8m-som # i.MX8MQ NITROGEN SoM
- einfochips,imx8mq-thor96 # i.MX8MQ Thor96 Board
- fsl,imx8mq-evk # i.MX8MQ EVK Board
- google,imx8mq-phanbell # Google Coral Edge TPU
--
2.31.1
next reply other threads:[~2021-06-14 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 17:06 Lucas Stach [this message]
2021-06-14 17:06 ` [PATCH v4 2/5] arm64: dts: imx8mq: add Nitrogen8 SoM Lucas Stach
2021-06-14 17:06 ` [PATCH v4 3/5] dt-bindings: vendor-prefixes: add mntre Lucas Stach
2021-06-14 17:06 ` [PATCH v4 4/5] dt-bindings: arm: fsl: add MNT Reform2 board Lucas Stach
2021-06-14 17:06 ` [PATCH v4 5/5] arm64: dts: imx8mq: add support for MNT Reform2 Lucas Stach
2021-06-24 20:41 ` [PATCH v4 1/5] dt-bindings: arm: fsl: add Nitrogen8 SoM Rob Herring
2021-07-14 4:13 ` 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=20210614170633.31638-1-dev@lynxeye.de \
--to=dev@lynxeye.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=lukas@mntre.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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).