From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: "Lu, Brent" <brent.lu@intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Cc: "Rojewski, Cezary" <cezary.rojewski@intel.com>,
"kuninori.morimoto.gx@renesas.com"
<kuninori.morimoto.gx@renesas.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"yang.jie@linux.intel.com" <yang.jie@linux.intel.com>,
"tiwai@suse.com" <tiwai@suse.com>,
"liam.r.girdwood@linux.intel.com"
<liam.r.girdwood@linux.intel.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Subject: Re: [alsa-devel] [PATCH] ASoC: bdw-rt5677: channel constraint support
Date: Tue, 10 Sep 2019 09:12:15 -0500 [thread overview]
Message-ID: <99769525-779a-59aa-96da-da96f8f09a8a@linux.intel.com> (raw)
In-Reply-To: <CF33C36214C39B4496568E5578BE70C7402CB9AC@PGSMSX108.gar.corp.intel.com>
>> I also don't see any case where we support 4 channels in any broadwell
>> machine driver?
> It's the bdw-rt5650.c which only exists in chrome's 3.14 branch supporting Buddy
> project. They submitted the machine driver but not yet merged.
>
> https://patchwork.kernel.org/patch/11050985/
>
>>
>> So again can you point me to an issue or existing backport that requires the
>> patch below. Not trying to be obtuse but we should only change older
>> platforms when there is evidence that a change is needed.
> The story is Chrome has a tool called alsa_conformance_test which runs capture or
> playback against a PCM port with all possible configurations (channel, format, rate)
> then measure if the sample rate is correct. Since the channel max number reported
> is 4, it tests the 4-channel 48K capture and reports the actual sample rate is 24000
> instead of 48000. That's the reason we want to add a constraint in machine driver to
> avoid user space programs trying to do 4 channel recording since this machine does
> not support it in the beginning.
ok, that helps get context, thanks for the details.
I would have expected some error to be returned if there's a front-end
opened with 4 channels and the back-end only supports two. Adding the
constraint seems like a work-around to avoid dealing with the mismatch
between FE and BE. I don't understand DPCM enough to suggest an
alternative though. Ranjani, can you help on this one?
And even if we agree with this solution, it'd be nice to apply it for
the Broadwell machine driver for consistency.
next prev parent reply other threads:[~2019-09-10 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 1:24 [PATCH] ASoC: bdw-rt5677: channel constraint support Brent Lu
2019-09-06 14:20 ` [alsa-devel] " Pierre-Louis Bossart
2019-09-09 6:34 ` Lu, Brent
2019-09-09 17:53 ` Pierre-Louis Bossart
2019-09-10 8:28 ` Lu, Brent
2019-09-10 14:12 ` Pierre-Louis Bossart [this message]
2019-09-12 6:00 ` Lu, Brent
2019-09-12 13:06 ` Pierre-Louis Bossart
2019-09-27 12:34 ` Lu, Brent
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=99769525-779a-59aa-96da-da96f8f09a8a@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=brent.lu@intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ranjani.sridharan@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.com \
--cc=yang.jie@linux.intel.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;
as well as URLs for NNTP newsgroup(s).