linux-kernel - Re: [PATCH v2] arm64: dts: ti: k3-am64-mcu: remove incorrect UART base clock rates

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: <165107250533.1111532.8897601413701499471.b4-ty@ti.com>
Date:   Wed, 27 Apr 2022 20:47:30 +0530
From:   Vignesh Raghavendra <vigneshr@...com>
To:     Tero Kristo <kristo@...nel.org>, Nishanth Menon <nm@...com>,
        Matthias Schiffer <matthias.schiffer@...tq-group.com>
CC:     Vignesh Raghavendra <vigneshr@...com>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v2] arm64: dts: ti: k3-am64-mcu: remove incorrect UART base clock rates

Hi Matthias Schiffer,

On Tue, 19 Apr 2022 09:51:57 +0200, Matthias Schiffer wrote:
> We found that (at least some versions of) the sci-fw set the base clock
> rate for UARTs in the MCU domain to 96 MHz instead of the expected 48 MHz,
> leading to incorrect baud rates when used from Linux.
> 
> As the 8250_omap driver will query the actual clock rate from the clk
> driver when clock-frequency is unset, removing the incorrect property is
> sufficient to fix the baud rate.
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[1/1] arm64: dts: ti: k3-am64-mcu: remove incorrect UART base clock rates
      commit: 439677d416b17dd39964d5f7d64b742a2e51da5b

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant 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.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh