From: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
To: charles-antoine.couret@mind.be
Cc: broonie@kernel.org, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2 v2] spi: add SPI_MOSI_IDLE_LOW support from device tree
Date: Sun, 29 Mar 2026 11:25:56 -0300 [thread overview]
Message-ID: <ack2dPiLpO0uE2VE@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <20260329125725.2984756-1-charles-antoine.couret@mind.be>
Hello Charles-Antoine,
On 03/29, charles-antoine.couret@mind.be wrote:
> From: Charles-Antoine Couret <charles-antoine.couret@mind.be>
>
> This flag was introduced but was not added as device tree property which is
> limiting the possibility to use this flag on real devices.
I'm not seeing why a device tree property is needed for SPI idle modes. For
idling high, the configuration is requested through spi_setup(). It should
work in similar way for idling low. See spi-summary.rst. If believe a dt
property is needed despite the spi_setup() interface, can you elaborate on why?
>
> This flag can be configured as done for other flags.
>
> Signed-off-by: Charles-Antoine Couret <charles-antoine.couret@mind.be>
> ---
> drivers/spi/spi.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
> index 9b1125556d29..489a64e20305 100644
> --- a/drivers/spi/spi.c
> +++ b/drivers/spi/spi.c
> @@ -2363,6 +2363,8 @@ static int of_spi_parse_dt(struct spi_controller *ctlr, struct spi_device *spi,
> spi->mode |= SPI_LSB_FIRST;
> if (of_property_read_bool(nc, "spi-cs-high"))
> spi->mode |= SPI_CS_HIGH;
> + if (of_property_read_bool(nc, "spi-mosi-idle-low"))
> + spi->mode |= SPI_MOSI_IDLE_LOW;
>
> /* Device DUAL/QUAD mode */
>
> --
> 2.53.0
>
>
With best regards,
Marcelo
next prev parent reply other threads:[~2026-03-29 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 12:57 charles-antoine.couret
2026-03-29 14:25 ` Marcelo Schmitt [this message]
2026-03-29 15:39 ` Couret Charles-Antoine
2026-03-29 19:29 ` Marcelo Schmitt
2026-03-31 23:05 ` Couret Charles-Antoine
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=ack2dPiLpO0uE2VE@debian-BULLSEYE-live-builder-AMD64 \
--to=marcelo.schmitt1@gmail.com \
--cc=broonie@kernel.org \
--cc=charles-antoine.couret@mind.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.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
all inboxes | Powered by JetHome®