linux-kernel - Re: [PATCH] spi: bcm2835: Set controller max_speed

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:   Wed, 13 Jan 2021 17:54:26 +0000
From:   Mark Brown <broonie@...nel.org>
To:     sbranden@...adcom.com, rjui@...adcom.com, f.fainelli@...il.com,
        nsaenzjulienne@...e.de,
        Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc:     linux-rpi-kernel@...ts.infradead.org, linux-spi@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        bcm-kernel-feedback-list@...adcom.com,
        linux-arm-kernel@...ts.infradead.org, patches@...nsource.cirrus.com
Subject: Re: [PATCH] spi: bcm2835: Set controller max_speed_hz

On Thu, 7 Jan 2021 16:48:25 +0000, Richard Fitzgerald wrote:
> Set the struct spi_controller max_speed_hz. This is based on the
> reported source clock frequency during probe. The maximum bus clock
> is half the source clock (as per the code in bcm2835_spi_transfer_one).
> 
> If the controller max_speed_hz is not set, the spi core will limit all
> transfers to 0 Hz so only the minimum possible bus frequency would be used.

Applied to

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

Thanks!

[1/1] spi: bcm2835: Set controller max_speed_hz
      commit: c6892892a95debac8050579b0709214b7b28b514

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