spi: Simplify conditionals in spi_set_cs()
PATCH 1/1 spi: Simplify conditionals in spi_set_cs()
First of all, the (foo && bar) || (!foo && !bar) when foo and bar are booleans is equivalent to (foo == bar). Second, reuse variable that holds already the calculation of the SPI CS mode to be active-high. No functional changes intended.
--- drivers/spi/spi.c | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-)
drivers/spi/spi.c +4 -6
@@ -1077,10 +1077,8 @@ static void spi_set_cs(struct spi_device *spi, bool enable, bool force)* Avoid calling into the driver (or doing delays) if the chip select * isn't actually changing from the last time this was called. */ -if (!force && ((enable && spi->controller->last_cs_index_mask == spi->cs_index_mask && -spi_is_last_cs (spi)) || - (!enable && spi->controller->last_cs_index_mask == spi->cs_index_mask && - !spi_is_last_cs (spi))) && +if (!force && (enable ==spi_is_last_cs (spi)) && + (spi->controller->last_cs_index_mask == spi->cs_index_mask) && (spi->controller->last_cs_mode_high == (spi->mode &SPI_CS_HIGH )))return ;
@@ -1089,9 +1087,9 @@ static void spi_set_cs(struct spi_device *spi, bool enable, bool force) spi->controller->last_cs_index_mask = spi->cs_index_mask;for (idx =0 ; idx <SPI_CS_CNT_MAX ; idx++) spi->controller->last_cs[idx] = enable ?spi_get_chipselect (spi,0 ) :SPI_INVALID_CS ; - spi->controller->last_cs_mode_high = spi->mode &SPI_CS_HIGH ; -if (spi->mode &SPI_CS_HIGH ) + spi->controller->last_cs_mode_high = spi->mode &SPI_CS_HIGH ; +if (spi->controller->last_cs_mode_high) enable = !enable;/*
Signature · 1 line
2.47.2
Mark Brown
maintainerQuoted 6 lines · Andy Shevchenko
First of all, the (foo && bar) || (!foo && !bar) when foo and bar are booleans is equivalent to (foo == bar). Second, reuse variable that holds already the calculation of the SPI CS mode to be active-high. No functional changes intended.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: Simplify conditionals in spi_set_cs()
commit: 1f1d979fbf741c3608a344373f88444dc8749967
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks,
Mark