From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: <patrice.chotard@foss.st.com>, Mark Brown <broonie@kernel.org>
Cc: <linux-spi@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <christophe.kerello@foss.st.com>
Subject: Re: [PATCH v4 1/2] ARM: dts: stm32: Create separate pinmux for qspi cs pin in stm32mp15-pinctrl.dtsi
Date: Fri, 26 Aug 2022 10:44:37 +0200 [thread overview]
Message-ID: <17a67dd8-d2ac-99d1-d974-484c6dfa4e85@foss.st.com> (raw)
In-Reply-To: <20220823075850.575043-2-patrice.chotard@foss.st.com>
Dear Patrice
On 8/23/22 09:58, patrice.chotard@foss.st.com wrote:
> From: Patrice Chotard <patrice.chotard@foss.st.com>
>
> Create a separate pinmux for qspi chip select in stm32mp15-pinctrl.dtsi.
> In the case we want to use transfer_one() API to communicate with a SPI
> device, chip select signal must be driven individually.
>
> Signed-off-by: Patrice Chotard <patrice.chotard@foss.st.com>
> ---
> arch/arm/boot/dts/stm32mp15-pinctrl.dtsi | 50 ++++++++++++++++--------
> arch/arm/boot/dts/stm32mp157c-ev1.dts | 12 +++++-
> 2 files changed, 43 insertions(+), 19 deletions(-)
>
> diff --git a/arch/arm/boot/dts/stm32mp15-pinctrl.dtsi b/arch/arm/boot/dts/stm32mp15-pinctrl.dtsi
> index 6052243ad81c..ade4fab45f14 100644
> --- a/arch/arm/boot/dts/stm32mp15-pinctrl.dtsi
> +++ b/arch/arm/boot/dts/stm32mp15-pinctrl.dtsi
> @@ -1189,7 +1189,7 @@ pins {
> };
>
Applied on stm32-next.
Thanks.
Alex
next prev parent reply other threads:[~2022-08-26 8:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 7:58 [PATCH v4 0/2] spi: stm32_qspi: use QSPI bus as 8 lines communication channel patrice.chotard
2022-08-23 7:58 ` [PATCH v4 1/2] ARM: dts: stm32: Create separate pinmux for qspi cs pin in stm32mp15-pinctrl.dtsi patrice.chotard
2022-08-26 8:44 ` Alexandre TORGUE [this message]
2022-08-23 7:58 ` [PATCH v4 2/2] spi: stm32_qspi: Add transfer_one_message() spi callback patrice.chotard
2022-08-23 16:32 ` (subset) [PATCH v4 0/2] spi: stm32_qspi: use QSPI bus as 8 lines communication channel Mark Brown
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=17a67dd8-d2ac-99d1-d974-484c6dfa4e85@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=broonie@kernel.org \
--cc=christophe.kerello@foss.st.com \
--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=patrice.chotard@foss.st.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).