From: Rob Herring <robh@kernel.org>
To: Olivier Moysan <olivier.moysan@foss.st.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
fabrice.gasnier@foss.st.com, devicetree@vger.kernel.org,
arnaud.pouliquen@foss.st.com, Rob Herring <robh+dt@kernel.org>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>
Subject: Re: [PATCH 1/9] ASoC: dt-bindings: stm32: i2s: update example
Date: Tue, 23 Nov 2021 09:34:29 -0700 [thread overview]
Message-ID: <1637685269.713393.3442923.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20211119144551.7577-2-olivier.moysan@foss.st.com>
On Fri, 19 Nov 2021 15:45:43 +0100, Olivier Moysan wrote:
> Some STM32 SPI peripheral instances support I2S for audio.
> SPI and I2S features were initially described through two separated
> nodes in the SoC Device Tree. In the next SoC Device Trees
> a single node is used to describe SPI peripheral, leading
> to a change in node name for I2S.
> Change example in STM32 DT binding example to match this change.
>
> Signed-off-by: Olivier Moysan <olivier.moysan@foss.st.com>
> ---
> Documentation/devicetree/bindings/sound/st,stm32-i2s.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
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/1557188
audio-controller@4000b000: 'port' does not match any of the regexes: 'pinctrl-[0-9]+'
arch/arm/boot/dts/stm32mp157a-dk1.dt.yaml
arch/arm/boot/dts/stm32mp157c-dk2.dt.yaml
next prev parent reply other threads:[~2021-11-23 16:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 14:45 [PATCH 0/9] ARM: dts: stm32: merge spi and i2s nodes Olivier Moysan
2021-11-19 14:45 ` [PATCH 1/9] ASoC: dt-bindings: stm32: i2s: update example Olivier Moysan
2021-11-23 16:34 ` Rob Herring [this message]
2021-11-19 14:45 ` [PATCH 2/9] ASoC: dt-bindings: stm32: i2s: add audio-graph-card port Olivier Moysan
2021-11-23 16:34 ` Rob Herring
2021-11-19 14:45 ` [PATCH 3/9] ASoC: dt-bindings: stm32: i2s: allow additional properties Olivier Moysan
2021-11-19 14:45 ` [PATCH 4/9] ARM: dts: stm32: merge spi and i2s nodes Olivier Moysan
2021-11-19 14:45 ` [PATCH 5/9] ARM: dts: stm32: rename i2s node on stm32mp15xx-dkx boards Olivier Moysan
2021-11-19 14:45 ` [PATCH 6/9] ARM: dts: stm32: rename spi node on stm32mp15xx-dhcor-avenger96 boards Olivier Moysan
2021-11-19 14:45 ` [PATCH 7/9] ARM: dts: stm32: rename spi node on stm32mp15xx-dhcom-drc02 boards Olivier Moysan
2021-11-19 14:45 ` [PATCH 8/9] ARM: dts: stm32: rename spi node on stm32mp157c-ev1 board Olivier Moysan
2021-11-19 14:45 ` [PATCH 9/9] ARM: dts: stm32: adapt i2s node to spi binding on stm32mp15xx-dk Olivier Moysan
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=1637685269.713393.3442923.nullmailer@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=arnaud.pouliquen@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@foss.st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=olivier.moysan@foss.st.com \
--cc=robh+dt@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).