Hello Nishanth, On Tue, Jul 30, 2024 at 06:04:44AM -0500, Nishanth Menon wrote: > On 10:50-20240730, Parth Pancholi wrote: > > On Tue, 2024-07-30 at 11:37 +0200, Parth Pancholi wrote: > > This message originated from outside your organization > > > > From: Parth Pancholi <parth.pancholi@xxxxxxxxxxx> > > > > Correct the McASP nodes - mcasp3 and mcasp4 with the right > > DMAs thread IDs as per TISCI documentation [1] for J784s4. > > This fixes the related McASPs probe failure due to incorrect > > DMA IDs. > > > > Link: http://downloads.ti.com/tisci/esd/latest/5_soc_doc/j784s4/psil_cfg.html#psi-l-source-and-destination-thread-ids/<http://downloads.ti.com/tisci/esd/latest/5_soc_doc/j784s4/psil_cfg.html#psi-l-source-and-destination-thread-ids> [1] > > Fixes: 5095ec4aa1ea ("arm64: dts: ti: k3-j784s4-main: Add McASP nodes") > > Signed-off-by: Parth Pancholi <parth.pancholi@xxxxxxxxxxx> > > --- > > arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi | 4 ++-- > > 1 file changed, 2 insertions(+), 2 deletions(-) > > > > diff --git a/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi b/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi > > index f170f80f00c1..d4ac1c9872a5 100644 > > --- a/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi > > +++ b/arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi > > @@ -2755,7 +2755,7 @@ mcasp3: mcasp@2b30000 { > > interrupts = <GIC_SPI 550 IRQ_TYPE_LEVEL_HIGH>, > > <GIC_SPI 551 IRQ_TYPE_LEVEL_HIGH>; > > interrupt-names = "tx", "rx"; > > - dmas = <&main_udmap 0xc500>, <&main_udmap 0x4500>; > > + dmas = <&main_udmap 0xc403>, <&main_udmap 0x4403>; > > dma-names = "tx", "rx"; > > clocks = <&k3_clks 268 0>; > > clock-names = "fck"; > > @@ -2773,7 +2773,7 @@ mcasp4: mcasp@2b40000 { > > interrupts = <GIC_SPI 552 IRQ_TYPE_LEVEL_HIGH>, > > <GIC_SPI 553 IRQ_TYPE_LEVEL_HIGH>; > > interrupt-names = "tx", "rx"; > > - dmas = <&main_udmap 0xc501>, <&main_udmap 0x4501>; > > + dmas = <&main_udmap 0xc404>, <&main_udmap 0x4404>; > > dma-names = "tx", "rx"; > > clocks = <&k3_clks 269 0>; > > clock-names = "fck"; > > > I think your patch got corrupted. Could you use git send-email or a > proper client? Are you sure it was not your side to mess-up with it? I tested and it applies fine to me $ b4 shazam 20240730093754.1659782-1-parth105105@xxxxxxxxx Grabbing thread from lore.kernel.org/all/20240730093754.1659782-1-parth105105%40gmail.com/t.mbox.gz Checking for newer revisions Grabbing search results from lore.kernel.org Analyzing 2 messages in the thread Checking attestation on all messages, may take a moment... --- ✓ [PATCH] arm64: dts: ti: k3-j784s4-main: Correct McASP DMAs --- ✓ Signed: DKIM/gmail.com --- Total patches: 1 --- Applying: arm64: dts: ti: k3-j784s4-main: Correct McASP DMAs
