From: Shawn Guo <shawnguo@kernel.org> To: Christoph Niedermaier <cniedermaier@dh-electronics.com> Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, robh+dt@kernel.org, kernel@dh-electronics.com Subject: Re: [PATCH V2] dt-bindings: arm: fsl: Add DHCOM PicoITX and DHCOM DRC02 boards Date: Wed, 14 Jul 2021 10:26:02 +0800 [thread overview] Message-ID: <20210714022601.GB31370@dragon> (raw) In-Reply-To: <20210525143001.9298-1-cniedermaier@dh-electronics.com> On Tue, May 25, 2021 at 04:30:01PM +0200, Christoph Niedermaier wrote: > Add DH electronics DHCOM PicoITX and DHCOM DRC02 boards. > > Signed-off-by: Christoph Niedermaier <cniedermaier@dh-electronics.com> > Cc: linux-arm-kernel@lists.infradead.org > Cc: linux-kernel@vger.kernel.org > Cc: robh+dt@kernel.org > Cc: Shawn Guo <shawnguo@kernel.org> > Cc: kernel@dh-electronics.com > To: devicetree@vger.kernel.org > --- > V2: Remove line with fsl,imx6s on the DRC02 Board > --- > Documentation/devicetree/bindings/arm/fsl.yaml | 12 ++++++++++++ In the future, please have this bindings patch included in the series that actually uses it. Shawn > 1 file changed, 12 insertions(+) > > diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml b/Documentation/devicetree/bindings/arm/fsl.yaml > index fce2a8670b49..3c4ff79a3be7 100644 > --- a/Documentation/devicetree/bindings/arm/fsl.yaml > +++ b/Documentation/devicetree/bindings/arm/fsl.yaml > @@ -407,6 +407,12 @@ properties: > - const: dfi,fs700e-m60 > - const: fsl,imx6dl > > + - description: i.MX6DL DHCOM PicoITX Board > + items: > + - const: dh,imx6dl-dhcom-picoitx > + - const: dh,imx6dl-dhcom-som > + - const: fsl,imx6dl > + > - description: i.MX6DL Gateworks Ventana Boards > items: > - enum: > @@ -458,6 +464,12 @@ properties: > - const: toradex,colibri_imx6dl # Colibri iMX6 Module > - const: fsl,imx6dl > > + - description: i.MX6S DHCOM DRC02 Board > + items: > + - const: dh,imx6s-dhcom-drc02 > + - const: dh,imx6s-dhcom-som > + - const: fsl,imx6dl > + > - description: i.MX6SL based Boards > items: > - enum: > -- > 2.11.0 >
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org> To: Christoph Niedermaier <cniedermaier@dh-electronics.com> Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, robh+dt@kernel.org, kernel@dh-electronics.com Subject: Re: [PATCH V2] dt-bindings: arm: fsl: Add DHCOM PicoITX and DHCOM DRC02 boards Date: Wed, 14 Jul 2021 10:26:02 +0800 [thread overview] Message-ID: <20210714022601.GB31370@dragon> (raw) In-Reply-To: <20210525143001.9298-1-cniedermaier@dh-electronics.com> On Tue, May 25, 2021 at 04:30:01PM +0200, Christoph Niedermaier wrote: > Add DH electronics DHCOM PicoITX and DHCOM DRC02 boards. > > Signed-off-by: Christoph Niedermaier <cniedermaier@dh-electronics.com> > Cc: linux-arm-kernel@lists.infradead.org > Cc: linux-kernel@vger.kernel.org > Cc: robh+dt@kernel.org > Cc: Shawn Guo <shawnguo@kernel.org> > Cc: kernel@dh-electronics.com > To: devicetree@vger.kernel.org > --- > V2: Remove line with fsl,imx6s on the DRC02 Board > --- > Documentation/devicetree/bindings/arm/fsl.yaml | 12 ++++++++++++ In the future, please have this bindings patch included in the series that actually uses it. Shawn > 1 file changed, 12 insertions(+) > > diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml b/Documentation/devicetree/bindings/arm/fsl.yaml > index fce2a8670b49..3c4ff79a3be7 100644 > --- a/Documentation/devicetree/bindings/arm/fsl.yaml > +++ b/Documentation/devicetree/bindings/arm/fsl.yaml > @@ -407,6 +407,12 @@ properties: > - const: dfi,fs700e-m60 > - const: fsl,imx6dl > > + - description: i.MX6DL DHCOM PicoITX Board > + items: > + - const: dh,imx6dl-dhcom-picoitx > + - const: dh,imx6dl-dhcom-som > + - const: fsl,imx6dl > + > - description: i.MX6DL Gateworks Ventana Boards > items: > - enum: > @@ -458,6 +464,12 @@ properties: > - const: toradex,colibri_imx6dl # Colibri iMX6 Module > - const: fsl,imx6dl > > + - description: i.MX6S DHCOM DRC02 Board > + items: > + - const: dh,imx6s-dhcom-drc02 > + - const: dh,imx6s-dhcom-som > + - const: fsl,imx6dl > + > - description: i.MX6SL based Boards > items: > - enum: > -- > 2.11.0 > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-07-14 2:26 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-25 14:30 [PATCH V2] dt-bindings: arm: fsl: Add DHCOM PicoITX and DHCOM DRC02 boards Christoph Niedermaier 2021-05-25 14:30 ` Christoph Niedermaier 2021-06-02 19:50 ` Rob Herring 2021-06-02 19:50 ` Rob Herring 2021-06-16 11:19 ` Christoph Niedermaier 2021-06-16 11:19 ` Christoph Niedermaier 2021-06-16 11:32 ` Marek Vasut 2021-06-16 11:32 ` Marek Vasut 2021-07-08 7:38 ` Christoph Niedermaier 2021-07-08 7:38 ` Christoph Niedermaier 2021-07-08 11:54 ` Fabio Estevam 2021-07-08 11:54 ` Fabio Estevam 2021-07-14 2:23 ` Shawn Guo 2021-07-14 2:23 ` Shawn Guo 2021-07-14 20:13 ` Christoph Niedermaier 2021-07-14 20:13 ` Christoph Niedermaier 2021-07-14 2:26 ` Shawn Guo [this message] 2021-07-14 2:26 ` Shawn Guo 2021-07-14 20:19 ` Christoph Niedermaier
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=20210714022601.GB31370@dragon \ --to=shawnguo@kernel.org \ --cc=cniedermaier@dh-electronics.com \ --cc=devicetree@vger.kernel.org \ --cc=kernel@dh-electronics.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.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: linkBe 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.