From: David Laight <David.Laight@ACULAB.COM>
To: 'Jonas Gorski' <jonas.gorski@gmail.com>,
Guenter Roeck <linux@roeck-us.net>
Cc: Mark Brown <broonie@kernel.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Herve Codina <herve.codina@bootlin.com>,
"Amit Kumar Mahapatra" <amit.kumar-mahapatra@amd.com>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: RE: [PATCH] spi: Raise limit on number of chip selects
Date: Wed, 24 Jan 2024 14:35:45 +0000 [thread overview]
Message-ID: <7cadfe452f614e92be81d01111203a54@AcuMS.aculab.com> (raw)
In-Reply-To: <CAOiHx=mM7kpzR-MOshsgXZM+CSB0nawfWxMhpt=tuhmJyMTCzQ@mail.gmail.com>
...
> For some reason we don't store neither the actual number of supported
> parallel chipselects in the controller, nor the amount of chipselects
> used by the spi device, so all loops always need to iterate
> SPI_CS_CNT_MAX times and check for the chipselect numbers not being
> 0xff instead of limiting by the (possible to know) actual number of
> chip selects in use.
Or even the highest one ever used.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2024-01-24 14:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 1:21 [PATCH] spi: Raise limit on number of chip selects Mark Brown
2024-01-22 22:07 ` Mark Brown
2024-01-23 11:04 ` Herve Codina
2024-01-23 13:18 ` Mark Brown
2024-01-23 13:26 ` Christophe Leroy
2024-01-23 13:53 ` Mark Brown
2024-01-23 16:50 ` Jonas Gorski
2024-01-23 17:47 ` Guenter Roeck
2024-01-24 13:41 ` Jonas Gorski
2024-01-24 14:35 ` David Laight [this message]
2024-01-24 14:59 ` Mark Brown
2024-01-24 15:28 ` Christophe Leroy
2024-01-24 16:08 ` 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=7cadfe452f614e92be81d01111203a54@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=amit.kumar-mahapatra@amd.com \
--cc=broonie@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=herve.codina@bootlin.com \
--cc=jonas.gorski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=thomas.petazzoni@bootlin.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).