linux-kernel - Re: [PATCH] spi: Restore delays for non-GPIO chip select

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]

Date: Tue, 12 Mar 2024 16:57:18 +0000
From: Mark Brown <broonie@...nel.org>
To: Amit Kumar Mahapatra <amit.kumar-mahapatra@....com>, 
 Janne Grunau <j@...nau.net>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 asahi@...ts.linux.dev, regressions@...ts.linux.dev
Subject: Re: [PATCH] spi: Restore delays for non-GPIO chip select

On Mon, 11 Mar 2024 23:53:17 +0100, Janne Grunau wrote:
> SPI controller with integrated chip select handling still need to adhere
> to SPI device's CS setup, hold and inactive delays. For controller
> without set_cs_timing spi core shall handle the delays to avoid
> duplicated delay handling in each controller driver.
> Fixes a regression for the out of tree SPI controller and SPI HID
> transport on Apple M1/M1 Pro/Max notebooks.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: Restore delays for non-GPIO chip select
      commit: aa0162dc0dd95c3bf248e3c78068760094e8f64b

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