linux-kernel - Re: [PATCH 1/2] arm64: dts: ti: k3-am64: Only set UART baud for used ports

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:   Thu, 15 Jun 2023 15:59:38 +0530
From:   Vignesh Raghavendra <vigneshr@...com>
To:     Nishanth Menon <nm@...com>, Wadim Egorov <w.egorov@...tec.de>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Andrew Davis <afd@...com>
CC:     Vignesh Raghavendra <vigneshr@...com>,
        <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] arm64: dts: ti: k3-am64: Only set UART baud for used ports

Hi Andrew Davis,

On Thu, 01 Jun 2023 13:49:32 -0500, Andrew Davis wrote:
> As the binding for "current-speed" states, this should only be used
> when the baud rate of an attached device cannot be detected. This is
> the case for our attached on-board USB-to-UART converter used for
> early kernel console. For all other unconnected/disabled ports this
> can be configured in userspace later, DT is not the place for device
> configuration, especially when there are already standard ways to
> set serial baud in userspace.
> 
> [...]

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

[1/2] arm64: dts: ti: k3-am64: Only set UART baud for used ports
      commit: 27f98f3eca7334fec668ec637ed5e0514458bba8
[2/2] arm64: dts: ti: k3-am64: Use phandle to stdout UART node
      commit: 6b343136388fe1ef5837e45ab921705de76665ee

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