linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Jai Luthra <j-luthra@ti.com>
Cc: Francesco Dolcini <francesco@dolcini.it>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jayesh Choudhary <j-choudhary@ti.com>,
	Devarsh Thakkar <devarsht@ti.com>, Bryan Brattlof <bb@ti.com>,
	Aradhya Bhatia <a-bhatia1@ti.com>,
	Francesco Dolcini <francesco.dolcini@toradex.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/7] arm64: dts: ti: k3-am62-verdin: Drop McASP AFIFOs
Date: Wed, 5 Jun 2024 07:52:32 -0500	[thread overview]
Message-ID: <20240605125232.5xql5nonllyslchc@saucy> (raw)
In-Reply-To: <yd4doskkq443xkvc4ahnxexyi7f5oteoh5egiv3plcduyl7dfr@dgtdwd3dbdkg>

On 14:28-20240605, Jai Luthra wrote:
> Hi Francesco,
> 
> Thanks for the review.
> 
> On Jun 05, 2024 at 10:47:13 +0200, Francesco Dolcini wrote:
> > Hello Jai, thanks for the patch.
> > 
> > On Tue, Jun 04, 2024 at 03:11:06PM +0530, Jai Luthra wrote:
> > > McASP AFIFOs are not necessary with UDMA-P/BCDMA as there is buffering
> > > on the DMA IP. Drop these for better audio latency.
> > > 
> > > Fixes: 316b80246b16 ("arm64: dts: ti: add verdin am62")
> > > Signed-off-by: Jai Luthra <j-luthra@ti.com>
> > > ---
> > >  arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi | 8 ++++----
> > >  1 file changed, 4 insertions(+), 4 deletions(-)
> > > 
> > > diff --git a/arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi b/arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi
> > > index 2038c5e04639..27e5220e1dc7 100644
> > > --- a/arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi
> > > +++ b/arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi
> > > @@ -1364,8 +1364,8 @@ &mcasp0 {
> > >  	       0 0 0 0
> > >  	>;
> > >  	tdm-slots = <2>;
> > > -	rx-num-evt = <32>;
> > > -	tx-num-evt = <32>;
> > > +	rx-num-evt = <0>;
> > > +	tx-num-evt = <0>;
> > 
> > From my understanding of the dt-binding having these properties set to
> > <0> is equivalent to not having those properties at all.
> > My suggestion would be to just remove those, therefore.
> > 
> 
> I was following the existing convention of setting it to 0 for 
> disabling, as done in k3-j721e-common-proc-board.dts
> 
> IMO it is better to keep it explicit, but I don't feel strongly against 
> dropping it either (as long as we do the same for j721e). Will defer the 
> decision to the tree maintainers.
> 

If they are equivalent, then just drop them.

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-06-05 12:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04  9:41 [PATCH 0/7] arm64: dts: ti: McASP fixes Jai Luthra
2024-06-04  9:41 ` [PATCH 1/7] arm64: dts: ti: k3-am62x: Drop McASP AFIFOs Jai Luthra
2024-06-04  9:41 ` [PATCH 2/7] arm64: dts: ti: k3-am62a7: " Jai Luthra
2024-06-04  9:41 ` [PATCH 3/7] arm64: dts: ti: k3-am62p5: " Jai Luthra
2024-06-04  9:41 ` [PATCH 4/7] arm64: dts: ti: k3-am625-beagleplay: " Jai Luthra
2024-06-04  9:41 ` [PATCH 5/7] arm64: dts: ti: k3-am62-verdin: " Jai Luthra
2024-06-05  8:47   ` Francesco Dolcini
2024-06-05  8:58     ` Jai Luthra
2024-06-05 12:52       ` Nishanth Menon [this message]
2024-06-04  9:41 ` [PATCH 6/7] arm64: dts: ti: k3-am625-phyboard-lyra-rdk: " Jai Luthra
2024-06-04  9:41 ` [PATCH 7/7] arm64: dts: ti: k3-am62p5-sk: Fix pinmux for McASP1 TX Jai Luthra
2024-06-04 13:33 ` [PATCH 0/7] arm64: dts: ti: McASP fixes Francesco Dolcini
2024-06-05  6:57   ` Jai Luthra

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=20240605125232.5xql5nonllyslchc@saucy \
    --to=nm@ti.com \
    --cc=a-bhatia1@ti.com \
    --cc=bb@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devarsht@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=francesco.dolcini@toradex.com \
    --cc=francesco@dolcini.it \
    --cc=j-choudhary@ti.com \
    --cc=j-luthra@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=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;
as well as URLs for NNTP newsgroup(s).