mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Mark Brown <broonie@kernel.org>, Herve Codina <herve.codina@bootlin.com>
Cc: Amit Kumar Mahapatra <amit.kumar-mahapatra@amd.com>,
	Guenter Roeck <linux@roeck-us.net>,
	"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: Tue, 23 Jan 2024 13:26:04 +0000	[thread overview]
Message-ID: <93385fc2-7596-4f66-b0c1-07d7d5c9ed8d@csgroup.eu> (raw)
In-Reply-To: <cefafa30-b78d-471b-83e0-b05060d806d4@sirena.org.uk>



Le 23/01/2024 à 14:18, Mark Brown a écrit :
> On Tue, Jan 23, 2024 at 12:04:30PM +0100, Herve Codina wrote:
> 
>> Moving the SPI_CS_CNT_MAX value from 4 to 8 is not enough to handle my case.
>> Tested moving SPI_CS_CNT_MAX to 16 and it was ok.
> 
> OK, I've also heard 12 as a number which this would cover.

By the way the comment in include/linux/spi/spi.h is confusing. This 
SPI_CS_CNT_MAX is really not the max number of CS supported per SPI 
device but the max number of CS supported per SPI controller.

  reply	other threads:[~2024-01-23 13:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22  1:21 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 [this message]
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
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=93385fc2-7596-4f66-b0c1-07d7d5c9ed8d@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=amit.kumar-mahapatra@amd.com \
    --cc=broonie@kernel.org \
    --cc=herve.codina@bootlin.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

all inboxes | Powered by JetHome®