From: Patrice Chotard <patrice.chotard@foss.st.com>
To: Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
<christophe.kerello@foss.st.com>, <linux-spi@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Patrice Chotard <patrice.chotard@foss.st.com>
Subject: [PATCH 0/2] spi: spi-stm32-ospi: dt-bindings fixes
Date: Fri, 21 Mar 2025 10:44:05 +0100 [thread overview]
Message-ID: <20250321-upstream_ospi_required_resets-v1-0-9aa4702e3ae2@foss.st.com> (raw)
Make "resets" property mandatory.
Update spi-stm32-ospi driver and dt-bindings accordingly.
Signed-off-by: Patrice Chotard <patrice.chotard@foss.st.com>
---
Patrice Chotard (2):
spi: dt-bindings: st,stm32mp25-ospi: Make "resets" a required property
spi: spi-stm32-ospi: Make "resets" a required property
Documentation/devicetree/bindings/spi/st,stm32mp25-ospi.yaml | 1 +
drivers/spi/spi-stm32-ospi.c | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
---
base-commit: e94bd4ec45ac156616da285a0bf03056cd7430fc
change-id: 20250321-upstream_ospi_required_resets-34a8b17611b6
Best regards,
--
Patrice Chotard <patrice.chotard@foss.st.com>
next reply other threads:[~2025-03-21 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 9:44 Patrice Chotard [this message]
2025-03-21 9:44 ` [PATCH 1/2] spi: dt-bindings: st,stm32mp25-ospi: Make "resets" a required property Patrice Chotard
2025-03-21 10:13 ` Krzysztof Kozlowski
2025-03-24 10:19 ` Patrice CHOTARD
2025-03-21 9:44 ` [PATCH 2/2] spi: spi-stm32-ospi: " Patrice Chotard
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=20250321-upstream_ospi_required_resets-v1-0-9aa4702e3ae2@foss.st.com \
--to=patrice.chotard@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=broonie@kernel.org \
--cc=christophe.kerello@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=p.zabel@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).