From: Rob Herring <robh@kernel.org>
To: Christoph Niedermaier <cniedermaier@dh-electronics.com>
Cc: Fabio Estevam <festevam@denx.de>,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
kernel@dh-electronics.com, linux-arm-kernel@lists.infradead.org,
Shawn Guo <shawnguo@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH V3] dt-bindings: arm: fsl: Add DHCOM PicoITX and DHCOM DRC02 boards
Date: Wed, 21 Jul 2021 20:45:56 -0600 [thread overview]
Message-ID: <20210722024556.GA3196044@robh.at.kernel.org> (raw)
In-Reply-To: <20210714202252.5898-1-cniedermaier@dh-electronics.com>
On Wed, 14 Jul 2021 22:22:52 +0200, Christoph Niedermaier wrote:
> Add DH electronics DHCOM PicoITX and DHCOM DRC02 boards. The DHCOM DRC02
> device can only house a SOM with iMX6S and not with iMX6DL, due to some
> thermal design consideration. But for compatible fsl,imx6dl is chosen,
> because fsl,imx6s isn't available, the iMX6S is basically a iMX6DL with
> one CPU core disabled and therefore the kernel discerns the iMX6S/iMX6DL
> automatically.
>
> 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
> Cc: Fabio Estevam <festevam@denx.de>
> To: devicetree@vger.kernel.org
> ---
> V2: - Remove line with fsl,imx6s on the DRC02 Board
> V3: - Rework of the commit message
> - Add Fabio Estevam to the CC list
> ---
> Documentation/devicetree/bindings/arm/fsl.yaml | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-07-22 2:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 20:22 [PATCH V3] dt-bindings: arm: fsl: Add DHCOM PicoITX and DHCOM DRC02 boards Christoph Niedermaier
2021-07-22 2:45 ` Rob Herring [this message]
2021-07-23 3:30 ` Shawn Guo
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=20210722024556.GA3196044@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=cniedermaier@dh-electronics.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--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).