From: Francesco Dolcini <francesco@dolcini.it>
To: Nishanth Menon <nm@ti.com>
Cc: Parth Pancholi <parth.pancholi@toradex.com>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"parth105105@gmail.com" <parth105105@gmail.com>,
"kristo@kernel.org" <kristo@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"j-choudhary@ti.com" <j-choudhary@ti.com>
Subject: Re: [PATCH] arm64: dts: ti: k3-j784s4-main: Correct McASP DMAs
Date: Tue, 30 Jul 2024 14:01:04 +0200 [thread overview]
Message-ID: <20240730120034.GA39114@francesco-nb> (raw)
In-Reply-To: <20240730110444.fctc2lje62ewg4ob@safari>
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@toradex.com>
> >
> > 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@toradex.com>
> > ---
> > 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@gmail.com
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
next prev parent reply other threads:[~2024-07-30 12:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 9:37 [PATCH] arm64: dts: ti: k3-j784s4-main: Correct McASP DMAs Parth Pancholi
[not found] ` <94a0be3616425c7aef7bb0507d60ee11d4776545.camel@toradex.com>
2024-07-30 11:04 ` Nishanth Menon
2024-07-30 12:01 ` Francesco Dolcini [this message]
2024-07-30 12:06 ` Nishanth Menon
2024-07-30 12:02 ` Francesco Dolcini
2024-07-31 5:43 ` Jayesh Choudhary
2024-08-06 12:12 ` Nishanth Menon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240730120034.GA39114@francesco-nb \
--to=francesco@dolcini.it \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j-choudhary@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=parth.pancholi@toradex.com \
--cc=parth105105@gmail.com \
--cc=robh@kernel.org \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox