From: Jonas Jelonek <jonas@jonasjelonek.de>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: realtek-rtl: add support for second CS
Date: Sat, 19 Sep 2026 19:02:07 +0200 [thread overview]
Message-ID: <027f8dea-2661-4ece-b4f0-d772e81cc6e5@jonasjelonek.de> (raw)
In-Reply-To: <aq68SNTdUKzIm0K5@sirena.org.uk>
Hi,
On 19.09.26 18:46, Mark Brown wrote:
> On Fri, Sep 18, 2026 at 09:47:40PM +0000, Jonas Jelonek wrote:
>> The initial driver assumed that the controller's second chip select was
>> vestigial because none of the devices examined at the time used it. This
>> does not hold for all hardware: there are devices with a peripheral
>> connected to CS1. Since the controller only advertises one chip select
>> and keeps CS1 permanently deasserted, those peripherals cannot be used.
>> + /* CSB0/CSB1 are active low: deassert both. */
>> value = __raw_readl(REG(RTL_SPI_SFCSR));
>> - /* Permanently disable CS1, since it's never used */
>> - value |= RTL_SPI_SFCSR_CSB1;
>> - /* Select CS0 for use */
>> - value &= RTL_SPI_SFCSR_CS;
>> + value |= RTL_SPI_SFCSR_CSB0 | RTL_SPI_SFCSR_CSB1;
>> __raw_writel(value, REG(RTL_SPI_SFCSR));
> The original code would ensure that all bits in the register are
> initialised to known values, the new code sets some bits and leaves the
> rest with whatever value they happened to have previously. Probably we
> still want the initialisation of the other bits.
Yes, you're right. Thanks for pointing that out. Indeed, bits setting the
data length and the I/O mode sit in this register too. Zero is required to
have one byte data length and single I/O. I'll fix this in a v2.
Best,
Jonas
prev parent reply other threads:[~2026-09-19 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 21:47 Jonas Jelonek
2026-09-19 16:46 ` Mark Brown
2026-09-19 17:02 ` Jonas Jelonek [this message]
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=027f8dea-2661-4ece-b4f0-d772e81cc6e5@jonasjelonek.de \
--to=jonas@jonasjelonek.de \
--cc=broonie@kernel.org \
--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®