mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jai Luthra <j-luthra@ti.com>
To: Nishanth Menon <nm@ti.com>, 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>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Devarsh Thakkar <devarsht@ti.com>, Jai Luthra <j-luthra@ti.com>
Subject: [PATCH 0/7] arm64: dts: ti: McASP fixes
Date: Tue, 4 Jun 2024 15:11:01 +0530	[thread overview]
Message-ID: <20240604-mcasp_fifo_drop-v1-0-03ebe25f47db@ti.com> (raw)

Drop McASP AFIFOs for all AM62 based platforms, as the extra buffering
is not needed with BCDMA already having internal buffering.

Also fix the pinmux for McASP1 on AM62P.

Signed-off-by: Jai Luthra <j-luthra@ti.com>
---
Jai Luthra (7):
      arm64: dts: ti: k3-am62x: Drop McASP AFIFOs
      arm64: dts: ti: k3-am62a7: Drop McASP AFIFOs
      arm64: dts: ti: k3-am62p5: Drop McASP AFIFOs
      arm64: dts: ti: k3-am625-beagleplay: Drop McASP AFIFOs
      arm64: dts: ti: k3-am62-verdin: Drop McASP AFIFOs
      arm64: dts: ti: k3-am625-phyboard-lyra-rdk: Drop McASP AFIFOs
      arm64: dts: ti: k3-am62p5-sk: Fix pinmux for McASP1 TX

 arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi            | 8 ++++----
 arch/arm64/boot/dts/ti/k3-am625-beagleplay.dts        | 4 ++--
 arch/arm64/boot/dts/ti/k3-am625-phyboard-lyra-rdk.dts | 4 ++--
 arch/arm64/boot/dts/ti/k3-am62a7-sk.dts               | 4 ++--
 arch/arm64/boot/dts/ti/k3-am62p5-sk.dts               | 6 +++---
 arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi        | 4 ++--
 6 files changed, 15 insertions(+), 15 deletions(-)
---
base-commit: d97496ca23a2d4ee80b7302849404859d9058bcd
change-id: 20240604-mcasp_fifo_drop-683bc3412262

Best regards,
-- 
Jai Luthra <j-luthra@ti.com>


             reply	other threads:[~2024-06-04  9:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04  9:41 Jai Luthra [this message]
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
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=20240604-mcasp_fifo_drop-v1-0-03ebe25f47db@ti.com \
    --to=j-luthra@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=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=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

all inboxes | Powered by JetHome®