From: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
To: Alexey Klimov <alexey.klimov@linaro.org>,
srini@kernel.org, linux-arm-msm@vger.kernel.org
Cc: linux-sound@vger.kernel.org
Subject: Re: [linux-next] (new?) audio issues on Qualcomm sm8550
Date: Tue, 16 Dec 2025 05:48:46 +0000 [thread overview]
Message-ID: <fb7ea0ab-d75a-4716-93dc-08545fdb1677@oss.qualcomm.com> (raw)
In-Reply-To: <DEVENUXSAUMM.1DMQ7M0ASXSDV@linaro.org>
Thanks Alexey for reporting this
On 12/11/25 1:01 PM, Alexey Klimov wrote:
> Hi all,
>
> I am reporting new errors here because I soon lose access to some devices.
> Please let me know what is the proper way to report this if this is not the right
> thing to do.
>
> I've started to see new errors on sm8550-qrd for a while now with recent linux-nexts:
> (also reproduced with today's next-20251211)
>
> qcom-soundwire 6d30000.soundwire: dout-ports (0) mismatch with controller (1)
I think we discussed this briefly in this thread
https://www.spinics.net/lists/devicetree/msg837844.html
This is very much the expected behavior. There is a bug in the dt entry
of 6d30000.soundwire controller, which missed dout port in frame shaping
data.
> wcd938x_codec audio-codec: bound sdw:2:0:0217:010d:00:4 (ops wcd_sdw_component_ops [snd_soc_wcd_common])
> wcd938x_codec audio-codec: bound sdw:3:0:0217:010d:00:3 (ops wcd_sdw_component_ops [snd_soc_wcd_common])
> wsa_macro 6b00000.codec: using zero-initialized flat cache, this may cause unexpected behavior
> snd-sc8280xp sound: ASoC: Parent card not yet available, widget card binding deferred
> va_macro 6d44000.codec: supply vdd-micb not found, using dummy regulator
> wcd938x_codec audio-codec: Impedance detect ramp error, c1=0, x1=0x0
> wcd938x_codec audio-codec: Impedance detect ramp error, c1=0, x1=0x0
> wcd938x_codec audio-codec: Impedance detect ramp error, c1=0, x1=0x0
>
> I also think that changing volume via 'WSA_RX{0,1} Digital Volume' no longer works. It used to work before.
> Impedance ramp error seems to occur occasionaly, I don't think this one is critical.
this is interesting, I can try to reproduce that.
--srini>
> Best regards,
> Alexey
>
next prev parent reply other threads:[~2025-12-16 5:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 13:01 [linux-next] (new?) audio issues on Qualcomm sm8550 Alexey Klimov
2025-12-16 5:48 ` Srinivas Kandagatla [this message]
2025-12-22 4:19 ` Alexey Klimov
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=fb7ea0ab-d75a-4716-93dc-08545fdb1677@oss.qualcomm.com \
--to=srinivas.kandagatla@oss.qualcomm.com \
--cc=alexey.klimov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=srini@kernel.org \
/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