Re: [PATCH 3/6] spi: do not initialize device chipselects to SPI_INVALID_CS

From: Mark Brown
Date: Sat Oct 12 2024 - 06:27:45 EST


On Sat, Oct 12, 2024 at 11:53:37AM +0200, Jonas Gorski wrote:
> Now that we know the number of valid chipselects, we don't need to
> initialize them to SPI_INVALID_CS to be able to know if they are valid,
> so we can drop both the initialization to SPI_INVALID_CS, as well as the
> check for it.

Dropping the check is fine but it seems useful to set a poison value to
unused chip selects for robustness.

Attachment: signature.asc
Description: PGP signature