Received-SPF: pass (google.com: domain of linux-kernel+bounces-137551-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
From: Nishanth Menon <nm@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>, Tero Kristo <kristo@kernel.org>,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski
	<krzysztof.kozlowski+dt@linaro.org>,
        Conor Dooley <conor+dt@kernel.org>, Andrew Davis <afd@ti.com>
CC: Nishanth Menon <nm@ti.com>, <linux-arm-kernel@lists.infradead.org>,
        <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/6] arm64: dts: ti: k3-am65: Remove UART baud rate selection
Date: Tue, 9 Apr 2024 14:39:13 -0500
Message-ID: <171269153957.643321.7481119560022583706.b4-ty@ti.com>
In-Reply-To: <20240326185441.29656-1-afd@ti.com>
References: <20240326185441.29656-1-afd@ti.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Hi Andrew Davis,

On Tue, 26 Mar 2024 13:54:36 -0500, Andrew Davis wrote:
> As described in the binding document for the "current-speed" property:
> 
> "This should only be present in case a driver has no chance to know the
> baud rate of the slave device."
> 
> This is not the case for the UART used in K3 devices, the current
> baud-rate can be calculated from the registers. Having this property
> has the effect of actually skipping the baud-rate setup in some drivers
> as it assumes it will already be set to this rate, which may not always
> be the case.
> 
> [...]

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

[1/6] arm64: dts: ti: k3-am65: Remove UART baud rate selection
      commit: 9a1cedcdb98387bfc5d4fb9f1a1ada9121d32757
[2/6] arm64: dts: ti: k3-am64: Remove UART baud rate selection
      commit: 78331a044106f7022915058376ac56ec5d048124
[3/6] arm64: dts: ti: k3-j7200: Remove UART baud rate selection
      commit: 69dfa876d4b03f7bc043b196c472fca5d339722a
[4/6] arm64: dts: ti: k3-j721e: Remove UART baud rate selection
      commit: 14e556b08380b20833c5e2f6a5826d0669e0e0fa
[5/6] arm64: dts: ti: k3-j721s2: Remove UART baud rate selection
      commit: cfcfcd47c9f049be4ebcee90eafaf78b03cdf05f
[6/6] arm64: dts: ti: k3-j784s4: Remove UART baud rate selection
      commit: bd305a20fd338690fdd8ab8c4a50ab9d14066dfe

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
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D