From: Christoph Niedermaier <cniedermaier@dh-electronics.com>
To: 'Rob Herring' <robh@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
kernel <kernel@dh-electronics.com>,
'Fabio Estevam' <festevam@gmail.com>
Subject: RE: [PATCH V2] dt-bindings: arm: fsl: Add DHCOM PicoITX and DHCOM DRC02 boards [Klartext]
Date: Mon, 7 Jun 2021 09:29:36 +0000 [thread overview]
Message-ID: <fb1e21a4a27948d08f960b24dc5dbe54@dh-electronics.com> (raw)
From: Rob Herring <robh@kernel.org>
Sent: Wednesday, June 2, 2021 9:50 PM
> 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 ++++++++++++
>> 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
>
> fsl,imx6s?
In the first version I had here an additional line with "fsl,imx6s",
but currently the kernel isn't supporting that compatible. The i.MX6
Solo is currently supported by "fsl,imx6dl". So my idea was to add
both "fsl,imx6dl" and "fsl,imx6s" to match it maybe on a later kernel
version. If there is no match with the Solo now, it will fall back to
the i.MX6 DualLite. That is why I had both fsl,imx6s and fsl,imx6dl
in that order. On Fabio's advice, I removed the line with "fsl,imx6s"
in version 2.
Is this what you meant by your comment?
>
>> +
>> - description: i.MX6SL based Boards
>> items:
>> - enum:
>> --
>> 2.11.0
Regards
Christoph
reply other threads:[~2021-06-07 9:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=fb1e21a4a27948d08f960b24dc5dbe54@dh-electronics.com \
--to=cniedermaier@dh-electronics.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@dh-electronics.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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).