From: Francesco Dolcini <francesco@dolcini.it>
To: Jai Luthra <j-luthra@ti.com>
Cc: 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>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] arm64: dts: ti: McASP fixes
Date: Tue, 4 Jun 2024 15:33:52 +0200 [thread overview]
Message-ID: <20240604133352.GA10282@francesco-nb> (raw)
In-Reply-To: <20240604-mcasp_fifo_drop-v1-0-03ebe25f47db@ti.com>
Hello Jai,
On Tue, Jun 04, 2024 at 03:11:01PM +0530, Jai Luthra wrote:
> Drop McASP AFIFOs for all AM62 based platforms, as the extra buffering
> is not needed with BCDMA already having internal buffering.
Is this related with the issue in which after play/record or use the
McASP interface the system crashes or behaves in unexpected ways or this
is something else?
Francesco
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Francesco Dolcini <francesco@dolcini.it>
To: Jai Luthra <j-luthra@ti.com>
Cc: 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>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] arm64: dts: ti: McASP fixes
Date: Tue, 4 Jun 2024 15:33:52 +0200 [thread overview]
Message-ID: <20240604133352.GA10282@francesco-nb> (raw)
In-Reply-To: <20240604-mcasp_fifo_drop-v1-0-03ebe25f47db@ti.com>
Hello Jai,
On Tue, Jun 04, 2024 at 03:11:01PM +0530, Jai Luthra wrote:
> Drop McASP AFIFOs for all AM62 based platforms, as the extra buffering
> is not needed with BCDMA already having internal buffering.
Is this related with the issue in which after play/record or use the
McASP interface the system crashes or behaves in unexpected ways or this
is something else?
Francesco
next prev parent reply other threads:[~2024-06-04 13:34 UTC|newest]
Thread overview: 26+ 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 ` 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 ` Jai Luthra
2024-06-04 9:41 ` [PATCH 2/7] arm64: dts: ti: k3-am62a7: " Jai Luthra
2024-06-04 9:41 ` Jai Luthra
2024-06-04 9:41 ` [PATCH 3/7] arm64: dts: ti: k3-am62p5: " Jai Luthra
2024-06-04 9:41 ` Jai Luthra
2024-06-04 9:41 ` [PATCH 4/7] arm64: dts: ti: k3-am625-beagleplay: " Jai Luthra
2024-06-04 9:41 ` Jai Luthra
2024-06-04 9:41 ` [PATCH 5/7] arm64: dts: ti: k3-am62-verdin: " Jai Luthra
2024-06-04 9:41 ` Jai Luthra
2024-06-05 8:47 ` Francesco Dolcini
2024-06-05 8:47 ` Francesco Dolcini
2024-06-05 8:58 ` Jai Luthra
2024-06-05 8:58 ` Jai Luthra
2024-06-05 12:52 ` Nishanth Menon
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 ` 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 9:41 ` Jai Luthra
2024-06-04 13:33 ` Francesco Dolcini [this message]
2024-06-04 13:33 ` [PATCH 0/7] arm64: dts: ti: McASP fixes Francesco Dolcini
2024-06-05 6:57 ` Jai Luthra
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=20240604133352.GA10282@francesco-nb \
--to=francesco@dolcini.it \
--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=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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.