public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Paul Menzel <pmenzel+linux-usb@molgen.mpg.de>
Cc: Mario Limonciello <mario.limonciello@dell.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	Thorsten Leemhuis <linux@leemhuis.info>
Subject: Re: `ucsi_acpi: probe of USBC000:00 failed with error -12` on Dell XPS 13 9360/9370
Date: Fri, 18 May 2018 13:40:00 +0300	[thread overview]
Message-ID: <20180518104000.GA13595@kuha.fi.intel.com> (raw)
In-Reply-To: <40707f34-e0a6-3114-36a3-6603bdcd8d82@molgen.mpg.de>

Hi Paul,

On Thu, May 17, 2018 at 03:34:49PM +0200, Paul Menzel wrote:
> Dear Heikki,
> 
> Note, this problem also exists on the Dell XPS 13 9360 (Kaby Lake) device.

OK. Good to know. Though, we don't have one of those either.

> On 05/17/18 10:59, Heikki Krogerus wrote:
> > On Wed, May 16, 2018 at 04:13:31PM +0000, Mario.Limonciello@dell.com wrote:
> > > 
> > > 
> > > > -----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+.
> > 
> > Just to double check: "UCSI was confirmed working properly", so not
> > "the Type-C ports were confirmed working properly"?
> > 
> > > 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.
> > 
> > OK.
> > 
> > > Intel should internally have some XPS 9370 you can remotely access if
> > > you would like to poke around ACPI tables some.
> > 
> > I will try get access to XPS 9370, but with the acpi tables, if
> > somebody could just send me acpidump, that would be enough:
> > 
> >          % acpidump -o xps9370_acpi.dump
> 
> I uploaded them to another bug report [1]. Please find it attached.

Thanks!


Br,

-- 
heikki

  reply	other threads:[~2018-05-18 10:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 14:34 `ucsi_acpi: probe of USBC000:00 failed with error -12` on Dell XPS 13 9370 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
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 [this message]
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

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=20180518104000.GA13595@kuha.fi.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=mario.limonciello@dell.com \
    --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