From: "Péter Ujfalusi" <peter.ujfalusi@gmail.com>
To: Sen Wang <sen@ti.com>,
broonie@kernel.org, lgirdwood@gmail.com, perex@perex.cz,
tiwai@suse.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Cc: linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support
Date: Mon, 2 Feb 2026 19:02:31 +0200 [thread overview]
Message-ID: <d7ed59c4-2262-4cd5-978f-e9e5c0e8a9a9@gmail.com> (raw)
In-Reply-To: <20260130051045.1898892-5-sen@ti.com>
On 30/01/2026 07:10, Sen Wang wrote:
> McASP has dedicated clock & frame sync registers for both transmit
> and receive. Currently McASP driver only supports synchronous behavior and
> couples both TX & RX settings.
>
> Add logic that enables asynchronous mode via ti,async-mode property. In
> async mode, playback & record can be done simultaneously with different
> audio configurations (tdm slots, tdm width, audio bit depth).
>
> Note the ability to have different tx/rx DSP formats (i2s, dsp_a, etc.),
> while possible in hardware, remains to be a gap as it require changes
> to the corresponding machine driver interface.
>
> Existing IIS (sync mode) and DIT mode logic remains mostly unchanged.
> Exceptions are IIS mode logic that previously assumed sync mode, which has
> now been made aware of the distinction. And shared logic across all modes
> also now checks for McASP tx/rx-specific driver attributes. Those
> attributes have been populated according to the original extent, ensuring
> no divergence in functionality.
>
> Constraints no longer applicable for async mode are skipped.
> Clock selection options have also been added to include rx/tx-only clk_ids,
> exposing independent configuration via the machine driver as well.
>
> Note that asynchronous mode is not applicable for McASP in DIT mode,
> which is a transmitter-only mode to interface w/ self-clocking formats.
>
> Signed-off-by: Sen Wang <sen@ti.com>
> ---
> include/linux/platform_data/davinci_asp.h | 3 +-
> sound/soc/ti/davinci-mcasp.c | 487 +++++++++++++++++-----
> sound/soc/ti/davinci-mcasp.h | 10 +
> 3 files changed, 398 insertions(+), 102 deletions(-)
>
> diff --git a/sound/soc/ti/davinci-mcasp.c b/sound/soc/ti/davinci-mcasp.c
>
static void mcasp_start_rx(struct davinci_mcasp *mcasp)
> {
> if (mcasp->rxnumevt) { /* enable FIFO */
> @@ -230,13 +288,17 @@ static void mcasp_start_rx(struct davinci_mcasp *mcasp)
> /*
> * When ASYNC == 0 the transmit and receive sections operate
> * synchronously from the transmit clock and frame sync. We need to make
> - * sure that the TX signlas are enabled when starting reception.
> + * sure that the TX signals are enabled when starting reception.
> + * Else set pin to be output when McASP is the master
In new code - while it might not match with old code - use producer
instead of master.
Otherwise it looks nice, I trust you have tested the sync and DIT mode.
With this nitpick addressed:
Acked-by: Peter Ujfalusi <peter.ujfalusi@gmail.com>
--
Péter
next prev parent reply other threads:[~2026-02-02 17:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 5:10 [PATCH 0/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support for McASP Sen Wang
2026-01-30 5:10 ` [PATCH 1/4] dt-bindings: sound: davinci-mcasp: Add optional properties for asynchronous mode Sen Wang
2026-02-02 12:44 ` Mark Brown
2026-02-02 20:18 ` Sen Wang
2026-01-30 5:10 ` [PATCH 2/4] ASoC: ti: davinci-mcasp: Disambiguate mcasp_is_synchronous function Sen Wang
2026-02-02 16:42 ` Péter Ujfalusi
2026-01-30 5:10 ` [PATCH 3/4] ASoC: ti: davinci-mcasp: Streamline pdir behavior across rx & tx streams Sen Wang
2026-02-02 16:49 ` Péter Ujfalusi
2026-02-02 21:22 ` Sen Wang
2026-01-30 5:10 ` [PATCH 4/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support Sen Wang
2026-02-02 17:02 ` Péter Ujfalusi [this message]
2026-02-02 21:47 ` Sen Wang
2026-02-05 11:04 ` [PATCH 0/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support for McASP Mark Brown
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=d7ed59c4-2262-4cd5-978f-e9e5c0e8a9a9@gmail.com \
--to=peter.ujfalusi@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=sen@ti.com \
--cc=tiwai@suse.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