public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: <Ryan.Wanner@microchip.com>
To: <robh@kernel.org>
Cc: <alsa-devel@alsa-project.org>, <broonie@kernel.org>,
	<Nicolas.Ferre@microchip.com>, <Claudiu.Beznea@microchip.com>,
	<devicetree@vger.kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
	<lgirdwood@gmail.com>, <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <robh+dt@kernel.org>,
	<alexandre.belloni@bootlin.com>
Subject: Re: [PATCH] ASoC: dt-bindings: atmel-i2s: Convert to json-schema
Date: Wed, 13 Jul 2022 22:02:13 +0000	[thread overview]
Message-ID: <9f94f0cb-a8d4-e5dd-0e98-e8773c04ce20@microchip.com> (raw)
In-Reply-To: <1657739327.994394.246143.nullmailer@robh.at.kernel.org>

On 7/13/22 12:08, Rob Herring wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On Wed, 13 Jul 2022 09:25:38 -0700, Ryan.Wanner@microchip.com wrote:
>> From: Ryan Wanner <Ryan.Wanner@microchip.com>
>>
>> Convert atmel i2s devicetree binding to json-schema.
>> Change file name to match json-schema naming.
>>
>> Signed-off-by: Ryan Wanner <Ryan.Wanner@microchip.com>
>> ---
>>  .../bindings/sound/atmel,sama5d2-i2s.yaml     | 83 +++++++++++++++++++
>>  .../devicetree/bindings/sound/atmel-i2s.txt   | 46 ----------
>>  2 files changed, 83 insertions(+), 46 deletions(-)
>>  create mode 100644 Documentation/devicetree/bindings/sound/atmel,sama5d2-i2s.yaml
>>  delete mode 100644 Documentation/devicetree/bindings/sound/atmel-i2s.txt
>>
> 
> Running 'make dtbs_check' with the schema in this patch gives the
> following warnings. Consider if they are expected or the schema is
> incorrect. These may not be new warnings.
> 
> Note that it is not yet a requirement to have 0 warnings for dtbs_check.
> This will change in the future.
> 
> Full log is available here: https://patchwork.ozlabs.org/patch/
> 
> 
The warning is fixed with this patch: 
https://lore.kernel.org/linux-arm-kernel/20220707215812.193008-1-Ryan.Wanner@microchip.com/ 
I did not think this strictly depended on this patch because it does not 
change things on this file.

> i2s@fc04c000: 'assigned-parrents' does not match any of the regexes: 'pinctrl-[0-9]+'
>         arch/arm/boot/dts/at91-kizbox3-hs.dtb
>         arch/arm/boot/dts/at91-sama5d27_som1_ek.dtb
>         arch/arm/boot/dts/at91-sama5d27_wlsom1_ek.dtb
>         arch/arm/boot/dts/at91-sama5d2_icp.dtb
>         arch/arm/boot/dts/at91-sama5d2_ptc_ek.dtb
>         arch/arm/boot/dts/at91-sama5d2_xplained.dtb
> 


  reply	other threads:[~2022-07-13 22:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 16:25 [PATCH] ASoC: dt-bindings: atmel-i2s: Convert to json-schema Ryan.Wanner
2022-07-13 19:08 ` Rob Herring
2022-07-13 22:02   ` Ryan.Wanner [this message]
2022-07-14  8:38 ` Krzysztof Kozlowski

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=9f94f0cb-a8d4-e5dd-0e98-e8773c04ce20@microchip.com \
    --to=ryan.wanner@microchip.com \
    --cc=Claudiu.Beznea@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=robh@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