From: Olivier Moysan <olivier.moysan@foss.st.com>
To: Alexandre Torgue <alexandre.torgue@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Rob Herring <robh+dt@kernel.org>, <arnaud.pouliquen@foss.st.com>,
<fabrice.gasnier@foss.st.com>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
Olivier Moysan <olivier.moysan@foss.st.com>
Subject: [PATCH 3/9] ASoC: dt-bindings: stm32: i2s: allow additional properties.
Date: Fri, 19 Nov 2021 15:45:45 +0100 [thread overview]
Message-ID: <20211119144551.7577-4-olivier.moysan@foss.st.com> (raw)
In-Reply-To: <20211119144551.7577-1-olivier.moysan@foss.st.com>
The STM32 SPI peripheral supports both SPI and I2S protocols.
In the SoC device tree the node describes the peripheral as an
SPI peripheral by default. This default configuration can be
overwritten in board device tree to use the IP as an I2S peripheral.
In this case the address-cells and size-cells properties from
SoC DT SPI node should not be checked against STM32 I2S bindings.
Set additionalProperties to "true" to allow these extra properties.
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(-)
diff --git a/Documentation/devicetree/bindings/sound/st,stm32-i2s.yaml b/Documentation/devicetree/bindings/sound/st,stm32-i2s.yaml
index 52e3368d34dc..591f9c941f54 100644
--- a/Documentation/devicetree/bindings/sound/st,stm32-i2s.yaml
+++ b/Documentation/devicetree/bindings/sound/st,stm32-i2s.yaml
@@ -73,7 +73,7 @@ required:
- dmas
- dma-names
-additionalProperties: false
+additionalProperties: true
examples:
- |
--
2.17.1
next prev parent reply other threads:[~2021-11-19 14:47 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
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 ` Olivier Moysan [this message]
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=20211119144551.7577-4-olivier.moysan@foss.st.com \
--to=olivier.moysan@foss.st.com \
--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=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).