From: Rob Herring <robh@kernel.org>
To: Roland Hieber <rhi@pengutronix.de>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
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>, Li Yang <leoyang.li@nxp.com>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Marco Felsch <m.felsch@pengutronix.de>,
Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [PATCH 4/5] ARM: dts: add Variscite VAR-SOM-MX7 System on Module
Date: Tue, 28 Nov 2023 11:22:30 -0600 [thread overview]
Message-ID: <20231128172230.GA3523780-robh@kernel.org> (raw)
In-Reply-To: <20231127-b4-imx7-var-som-gome-v1-4-f26f88f2d0bc@pengutronix.de>
On Mon, Nov 27, 2023 at 10:11:05PM +0100, Roland Hieber wrote:
> From: Marco Felsch <m.felsch@pengutronix.de>
>
> Add DTSI file of Variscite VAR-SOM-MX7 System on Module in a basic
> version. While we don't have a VAR-MX7 development board at hand, we
> will use this DTSI as base for a custom board in a later commit.
>
> Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
> Co-developed-by: Philipp Zabel <p.zabel@pengutronix.de>
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> ---
> arch/arm/boot/dts/nxp/imx/imx7d-var-som-mx7.dtsi | 607 +++++++++++++++++++++++
> 1 file changed, 607 insertions(+)
>
> diff --git a/arch/arm/boot/dts/nxp/imx/imx7d-var-som-mx7.dtsi b/arch/arm/boot/dts/nxp/imx/imx7d-var-som-mx7.dtsi
> new file mode 100644
> index 000000000000..29b9b9305b81
> --- /dev/null
> +++ b/arch/arm/boot/dts/nxp/imx/imx7d-var-som-mx7.dtsi
> @@ -0,0 +1,607 @@
> +// SPDX-License-Identifier: GPL-2.0-only
This license and...
> +#include "imx7d.dtsi"
...what's in here don't match.
Rob
next prev parent reply other threads:[~2023-11-28 17:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 21:11 [PATCH 0/5] ARM: dts: add support for Gossen Metrawatt Profitest Roland Hieber
2023-11-27 21:11 ` [PATCH 1/5] dt-bindings: at24: add ROHM BR24G04 Roland Hieber
2023-11-28 7:51 ` Krzysztof Kozlowski
2023-12-01 9:38 ` Bartosz Golaszewski
2023-11-27 21:11 ` [PATCH 2/5] dt-bindings: vendor-prefixes: add Gossen Metrawatt Roland Hieber
2023-11-28 7:52 ` Krzysztof Kozlowski
2023-11-27 21:11 ` [PATCH 3/5] ARM: dts: imx7d-pinfunc: add mux for OSC32K_32K_OUT via GPIO1_IO03 Roland Hieber
2023-11-27 21:11 ` [PATCH 4/5] ARM: dts: add Variscite VAR-SOM-MX7 System on Module Roland Hieber
2023-11-28 7:53 ` Krzysztof Kozlowski
2023-11-28 17:22 ` Rob Herring [this message]
2023-11-27 21:11 ` [PATCH 5/5] ARM: dts: add support for Gossen Metrawatt Profitest Roland Hieber
2023-11-28 6:09 ` kernel test robot
2023-11-28 7:56 ` Krzysztof Kozlowski
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=20231128172230.GA3523780-robh@kernel.org \
--to=robh@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@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-i2c@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=p.zabel@pengutronix.de \
--cc=rhi@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--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).