From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218992] Usb Type-C headset TX is noise
Date: Thu, 27 Jun 2024 10:24:48 +0000 [thread overview]
Message-ID: <bug-218992-208809-i09yt2HdeH@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218992-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218992
--- Comment #2 from Udipto (quic_ugoswami@quicinc.com) ---
One more info:
Looking at endpoint.c code I think the function snd_usb_endpoint_open extracts
the ep->clock_ref using clock_ref_find(chip, fp->clock) and this remains same
for all endpoints available.
In the issue case when the error mismatch sample rate comes up, looks like the
ep->clock_ref->opened is 2, and it will not decrease to 0 when we close EP 0x82
because EP 0x1 is opened. Also the clock_ref->rate will not go to 0 when close
EP 0x82.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-06-27 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 10:04 [Bug 218992] New: headset bugzilla-daemon
2024-06-27 10:11 ` [Bug 218992] Usb Type-C headset TX is noise bugzilla-daemon
2024-06-27 10:24 ` bugzilla-daemon [this message]
2024-06-27 10:25 ` bugzilla-daemon
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=bug-218992-208809-i09yt2HdeH@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@vger.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