linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Oliver Neukum <oneukum@suse.de>
Cc: linux-usb@vger.kernel.org
Subject: Re: No PNP0CA0 device on a Dell Precision 5520 laptop
Date: Tue, 11 Feb 2020 16:44:29 +0200	[thread overview]
Message-ID: <20200211144429.GD1498@kuha.fi.intel.com> (raw)
In-Reply-To: <1581431677.1580.7.camel@suse.de>

On Tue, Feb 11, 2020 at 03:34:37PM +0100, Oliver Neukum wrote:
> Am Dienstag, den 11.02.2020, 16:28 +0200 schrieb Heikki Krogerus:
> > On Tue, Feb 11, 2020 at 03:14:10PM +0100, Oliver Neukum wrote:
> > > Am Dienstag, den 11.02.2020, 15:59 +0200 schrieb Heikki Krogerus:
> > > > cat /sys/bus/acpi/devices/USBC000\:00/status
> > > 
> > > Technically -ENODEV. It does not exist, even in a listing.
> > > But this thing definitely has a type C port. It is connected
> > > to a docking station which supplies the whole system with power.
> > > Ethernet also works.
> > 
> > There is still no requirement for the BIOS or the EC firmware to
> > expose UCSI to the operating system. If the ACPI node is not there,
> > then there is no UCSI on that system. The USB Type-C connectors
> > function autonomously in any case on a system that exposes them to the
> > operating system with UCSI. UCSI is more like an optional status
> > interface that allows limited control over some specific things like
> > role swapping.
> > 
> > UCSI is usually supported when the USB Power Delivery (USB PD)
> > controllers are connected to the Embedded Controller on the system,
> > but on some of our platforms they are directly connected to the SOC
> > instead. So on those platforms we can directly communicate with the
> > USB PD controller from the operating system, which is actually much
> > better situation compared to UCSI IMO.
> > 
> > Do you have this ACPI node: INT3515 ?
> > 
> > It's for the TI TPS6598x USB PD controllers.
> 
> Hi,
> 
> yes I got that one. Thanks for the tip.

OK, cool! Let me know if the tps6598x.c driver works with that.

thanks,

-- 
heikki

  reply	other threads:[~2020-02-11 14:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 13:25 No PNP0CA0 device on a Dell Precision 5520 laptop Oliver Neukum
2020-02-11 13:59 ` Heikki Krogerus
2020-02-11 14:14   ` Oliver Neukum
2020-02-11 14:28     ` Heikki Krogerus
2020-02-11 14:34       ` Oliver Neukum
2020-02-11 14:44         ` Heikki Krogerus [this message]
2020-02-11 15:09           ` Oliver Neukum
2020-02-12 13:12           ` Oliver Neukum
2020-02-12 16:06             ` Heikki Krogerus
2020-02-13  7:27               ` Oliver Neukum
2020-02-11 16:09       ` Oliver Neukum

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=20200211144429.GD1498@kuha.fi.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.de \
    /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).