From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 205841] Lenovo USB-C dock audio NULL pointer
Date: Thu, 12 Dec 2019 08:23:50 +0000 [thread overview]
Message-ID: <bug-205841-208809-hk9UBQwetr@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205841-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205841
Heikki Krogerus (heikki.krogerus@linux.intel.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |heikki.krogerus@linux.intel
| |.com
--- Comment #4 from Heikki Krogerus (heikki.krogerus@linux.intel.com) ---
The NULL pointer is coming from UCSI driver, and it should not have any effect
on audio. UCSI is a firmware interface that we use just for reading the status
of the USB Type-C connectors. The firmware does all the actual negotiation with
the partner device, so the Dock in this case. Which dock is it?
I'll see if I can reproduce the NULL pointer dereference, but you can just
disable the UCSI drivers in your kernel configuration to get rid of it. Any
issues with the audio should not be related to it.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-12-12 8:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 7:19 [Bug 205841] New: Lenovo USB-C dock audio NULL pointer bugzilla-daemon
2019-12-12 7:20 ` [Bug 205841] " bugzilla-daemon
2019-12-12 7:34 ` bugzilla-daemon
2019-12-12 7:37 ` bugzilla-daemon
2019-12-12 8:23 ` bugzilla-daemon [this message]
2019-12-12 8:48 ` bugzilla-daemon
2019-12-12 8:58 ` bugzilla-daemon
2019-12-12 8:59 ` bugzilla-daemon
2019-12-27 10:01 ` bugzilla-daemon
2019-12-27 10:56 ` bugzilla-daemon
2020-04-14 19:56 ` bugzilla-daemon
2020-04-15 13:56 ` bugzilla-daemon
2020-04-15 14:08 ` 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-205841-208809-hk9UBQwetr@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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;
as well as URLs for NNTP newsgroup(s).