From: Michael Sit Wei Hong <michael.wei.hong.sit@intel.com>
To: alsa-devel@alsa-project.org
Cc: cezary.rojewski@intel.com, lars@metafoo.de,
andriy.shevchenko@intel.com, tiwai@suse.com,
jee.heng.sia@intel.com, pierre-louis.bossart@linux.intel.com,
liam.r.girdwood@linux.intel.com, vkoul@kernel.org,
broonie@kernel.org
Subject: [RFC PATCH 0/4] Enable DMA mode on Intel Keem Bay platform
Date: Tue, 17 Nov 2020 16:03:45 +0800 [thread overview]
Message-ID: <20201117080354.4309-1-michael.wei.hong.sit@intel.com> (raw)
v1: Initial patch version, to enable DMA mode on Intel Keembay platform
by exposing some dmaengine api to work around DMA limitations at the
client driver level.
This patchset suggests an ALSA-only quirk, having other more generic
means to deal with this limitation would be fine - we just wanted to
have a discussion on preferred directions. The IPs used are not
Intel-specific so sooner or later someone else will have similar
limitations to work-around.
Michael Sit Wei Hong (4):
dt-bindings: sound: intel, keembay-i2s: Add info for device to use DMA
ASoC: soc-generic-dmaengine-pcm: Add custom prepare and submit
function
ASoC: dmaengine_pcm: expose functions to header file for custom
functions
ASoC: Intel: KMB: Enable DMA transfer mode
.../bindings/sound/intel,keembay-i2s.yaml | 14 ++
include/sound/dmaengine_pcm.h | 21 ++
sound/core/pcm_dmaengine.c | 46 ++--
sound/soc/intel/Kconfig | 2 +
sound/soc/intel/keembay/kmb_platform.c | 202 ++++++++++++++++--
sound/soc/intel/keembay/kmb_platform.h | 9 +
sound/soc/soc-generic-dmaengine-pcm.c | 8 +-
7 files changed, 267 insertions(+), 35 deletions(-)
--
2.17.1
next reply other threads:[~2020-11-17 8:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 8:03 Michael Sit Wei Hong [this message]
2020-11-17 8:03 ` [RFC PATCH 1/4] dt-bindings: sound: intel, keembay-i2s: Add info for device to use DMA Michael Sit Wei Hong
2020-11-17 8:03 ` [RFC PATCH 2/4] ASoC: soc-generic-dmaengine-pcm: Add custom prepare and submit function Michael Sit Wei Hong
2020-11-17 13:56 ` Vinod Koul
2020-11-17 15:50 ` Andy Shevchenko
2020-11-18 0:34 ` Sia, Jee Heng
2020-11-18 4:40 ` Vinod Koul
2020-11-18 5:27 ` Sia, Jee Heng
2020-11-18 14:50 ` Shevchenko, Andriy
2020-11-24 3:51 ` Sia, Jee Heng
2020-11-30 9:57 ` Sit, Michael Wei Hong
2020-11-30 10:45 ` Lars-Peter Clausen
2020-11-30 11:09 ` Shevchenko, Andriy
2020-12-01 8:22 ` Lars-Peter Clausen
2020-12-01 9:10 ` Sia, Jee Heng
2020-12-05 0:55 ` Sit, Michael Wei Hong
2020-12-07 10:05 ` Lars-Peter Clausen
2020-12-07 15:36 ` Pierre-Louis Bossart
2020-12-08 3:21 ` Sia, Jee Heng
2020-12-10 8:24 ` Sit, Michael Wei Hong
2020-12-14 3:23 ` Sit, Michael Wei Hong
2020-11-17 8:03 ` [RFC PATCH 3/4] ASoC: dmaengine_pcm: expose functions to header file for custom functions Michael Sit Wei Hong
2020-11-17 8:03 ` [RFC PATCH 4/4] ASoC: Intel: KMB: Enable DMA transfer mode Michael Sit Wei Hong
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=20201117080354.4309-1-michael.wei.hong.sit@intel.com \
--to=michael.wei.hong.sit@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=jee.heng.sia@intel.com \
--cc=lars@metafoo.de \
--cc=liam.r.girdwood@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.com \
--cc=vkoul@kernel.org \
/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).