linux-kernel - Re: [PATCH] spi: fsl: invert spisel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <161219801882.46355.10875207480645821949.b4-ty@kernel.org>
Date:   Mon, 01 Feb 2021 16:46:58 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Christophe Leroy <christophe.leroy@...roup.eu>,
        Rasmus Villemoes <rasmus.villemoes@...vas.dk>
Cc:     linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
        stable@...r.kernel.org
Subject: Re: [PATCH] spi: fsl: invert spisel_boot signal on MPC8309

On Sat, 30 Jan 2021 15:35:45 +0100, Rasmus Villemoes wrote:
> Commit 7a2da5d7960a ("spi: fsl: Fix driver breakage when SPI_CS_HIGH
> is not set in spi->mode") broke our MPC8309 board by effectively
> inverting the boolean value passed to fsl_spi_cs_control. The
> SPISEL_BOOT signal is used as chipselect, but it's not a gpio, so
> we cannot rely on gpiolib handling the polarity.
> 
> Adapt to the new world order by inverting the logic here. This does
> assume that the slave sitting at the SPISEL_BOOT is active low, but
> should that ever turn out not to be the case, one can create a stub
> gpiochip driver controlling a single gpio (or rather, a single "spo",
> special-purpose output).

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: fsl: invert spisel_boot signal on MPC8309
      commit: 9d2aa6dbf87af89c13cac2d1b4cccad83fb14a7e

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