linux-kernel - Re: [PATCH v2] spi: omap2-mcspi: Fix hardcoded reference clock

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: <169574083816.2649563.11311626349884860645.b4-ty@kernel.org>
Date:   Tue, 26 Sep 2023 17:07:18 +0200
From:   Mark Brown <broonie@...nel.org>
To:     linux-spi@...r.kernel.org, Vaishnav Achath <vaishnav.a@...com>
Cc:     d-gole@...com, vigneshr@...com, linux-kernel@...r.kernel.org,
        u-kumar1@...com
Subject: Re: [PATCH v2] spi: omap2-mcspi: Fix hardcoded reference clock

On Tue, 26 Sep 2023 17:08:12 +0530, Vaishnav Achath wrote:
> A hardcoded reference clock of 48 MHz is used to calculate the
> clock divisor values, but the reference clock frequency can be
> different across devices and can be configured which can cause
> a mismatch between the reported frequency and actual SPI clock
> frequency observed. Fix this by fetching the clock rate from
> the clock provider and falling back to hardcoded reference only
> if the clock is not supplied.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: omap2-mcspi: Fix hardcoded reference clock
      commit: 2d9f4877988f64f0f336983de65c365b6a7debfb

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