From: Sen Wang <sen@ti.com>
To: <peter.ujfalusi@gmail.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>, Sen Wang <sen@ti.com>
Subject: [PATCH v2 0/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support for McASP
Date: Mon, 2 Feb 2026 18:36:59 -0600 [thread overview]
Message-ID: <20260203003703.2334443-1-sen@ti.com> (raw)
This series adds asynchronous mode support to the McASP driver, which
enables independent configuration of bitclocks, frame sync, and audio
configurations between tx(playback) and rx(record). And achieves
simultaneous playback & record using different audio configurations.
It also adds two clean up patches to the McASP driver that disambiguate
and simplifies the logic which avoids the async enhancement from being
too convoluted to review and analyze.
The implementation is based on vendor documentation and patches tested in
both SK-AM62P-LP (sync mode, McASP slave) and AM62D-EVM
(async mode, McASP master, rx & tx has different TDM configs).
Testing verifies async mode functionality while maintaining backward
compatibility with the default sync mode.
Bootlog and Async mode tests on AM62D-EVM: [0]
[0]: https://gist.github.com/SenWang125/f31f9172b186d414695e37c8b9ef127d
Signed-off-by: Sen Wang <sen@ti.com>
Changes in v2:
- Corrected patch 1 subject title
- Retained original order of operation in patch 3
- Corrected code comments to use inclusive terminology in patch 4
Sen Wang (4):
ASoC: dt-bindings: davinci-mcasp: Add properties for asynchronous mode
ASoC: ti: davinci-mcasp: Disambiguate mcasp_is_synchronous function
ASoC: ti: davinci-mcasp: Streamline pdir behavior across rx & tx streams
ASoC: ti: davinci-mcasp: Add asynchronous mode support
.../bindings/sound/davinci-mcasp-audio.yaml | 71 ++-
include/linux/platform_data/davinci_asp.h | 3 +-
sound/soc/ti/davinci-mcasp.c | 510 ++++++++++++++----
sound/soc/ti/davinci-mcasp.h | 10 +
4 files changed, 481 insertions(+), 113 deletions(-)
base-commit: dbf8fe85a16a33d6b6bd01f2bc606fc017771465
--
2.43.0
next reply other threads:[~2026-02-03 0:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 0:36 Sen Wang [this message]
2026-02-03 0:37 ` [PATCH v2 1/4] ASoC: dt-bindings: davinci-mcasp: Add properties for asynchronous mode Sen Wang
2026-02-03 0:37 ` [PATCH v2 2/4] ASoC: ti: davinci-mcasp: Disambiguate mcasp_is_synchronous function Sen Wang
2026-02-03 0:37 ` [PATCH v2 3/4] ASoC: ti: davinci-mcasp: Streamline pdir behavior across rx & tx streams Sen Wang
2026-02-03 0:37 ` [PATCH v2 4/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support Sen Wang
2026-02-04 11:44 ` [PATCH v2 0/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support for McASP Paresh Bhagat
2026-02-04 16:05 ` Péter Ujfalusi
2026-02-05 11:04 ` 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=20260203003703.2334443-1-sen@ti.com \
--to=sen@ti.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=peter.ujfalusi@gmail.com \
--cc=robh@kernel.org \
--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