From: "Alexey Klimov" <alexey.klimov@linaro.org>
To: "Srinivas Kandagatla" <srinivas.kandagatla@oss.qualcomm.com>,
<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: Mon, 22 Dec 2025 04:19:38 +0000 [thread overview]
Message-ID: <DF4GG97LYALC.1YRQN14DFQJPP@linaro.org> (raw)
In-Reply-To: <fb7ea0ab-d75a-4716-93dc-08545fdb1677@oss.qualcomm.com>
On Tue Dec 16, 2025 at 5:48 AM GMT, Srinivas Kandagatla wrote:
> 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.
Yep, now I am starting to recall. I just thought that it was fixed.
Port mismatch messages is also present on other boards too.
Thanks.
Best regards,
Alexey
prev parent reply other threads:[~2025-12-22 4:19 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
2025-12-22 4:19 ` 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=DF4GG97LYALC.1YRQN14DFQJPP@linaro.org \
--to=alexey.klimov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=srini@kernel.org \
--cc=srinivas.kandagatla@oss.qualcomm.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).