On Mon, Nov 16, 2020 at 02:10:16PM -0600, Pierre-Louis Bossart wrote: > On 11/16/20 1:58 PM, Mark Brown wrote: > > On Mon, Nov 16, 2020 at 02:19:03PM +0800, Michael Sit Wei Hong wrote: > > Can we not extend the dmaengine API so that the ASoC layer (and any > > other users) can become aware of this limitation and handle it > > appropriately rather than jumping straight to some client driver > > specific handling? > This was supposed to be an RFC, I asked Vinod/Lars to be copied for > feedback. Unfortunately the RFC tag is missing and Vinod's email wasn't the > right one... (fixed now). > 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. Generally with the dmaengine stuff we've added new query APIs to dmaengine and then used those in the ALSA/ASoC code to enumerate things, this certainly sounds like something that another device might have so it seems worth following that approach.
Attachment:
signature.asc
Description: PGP signature
