[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <171898028156.2272421.2927874175187560582.b4-ty@ti.com>
Date: Fri, 21 Jun 2024 20:43:19 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: Nishanth Menon <nm@...com>, MD Danish Anwar <danishanwar@...com>
CC: Vignesh Raghavendra <vigneshr@...com>, Conor Dooley <conor+dt@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Rob Herring <robh@...nel.org>, <linux-kernel@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
Tero Kristo <kristo@...nel.org>, <srk@...com>,
Roger Quadros <rogerq@...nel.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-am642-evm: Enable "SYNC_OUT0" output
Hi MD Danish Anwar,
On Fri, 14 Jun 2024 15:38:29 +0530, MD Danish Anwar wrote:
> The IEP0 SYNC_OUT0 pins are used for PPS out on AM64 EVM.
> Configure its PINMUX here.
>
>
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/1] arm64: dts: ti: k3-am642-evm: Enable "SYNC_OUT0" output
commit: 5fb89782a9e94936c14f2621637ef9df7c4ac0f0
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
Powered by blists - more mailing lists