From: Steffen Trumtrar <s.trumtrar@pengutronix.de>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Dinh Nguyen <dinguyen@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
kernel@pengutronix.de
Subject: Re: [PATCH 1/2] ARM: dts: socfpga: Add enclustra PE1 devicetree
Date: Tue, 7 Feb 2023 13:46:54 +0100 [thread overview]
Message-ID: <20230207124654.GA793@pengutronix.de> (raw)
In-Reply-To: <159d831a-7a36-bf2b-3ee8-d4338e999b9f@linaro.org>
On Tue, Feb 07, 2023 at 11:49:58AM +0100, Krzysztof Kozlowski wrote:
> On 07/02/2023 10:41, Steffen Trumtrar wrote:
> > The enclustra PE1 is a baseboard from enclustra GmbH for the enclustra
> > Mercury AA1+ SOM.
> >
> > Signed-off-by: Steffen Trumtrar <s.trumtrar@pengutronix.de>
> > ---
> > arch/arm/boot/dts/Makefile | 1 +
> > .../boot/dts/socfpga_arria10_mercury_pe1.dts | 55 +++++++++++++++++++
> > 2 files changed, 56 insertions(+)
> > create mode 100644 arch/arm/boot/dts/socfpga_arria10_mercury_pe1.dts
> >
> > diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
> > index d08a3c450ce7..2714b70f2a67 100644
> > --- a/arch/arm/boot/dts/Makefile
> > +++ b/arch/arm/boot/dts/Makefile
> > @@ -1179,6 +1179,7 @@ dtb-$(CONFIG_ARCH_S5PV210) += \
> > dtb-$(CONFIG_ARCH_INTEL_SOCFPGA) += \
> > socfpga_arria5_socdk.dtb \
> > socfpga_arria10_chameleonv3.dtb \
> > + socfpga_arria10_mercury_pe1.dtb \
> > socfpga_arria10_socdk_nand.dtb \
> > socfpga_arria10_socdk_qspi.dtb \
> > socfpga_arria10_socdk_sdmmc.dtb \
> > diff --git a/arch/arm/boot/dts/socfpga_arria10_mercury_pe1.dts b/arch/arm/boot/dts/socfpga_arria10_mercury_pe1.dts
> > new file mode 100644
> > index 000000000000..a236489afbc2
> > --- /dev/null
> > +++ b/arch/arm/boot/dts/socfpga_arria10_mercury_pe1.dts
> > @@ -0,0 +1,55 @@
> > +// SPDX-License-Identifier: GPL-2.0
> > +/*
> > + * Copyright 2023 Steffen Trumtrar <kernel@pengutronix.de>
> > + */
> > +/dts-v1/;
> > +#include "socfpga_arria10_mercury_aa1.dtsi"
> > +
> > +/ {
> > + model = "enclustra,mercury-pe1";
>
> This is user-visible string, not compatible. git grep for examples.
Oops, stupid me. Sorry, will fix that of course.
Thanks,
Steffen Trumtrar
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
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-02-07 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 9:41 [PATCH 1/2] ARM: dts: socfpga: Add enclustra PE1 devicetree Steffen Trumtrar
2023-02-07 9:41 ` [PATCH 2/2] dt-bindings: altera: Add enclustra mercury PE1 Steffen Trumtrar
2023-02-07 10:48 ` Krzysztof Kozlowski
2023-02-07 12:47 ` Steffen Trumtrar
2023-02-07 10:49 ` [PATCH 1/2] ARM: dts: socfpga: Add enclustra PE1 devicetree Krzysztof Kozlowski
2023-02-07 12:46 ` Steffen Trumtrar [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=20230207124654.GA793@pengutronix.de \
--to=s.trumtrar@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh+dt@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).