linux-kernel - Re: [PATCH] spi: axi-spi-engine: fix sleep calculation

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: <171931525390.64438.17593023139078720275.b4-ty@kernel.org>
Date: Tue, 25 Jun 2024 12:34:13 +0100
From: Mark Brown <broonie@...nel.org>
To: David Lechner <dlechner@...libre.com>
Cc: Michael Hennerich <michael.hennerich@...log.com>, 
 Nuno Sá <nuno.sa@...log.com>, linux-spi@...r.kernel.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: axi-spi-engine: fix sleep calculation

On Thu, 20 Jun 2024 11:43:58 -0500, David Lechner wrote:
> The sleep calculation was not taking into account increased delay when
> the SPI device is not running at the maximum SCLK frequency.
> 
> Rounding down when one SCLK tick was the same as the instruction
> execution time was fine, but it rounds down too much when SCLK is
> slower. This changes the rounding to round up instead while still
> taking into account the instruction execution time so that small
> delays remain accurate.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: axi-spi-engine: fix sleep calculation
      commit: 40b3d0838a1ff242e61f341e49226074bbdd319f

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