From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: johan+linaro@kernel.org, perex@perex.cz, tiwai@suse.com,
lgirdwood@gmail.com, ckeepax@opensource.cirrus.com,
kuninori.morimoto.gx@renesas.com, linux-kernel@vger.kernel.org,
pierre-louis.bossart@linux.intel.com,
alsa-devel@alsa-project.org, Stable@vger.kernel.org
Subject: Re: [PATCH] ASoC: qdsp6: q6apm: use dai link pcm id as pcm device number
Date: Fri, 30 Jun 2023 06:42:42 +0100 [thread overview]
Message-ID: <5fe3cbfe-645a-185b-9c88-5da56cfd7114@linaro.org> (raw)
In-Reply-To: <8c3be94e-56c0-4820-853d-669e90969c24@sirena.org.uk>
On 29/06/2023 18:42, Mark Brown wrote:
> On Thu, Jun 29, 2023 at 06:33:09PM +0100, Srinivas Kandagatla wrote:
>> On 29/06/2023 16:43, Mark Brown wrote:
>>> On Wed, Jun 28, 2023 at 10:24:04AM +0100, Srinivas Kandagatla wrote:
>
>>>> For some reason we ended up with a setup without this flag.
>>>> This resulted in inconsistent sound card devices numbers which
>>>> are also not starting as expected at dai_link->id.
>>>> (Ex: MultiMedia1 pcm ended up with device number 4 instead of 0)
>
>>> Why is this a problem?
>
>> In existing Qualcomm setup the backend pcm are added first, which results in
>> frontend pcms getting pcm numbers after this.
>
>> For example: with 3 backend dailinks in DT we have frontend pcm start at 3.
>> Now if we add new backend dai-link in DT we now have frontend pcm start at
>> 4.
>
>> This is a bug in qualcomm driver.
>
> Why is this an actual problem rather than just being a bit ugly? What
> is the negative consequence of having a PCM with this number?
Yes, it is ugly but also breaks the existing UCM as the pcm device
numbers keep changing.
Which is why I refereed it as bug in the driver.
--srini
next prev parent reply other threads:[~2023-06-30 5:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 9:24 Srinivas Kandagatla
2023-06-29 15:43 ` Mark Brown
2023-06-29 16:06 ` Greg KH
2023-06-29 16:16 ` Mark Brown
2023-06-29 17:22 ` Greg KH
2023-06-29 17:38 ` Mark Brown
2023-06-29 18:48 ` Greg KH
2023-06-29 21:23 ` Mark Brown
2023-06-29 17:33 ` Srinivas Kandagatla
2023-06-29 17:42 ` Mark Brown
2023-06-30 5:42 ` Srinivas Kandagatla [this message]
2023-06-30 17:07 ` Mark Brown
2023-07-03 7:48 ` Johan Hovold
2023-07-03 8:03 ` Johan Hovold
2023-07-03 8:19 ` Takashi Iwai
2023-07-03 8:48 ` Johan Hovold
2023-07-03 12:21 ` Johan Hovold
2023-07-03 11:56 ` Mark Brown
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=5fe3cbfe-645a-185b-9c88-5da56cfd7114@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=Stable@vger.kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=johan+linaro@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.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
all inboxes | Powered by JetHome®