From: <Mario.Limonciello@dell.com>
To: <heikki.krogerus@linux.intel.com>, <greg@kroah.com>,
<pmenzel+linux-usb@molgen.mpg.de>
Cc: <linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: `ucsi_acpi: probe of USBC000:00 failed with error -12` on Dell XPS 13 9370
Date: Wed, 16 May 2018 16:13:31 +0000 [thread overview]
Message-ID: <df6610738db046e9bd1db77d4346cfc3@ausx13mpc120.AMER.DELL.COM> (raw)
In-Reply-To: <20180516115814.GB11469@kuha.fi.intel.com>
> -----Original Message-----
> From: Heikki Krogerus [mailto:heikki.krogerus@linux.intel.com]
> Sent: Wednesday, May 16, 2018 6:58 AM
> To: Greg KH; Paul Menzel
> Cc: linux-usb@vger.kernel.org; linux-kernel@vger.kernel.org; Limonciello, Mario
> Subject: Re: `ucsi_acpi: probe of USBC000:00 failed with error -12` on Dell XPS 13
> 9370
>
> Hi,
>
> On Wed, May 16, 2018 at 10:02:26AM +0200, Greg KH wrote:
> > On Tue, May 15, 2018 at 06:47:37PM +0200, Paul Menzel wrote:
> > > Dear Greg,
> > >
> > >
> > > As always, thank you for the prompt response.
> > >
> > >
> > > On 05/15/18 18:00, Greg KH wrote:
> > > > On Tue, May 15, 2018 at 04:34:03PM +0200, Paul Menzel wrote:
> > >
> > > > > Linux 4.17-rc5 shows the error below on the Dell XPS 13 9370 with Debian
> > > > > Sid/unstable.
> > > > >
> > > > > ```
> > > > > [???]
> > > > > [ 0.440240] usb: port power management may be unreliable
> > > > > [ 0.441358] usbcore: registered new interface driver usb-storage
> > > > > [ 0.441367] usbcore: registered new interface driver usbserial_generic
> > > > > [ 0.441369] usbserial: USB Serial support registered for generic
> > > > > [ 0.441383] ioremap error for 0x3f799000-0x3f79a000, requested 0x2, got
> > > > > 0x0
> > > > > [ 0.441518] ucsi_acpi: probe of USBC000:00 failed with error -12
> > > > > [???]
> > > > > ```
> > > > >
> > > > > 1. Are the ioremap and ucsi_acpi error related or is a separate report
> > > > > needed?
> > > >
> > > > The ioremap error is what causes ucsi_acpi to fail the probe call (-12
> > > > is "out of memory".)
> > > >
> > > > > 2. Do you know the reason for the ucsi_acpi error?
> > > >
> > > > the call to ioremap failed.
> > > >
> > > > Does this device really have a working typec connector?
> > >
> > > Just to avoid misunderstandings, no device was connected to the laptop
> > > during my test.
> > >
> > > But, from other boots, the Dell docking station TB16 kind of works with it,
> > > so I???d say the USB Type-C connector is working.
> >
> > Ok, good, this might just be the acpi tables not set up properly for
> > this type of connection. Odd that the tables show it should work,
> > Heikki should know more about this.
>
> The firmware probable has not implemented UCSI on this board. I think
> Dell always supplies the ACPI device node for UCSI in their acpi
> tables. The _STA method in that device node is then used to inform the
> OS if the interface exists or not. The return value for _STA comes
> probable from BIOS, so this is most likely a BIOS problem.
Heikki,
I confirmed with internal team that UCSI is implemented on XPS 9370
and was confirmed to be working properly with Windows 10 RS2+.
The reason that _STA is responding on this device node now but wasn't
previously is it wasn't exposed in Linux until 4.16 when the Win 10 RS2
OSI string started to respond.
Intel should internally have some XPS 9370 you can remotely access if
you would like to poke around ACPI tables some.
>
> Please note that UCSI will only supply status information to the
> operating system, so the USB Type-C ports will function normally even
> without it. The ports are handled in firmware on these platforms.
>
> Paul, do you have the latest BIOS?
>
>
> > > > Does normal USB devices work with it?
> > >
> > > Sorry for being ignorant, but could you please tell me what normal USB
> > > devices are?
> >
> > If you plug a USB typeC device into this port, does it work? A docking
> > station is a little bit "different" in that it usually uses the PCIe
> > connection, not the USB connectors. Or at least that's how my Dell
> > docking station works last time I tried it[1]
I think the best description here is "Non-Thunderbolt" USB type C device.
Some examples:
There are Dell docking stations with Thunderbolt (TB16) or without (WD15).
You can also pick up little dongles for ethernet or combo dongles for
ethernet/VGA/HDMI/etc.
Anything non-Thunderbolt would satisfy what Greg was looking for.
> >
> > thanks,
> >
> > greg k-h
> >
> > [1] When the power supply for the docking station is bigger than the
> > laptop's power supply, you begin to wonder what is in that thing and
> > stop using it after a while...
Mostly to satisfy letting the docking station work with beefier machines and
still deliver power up to what USB PD will negotiate.
I think they can actually run with smaller power supplies but you will need
something "a little" bigger than regular system power supply to power the
dock and system both.
next prev parent reply other threads:[~2018-05-16 16:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 14:34 Paul Menzel
2018-05-15 16:00 ` Greg KH
2018-05-15 16:47 ` Paul Menzel
2018-05-16 8:02 ` Greg KH
2018-05-16 11:58 ` Heikki Krogerus
2018-05-16 12:35 ` Paul Menzel
2018-05-16 15:03 ` Mario.Limonciello
2018-05-16 16:13 ` Mario.Limonciello [this message]
2018-05-16 16:39 ` Greg KH
2018-05-17 8:59 ` Heikki Krogerus
2018-05-17 13:01 ` Mario.Limonciello
2018-05-17 13:58 ` Heikki Krogerus
2018-05-17 13:34 ` `ucsi_acpi: probe of USBC000:00 failed with error -12` on Dell XPS 13 9360/9370 Paul Menzel
2018-05-18 10:40 ` Heikki Krogerus
2018-05-18 15:08 ` Heikki Krogerus
2018-05-18 15:15 ` Greg Kroah-Hartman
2018-05-18 20:04 ` Rafael J. Wysocki
2018-05-18 21:28 ` Heikki Krogerus
2018-06-04 9:24 `ucsi_acpi: probe of USBC000:00 failed with error -12` on Dell XPS 13 9370 Kacper Pluta
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=df6610738db046e9bd1db77d4346cfc3@ausx13mpc120.AMER.DELL.COM \
--to=mario.limonciello@dell.com \
--cc=greg@kroah.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pmenzel+linux-usb@molgen.mpg.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
all inboxes | Powered by JetHome®