linux-kernel - Re: [PATCH] spi: stm32: add a delay before SPI disable

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: <169451869294.2398433.12354327819600702705.b4-ty@kernel.org>
Date:   Tue, 12 Sep 2023 12:38:12 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Valentin Caron <valentin.caron@...s.st.com>
Cc:     Alain Volmat <alain.volmat@...s.st.com>,
        Alexandre Torgue <alexandre.torgue@...s.st.com>,
        linux-spi@...r.kernel.org,
        linux-stm32@...md-mailman.stormreply.com,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: stm32: add a delay before SPI disable

On Wed, 06 Sep 2023 15:27:35 +0200, Valentin Caron wrote:
> As explained in errata sheet, in section "2.14.5 Truncation of SPI output
> signals after EOT event":
> On STM32MP1x, EOT interrupt can be thrown before the true end of
> communication.
> 
> So we add a delay of a half period to wait the real end of the
> transmission.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: stm32: add a delay before SPI disable
      commit: 6de8a70c84ee0586fdde4e671626b9caca6aed74

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