DSS is IO coherent on AM65, so we should mark it as such with 'dma-coherent' property in the DT file.
Signed-off-by: Tomi Valkeinen tomi.valkeinen@ti.com Fixes: fc539b90eda2 ("arm64: dts: ti: am654: Add DSS node") Cc: stable@vger.kernel.org # v5.8+ Acked-by: Nikhil Devshatwar nikhil.nd@ti.com ---
v2: Added fixes, stable and Nikhil's ack.
arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 2 ++ 1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am65-main.dtsi b/arch/arm64/boot/dts/ti/k3-am65-main.dtsi index 533525229a8d..a0b4a421026f 100644 --- a/arch/arm64/boot/dts/ti/k3-am65-main.dtsi +++ b/arch/arm64/boot/dts/ti/k3-am65-main.dtsi @@ -867,6 +867,8 @@ dss: dss@04a00000 {
status = "disabled";
+ dma-coherent; + dss_ports: ports { #address-cells = <1>; #size-cells = <0>;
On Mon, 2 Nov 2020 15:46:50 +0200, Tomi Valkeinen wrote:
DSS is IO coherent on AM65, so we should mark it as such with 'dma-coherent' property in the DT file.
Hi Tomi Valkeinen,
I have applied the following to branch ti-k3-dts-next on [1]. Thank you!
[1/1] arm64: dts: ti: k3-am65: mark dss as dma-coherent commit: 50301e8815c681bc5de8ca7050c4b426923d4e19
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] git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git
linux-stable-mirror@lists.linaro.org
-
Nishanth Menon -
Tomi Valkeinen