[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <aF553GU_btT81_b_@finisterre.sirena.org.uk>
Date: Fri, 27 Jun 2025 12:00:44 +0100
From: Mark Brown <broonie@...nel.org>
To: "Hohn, Torben" <Torben.Hohn@...ker.com>
Cc: "amit.kumar-mahapatra@....com" <amit.kumar-mahapatra@....com>,
"frogger@...danger.blackshift.org" <frogger@...danger.blackshift.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
"linux@...ck-us.net" <linux@...ck-us.net>
Subject: Re: [PATCH v2] spi: Raise limit on number of chip selects
On Thu, Jun 26, 2025 at 04:58:20PM +0000, Hohn, Torben wrote:
> Hello Marc,
That isn't my name...
> +#define SPI_CS_CNT_MAX 16
> If this is increased to 24 now, we need to carry another patch on top of mainline again once we add another Chipselect
> into our FPGA, or into the next iteration of our hardware. We would really prefer that a Kconfig value is used.
> We have handed a patch to pengutronix, because they can send proper emails.
> In the IIO framework there is a Konfig Value for something similar:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/iio/trigger.h#n74
This doesn't really work, we're supposed to support single kernel image
so putting per platform configuration in Kconfig ends up being at best a
usability problem. At some point it's better to just bite the bullet
and make things dynamic.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists