On Tue, Jun 16, 2020 at 09:23:25AM -0500, Pierre-Louis Bossart wrote: > On 6/16/20 4:02 AM, Stephan Gerhold wrote: > > On Tue, Jun 16, 2020 at 10:54:17AM +0200, Stephan Gerhold wrote: > > > For the QCOM case it may be feasible to set dpcm_playback/dpcm_capture > > > appropriately because it is basically only used with one particular > > > DAI driver. But simple-audio-card is generic and used with many > > > different drivers so hard-coding a call into some other driver like > > > Srinivas did above won't work in that case. > Doesn't simple-card rely on DT blobs that can also be updated? DT is an ABI just like ACPI - it's just more featureful. Many systems can easily update their DTs but not all of them and users don't always want to try to keep it in lock step with the kernel. Stuff like this is why I've been dubious about putting DPCM things in there, it's too much of a hard coding of internal APIs.
Attachment:
signature.asc
Description: PGP signature
