From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Marek Vasut <marex@denx.de>, linux-arm-kernel@lists.infradead.org
Cc: Patrick Delaunay <patrick.delaunay@st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [Linux-stm32] [PATCH] ARM: dts: stm32: Add DHCOM based PicoITX board
Date: Wed, 4 Nov 2020 13:20:46 +0100 [thread overview]
Message-ID: <d3ad3da0-384f-51d7-e0fd-fff933e5d1f5@pengutronix.de> (raw)
In-Reply-To: <e4d1ec6e-a5a3-c90d-d6dd-fc37f7c645f1@pengutronix.de>
On 11/4/20 1:19 PM, Ahmad Fatoum wrote:
>>>> +#include "stm32mp157.dtsi"
>>>> +#include "stm32mp15xc.dtsi"
>>>> +#include "stm32mp15xx-dhcom-som.dtsi"
>>>> +#include "stm32mp15xx-dhcom-picoitx.dtsi"
>>>> +
>>>> +/ {
>>>> + model = "DH electronics STM32MP157C DHCOM PicoITX";
>>>> + compatible = "dh,stm32mp157c-dhcom-picoitx", "dh,stm32mp157c-dhcom-som",
>>>> + "st,stm32mp157";
>>>
>>> Is there a separate dt-bindings patch documenting these new compatibles?
>>
>> Which ones ? The dh is in vendor-prefixes.yaml .
>
> Documentation/devicetree/bindings/arm/stm32/stm32.yaml
>
> Should list the board compatibles in use, otherwise dt_binding_check complains.
s/dt_binding_check/dtbs_check/
--
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
next prev parent reply other threads:[~2020-11-04 12:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 18:11 [PATCH] ARM: dts: stm32: Add DHCOM based PicoITX board Marek Vasut
2020-11-04 10:53 ` [Linux-stm32] " Ahmad Fatoum
2020-11-04 12:18 ` Marek Vasut
2020-11-04 12:19 ` Ahmad Fatoum
2020-11-04 12:20 ` Ahmad Fatoum [this message]
2020-11-08 22:19 ` Marek Vasut
2020-11-17 11:32 ` Alexandre Torgue
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=d3ad3da0-384f-51d7-e0fd-fff933e5d1f5@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marex@denx.de \
--cc=mcoquelin.stm32@gmail.com \
--cc=patrick.delaunay@st.com \
/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).