devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Niedermaier <cniedermaier@dh-electronics.com>
To: 'Fabio Estevam' <festevam@gmail.com>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" 
	<linux-arm-kernel@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
	kernel <kernel@dh-electronics.com>
Subject: RE: [PATCH] dt-bindings: arm: fsl: Add DHCOM PicoITX and DHCOM DRC02 boards [Klartext]
Date: Mon, 24 May 2021 22:38:49 +0000	[thread overview]
Message-ID: <4964298a8d264dafaa807c43bab5d174@dh-electronics.com> (raw)

From: Fabio Estevam <festevam@gmail.com>
Sent: Monday, May 24, 2021 3:03 PM
> 
> Hi Christoph,
>

Hi Fabio,

> 
> On Mon, May 24, 2021 at 9:17 AM Christoph Niedermaier
> <cniedermaier@dh-electronics.com> wrote:
> 
>> +      - description: i.MX6S DHCOM DRC02 Board
>> +        items:
>> +          - const: dh,imx6s-dhcom-drc02
>> +          - const: dh,imx6s-dhcom-som
>> +          - const: fsl,imx6s
> 
> We don't have an fsl,imx6s compatible for the i.MX6 Solo variant. We
> just use fsl,imx6dl instead.

My thought was to be future proof. If there is no match with the Solo now,
it will fall back to the i.MX6 DualLite. That is why I added both fsl,imx6s
and fsl,imx6dl in this order.

Should I remove the line with fsl,imx6s?

Regards
Christoph

             reply	other threads:[~2021-05-24 22:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24 22:38 Christoph Niedermaier [this message]
2021-05-25  0:10 ` [PATCH] dt-bindings: arm: fsl: Add DHCOM PicoITX and DHCOM DRC02 boards [Klartext] Fabio Estevam

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=4964298a8d264dafaa807c43bab5d174@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+dt@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).