From: "Alexey Klimov" <alexey.klimov@linaro.org>
To: "Srinivas Kandagatla" <srinivas.kandagatla@oss.qualcomm.com>,
"Ravi Hothi" <ravi.hothi@oss.qualcomm.com>,
"Srinivas Kandagatla" <srini@kernel.org>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>
Cc: <linux-sound@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel@oss.qualcomm.com>,
<mohammad.rafi.shaik@oss.qualcomm.com>,
<ajay.nandam@oss.qualcomm.com>
Subject: Re: [PATCH v2 0/2] ASoC: qcom: q6dsp-lpass-ports: Expand sampling rate and PCM format constraints
Date: Mon, 22 Dec 2025 04:25:12 +0000 [thread overview]
Message-ID: <DF4GKIYJPDKA.DTLON4U0AZHB@linaro.org> (raw)
In-Reply-To: <d9e64bd0-7ccf-490c-a6be-d9cc9484475d@oss.qualcomm.com>
On Wed Dec 17, 2025 at 12:56 PM GMT, Srinivas Kandagatla wrote:
>
>
> On 12/17/25 11:38 AM, Alexey Klimov wrote:
>> On Mon Dec 15, 2025 at 7:29 AM GMT, Ravi Hothi wrote:
>>>
>>>
>>> On 12/10/2025 7:26 PM, Alexey Klimov wrote:
>>>> On Wed Dec 10, 2025 at 6:51 AM GMT, Ravi Hothi wrote:
>>>>> This patch series expands the existing constraints in
>>>>> the q6dsp-lpass-ports driver to improve compatibility
>>>>> and flexibility for audio stream configurations.
>>>>>
>>>>> The first patch extends the supported sampling rates to cover a wider
>>>>> range, from 8000 Hz to 192000 Hz, ensuring better compatibility with
>>>>> diverse audio hardware and allowing more flexible audio stream setups.
>>>>>
>>>>> The second patch adds support for the 32-bit PCM format
>>>>> (SNDRV_PCM_FMTBIT_S32_LE) alongside the existing 16-bit
>>>>> and 24-bit formats, enabling handling of high-resolution
>>>>> audio streams and improving audio quality for supported hardware.
>>>>
>>>> Is q6dsp-lpass-ports involved in compress offloaded playback on
>>>> existing devices? If yes, then how is it gonna play with
>>>> explicitly setting format/sampling rate to s16le/48k in sndcards drivers?
>
> be_hw_params_fixup callback in machine drivers can select any format
> that fits the usecase. currently this is hardcoded for s16le samples and
> 48K rate, but its not limited to this. This patch is expanding the
> allowed range in the dais so that machine drivers should be able to
> select other options, ex: for HDMI its better to be at S24LE or S32LE.
Yes. Exactly.
So, should we add kcontrols to machine driver to handle these usecases like
selecting s24le instead of s16le? Or what's the plan?
>>> Support for s16le/48k is already available; these patch will expand the
>>> existing constraint so that customers can use a wider range.
>>
>> Unfortunately, you didn't answer any of my questions or answered
>> a different one.
>>
>> Perhaps the main one: is q6dsp-lpass-ports involved in compress offloaded
>> playback on existing devices?
>
> lpass-ports are the Backend DAI ports, So yes, they will be involved in
> all the usecases that deal with handling sinks or sources irrespective
> of pcm or compressed content.
Thanks,
Alexey
prev parent reply other threads:[~2025-12-22 4:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 6:51 [PATCH v2 0/2] ASoC: qcom: q6dsp-lpass-ports: Expand sampling rate and PCM format constraints Ravi Hothi
2025-12-10 6:51 ` [PATCH v2 1/2] ASoC: qcom: q6dsp-lpass-ports: Extend q6dsp-lpass-ports driver to support additional sampling rates Ravi Hothi
2025-12-10 6:51 ` [PATCH v2 2/2] ASoC: qcom: q6dsp-lpass-ports: Update constraints to support 32-bit PCM format Ravi Hothi
2025-12-10 13:56 ` [PATCH v2 0/2] ASoC: qcom: q6dsp-lpass-ports: Expand sampling rate and PCM format constraints Alexey Klimov
2025-12-15 7:29 ` Ravi Hothi
2025-12-17 11:38 ` Alexey Klimov
2025-12-17 12:56 ` Srinivas Kandagatla
2025-12-22 4:25 ` Alexey Klimov [this message]
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=DF4GKIYJPDKA.DTLON4U0AZHB@linaro.org \
--to=alexey.klimov@linaro.org \
--cc=ajay.nandam@oss.qualcomm.com \
--cc=broonie@kernel.org \
--cc=kernel@oss.qualcomm.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mohammad.rafi.shaik@oss.qualcomm.com \
--cc=perex@perex.cz \
--cc=ravi.hothi@oss.qualcomm.com \
--cc=srini@kernel.org \
--cc=srinivas.kandagatla@oss.qualcomm.com \
--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;
as well as URLs for NNTP newsgroup(s).