From: <Mario.Limonciello@dell.com>
To: <heikki.krogerus@linux.intel.com>, <whitequark@whitequark.org>,
<mika.westerberg@linux.intel.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: USB type-C altmode support for UCSI
Date: Wed, 5 Sep 2018 13:50:03 +0000 [thread overview]
Message-ID: <4df3faaee8904d81bf7737b5f2daaff5@ausx13mpc120.AMER.DELL.COM> (raw)
In-Reply-To: <20180905132429.GB25121@kuha.fi.intel.com>
> > (There's also an UCSI bug where no notifications appear when connecting
> > a device, only when disconnecting and only once, but it can be worked
> > around by reloading the module, so it isn't critical. Not sure what's up
> > with that either.)
>
> This is indeed a separate issue, and you are the second person that
> reports it. Either the (EC) firmware on those laptops is not
> generating the connection event as is should for some reason, or the
> EC driver in Linux kernel fails to deliver the event to the UCSI
> driver. I don't have XPS 13 that I could use to reproduce the issue
> unfortunately.
>
> Mario! Can you help with this?
>
I need to know which system this was and which BIOS FW package to try to reproduce
if I can pass this to the right people, 9360/9370? Current FW?
Is this happening with all type-C devices? Or just Thunderbolt? Or (worse) just that
TBT device?
next prev parent reply other threads:[~2018-09-05 13:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1e8398f2c1790890f40b69f12e2934e3@whitequark.org>
[not found] ` <20180903140623.GD15112@kuha.fi.intel.com>
[not found] ` <28522bb57c5d8f49416b9174b19b1625@whitequark.org>
2018-09-05 13:24 ` Heikki Krogerus
2018-09-05 13:34 ` Mika Westerberg
2018-09-05 13:50 ` Mario.Limonciello [this message]
2018-09-05 14:13 ` whitequark
2018-09-07 11:04 ` whitequark
2018-09-10 21:25 ` Mario.Limonciello
2018-09-11 9:32 ` Mika Westerberg
2018-09-11 13:02 ` Mario.Limonciello
2018-10-06 6:01 ` A different PD controller firmware problem? Theodore Y. Ts'o
2018-11-08 18:00 ` Mario.Limonciello
2018-11-08 21:15 ` Theodore Y. Ts'o
2018-11-10 20:13 ` Theodore Y. Ts'o
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=4df3faaee8904d81bf7737b5f2daaff5@ausx13mpc120.AMER.DELL.COM \
--to=mario.limonciello@dell.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=whitequark@whitequark.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
all inboxes | Powered by JetHome®