devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Marek Vasut <marex@denx.de>, Rob Herring <robh@kernel.org>
Cc: "Leonard Göhrs" <l.goehrs@pengutronix.de>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	"Andre Przywara" <andre.przywara@arm.com>,
	kernel@dh-electronics.com,
	"Dario Binacchi" <dario.binacchi@amarulasolutions.com>,
	"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
	"Ahmad Fatoum" <a.fatoum@pengutronix.de>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Steffen Trumtrar" <s.trumtrar@pengutronix.de>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Sean Nyekjaer" <sean@geanix.com>,
	linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v2 1/3] dt-bindings: arm: stm32: Add compatible string for DH electronics STM32MP13xx DHCOR DHSBC board
Date: Wed, 5 Jun 2024 11:03:29 +0200	[thread overview]
Message-ID: <92700993-aec6-4880-bbda-8f54debbe765@foss.st.com> (raw)
In-Reply-To: <ec449ed4-53a9-4fb3-b994-d2079402a26d@denx.de>



On 4/29/24 17:12, Marek Vasut wrote:
> On 4/29/24 4:41 PM, Rob Herring wrote:
> 
>> My bot found new DTB warnings on the .dts files added or changed in this
>> series.
>>
>> Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
>> are fixed by another series. Ultimately, it is up to the platform
>> maintainer whether these warnings are acceptable or not. No need to reply
>> unless the platform maintainer has comments.
>>
>> If you already ran DT checks and didn't see these error(s), then
>> make sure dt-schema is up to date:
>>
>>    pip3 install dtschema --upgrade
>>
>>
>> New warnings running 'make CHECK_DTBS=y 
>> st/stm32mp135f-dhcor-dhsbc.dtb' for 20240427221048.65392-1-marex@denx.de:
>>
>> arch/arm/boot/dts/st/stm32mp135f-dhcor-dhsbc.dtb: 
>> /soc/serial@40018000/bluetooth: failed to match any schema with 
>> compatible: ['infineon,cyw43439-bt', 'brcm,bcm4329-bt']
> 
> This should be addressed in
> 
> [PATCH v2] dt-bindings: net: broadcom-bluetooth: Add CYW43439 DT binding
> 
> It is already AB'd by Krzysztof, I just pinged that patch to figure out 
> what's blocking it.
> 
>> arch/arm/boot/dts/st/stm32mp135f-dhcor-dhsbc.dtb: 
>> /soc/sai@4400a000/audio-controller@4400a004: failed to match any 
>> schema with compatible: ['st,stm32-sai-sub-a']
>> arch/arm/boot/dts/st/stm32mp135f-dhcor-dhsbc.dtb: 
>> /soc/sai@4400a000/audio-controller@4400a024: failed to match any 
>> schema with compatible: ['st,stm32-sai-sub-b']
>> arch/arm/boot/dts/st/stm32mp135f-dhcor-dhsbc.dtb: 
>> /soc/sai@4400b000/audio-controller@4400b004: failed to match any 
>> schema with compatible: ['st,stm32-sai-sub-a']
>> arch/arm/boot/dts/st/stm32mp135f-dhcor-dhsbc.dtb: 
>> /soc/sai@4400b000/audio-controller@4400b024: failed to match any 
>> schema with compatible: ['st,stm32-sai-sub-b']
> 
> This comes from arch/arm/boot/dts/st/stm32mp131.dtsi , i.e. unrelated to 
> this patch. But there is a schema for this in 
> Documentation/devicetree/bindings/sound/st,stm32-sai.yaml in todays' next .

Just tested on stm32-next rebsed on v6.10-rc1) and no yaml issue reported.

      reply	other threads:[~2024-06-05  9:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-27 22:10 [PATCH v2 1/3] dt-bindings: arm: stm32: Add compatible string for DH electronics STM32MP13xx DHCOR DHSBC board Marek Vasut
2024-04-27 22:10 ` [PATCH v2 2/3] ARM: dts: stm32: Add pinmux nodes for DH electronics STM32MP13xx DHCOR SoM and " Marek Vasut
2024-04-27 22:10 ` [PATCH v2 3/3] ARM: dts: stm32: Add support for " Marek Vasut
2024-06-05  9:22   ` Alexandre TORGUE
2024-04-29  5:09 ` [PATCH v2 1/3] dt-bindings: arm: stm32: Add compatible string for DH electronics STM32MP13xx DHCOR " Krzysztof Kozlowski
2024-04-29 14:41 ` Rob Herring
2024-04-29 15:12   ` Marek Vasut
2024-06-05  9:03     ` Alexandre TORGUE [this message]

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=92700993-aec6-4880-bbda-8f54debbe765@foss.st.com \
    --to=alexandre.torgue@foss.st.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=andre.przywara@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@dh-electronics.com \
    --cc=krzk+dt@kernel.org \
    --cc=l.goehrs@pengutronix.de \
    --cc=linus.walleij@linaro.org \
    --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=robh@kernel.org \
    --cc=s.trumtrar@pengutronix.de \
    --cc=sean@geanix.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).