All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Jonas Gorski <jonas.gorski@gmail.com>,
	Guenter Roeck <linux@roeck-us.net>,
	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 16:08:22 +0000	[thread overview]
Message-ID: <e7e5982b-7b85-477d-8649-a58ea1d40e29@sirena.org.uk> (raw)
In-Reply-To: <bc19929e-8231-4bb6-bb36-555a68cb7335@csgroup.eu>

[-- Attachment #1: Type: text/plain, Size: 552 bytes --]

On Wed, Jan 24, 2024 at 03:28:32PM +0000, Christophe Leroy wrote:

> Should we revert that commit 4d8ff6b0991d ("spi: Add multi-cs memories 
> support in SPI core") and implement something simpler ?

I really don't want to keep going through the pain with having people
constantly adding access for chip select that bypass the helpers if we
can avoid it, there's been a constant need for fixups which have just
added to the pain with the multi CS stuff.  My thinking was to get the
API in place and then improve the implementation behind it.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2024-01-24 16:08 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
2024-01-24 14:59               ` Mark Brown
2024-01-24 15:28                 ` Christophe Leroy
2024-01-24 16:08                   ` Mark Brown [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=e7e5982b-7b85-477d-8649-a58ea1d40e29@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=amit.kumar-mahapatra@amd.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.