From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: James Hilliard <james.hilliard1@gmail.com>, devicetree@vger.kernel.org
Cc: Conor Dooley <conor.dooley@microchip.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>,
Stefan Wahren <stefan.wahren@chargebyte.com>,
Frieder Schrempf <frieder.schrempf@kontron.de>,
Andreas Kemnade <andreas@kemnade.info>,
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: Re: [PATCH v4 1/4] dt-bindings: arm: fsl: Add VAR-SOM-MX6 SoM
Date: Fri, 21 Jul 2023 09:52:19 +0200 [thread overview]
Message-ID: <1eaaad13-f336-bbeb-77fc-7c5509afc15f@linaro.org> (raw)
In-Reply-To: <20230721073626.3673429-1-james.hilliard1@gmail.com>
On 21/07/2023 09:36, James Hilliard wrote:
> Add support for Variscite i.MX6Q VAR-SOM-MX6 SoM.
>
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
> 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 2510eaa8906d..a3ab78429799 100644
> --- a/Documentation/devicetree/bindings/arm/fsl.yaml
> +++ b/Documentation/devicetree/bindings/arm/fsl.yaml
> @@ -298,6 +298,7 @@ properties:
> - udoo,imx6q-udoo # Udoo i.MX6 Quad Board
> - uniwest,imx6q-evi # Uniwest Evi
> - variscite,dt6customboard
> + - variscite,var-som-imx6q # i.MX6 Quad Variscite VAR-SOM-MX6 module
SoM cannot be used on its own.
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-07-21 7:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 7:36 [PATCH v4 1/4] dt-bindings: arm: fsl: Add VAR-SOM-MX6 SoM James Hilliard
2023-07-21 7:36 ` [PATCH v4 2/4] ARM: dts: imx6qdl: Add Variscite VAR-SOM-MX6 SoM support James Hilliard
2023-07-21 7:36 ` [PATCH v4 3/4] dt-bindings: arm: fsl: Add VAR-SOM-MX6 Custom Board James Hilliard
2023-07-21 7:52 ` Krzysztof Kozlowski
2023-07-21 7:36 ` [PATCH v4 4/4] ARM: dts: imx6q: Add Variscite MX6 Custom board support James Hilliard
2023-07-21 7:53 ` Krzysztof Kozlowski
2023-07-21 7:52 ` Krzysztof Kozlowski [this message]
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=1eaaad13-f336-bbeb-77fc-7c5509afc15f@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andreas@kemnade.info \
--cc=cniedermaier@dh-electronics.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=james.hilliard1@gmail.com \
--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=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 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).