Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp3256196imm; Thu, 17 May 2018 06:03:24 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqupjPT7IPVVcpJel6EOGCwXto8CXSOptM8VVH50LAe8P9myFcWJwS5EBjpyw/8KMaR6Nic X-Received: by 2002:a65:6250:: with SMTP id q16-v6mr4120916pgv.113.1526562204405; Thu, 17 May 2018 06:03:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526562204; cv=none; d=google.com; s=arc-20160816; b=J+F3r9gy7qGmvSlKaZ/ORLm8K+bi9mRe5W6LW4ijtFzXZJdm/DMNZWedWgD4dEGbOo hlzSo4hEbt6JS7TBn9fYg/Mau1RpolYVY5AzwBOOn4J/511kOOaUO7RI8EOj3Psn3f9O pJ9f27pe/v8SrVVXCY/ueePJsU8fVk2Ja1HANP91TEoyC5ZnW401Z5ghWFbf5xc63PnP hVPW58Xf7+1X6R5ZmC2p+NdQ+JY55YtfFmdnEDS64Oc6DCZ5GRlmvzWgr8GVCB5GFho1 /lhM4UGZ+yV3JDwbw0RGwFmdkFMfsoZ7Lfdwsd4wXSLj+o+oQIHCl1dvMnAWX1GZAZ2C EuQw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :content-language:accept-language:in-reply-to:references:message-id :date:thread-index:thread-topic:subject:cc:to:from:dkim-signature :arc-authentication-results; bh=G+k9xkQljlgFkbxF6BRwo0NsWm/c845gUnjg1+MC76A=; b=faVY6TvStbUu3RaaztGurhYmAeSjQ7OK9/WlpOL8Wi70bxBIVgVkTUy365aO1vwlLJ 101Lirc6MZPwjj1qLBgKqBEpX/GG61PH1ttqSx4PZEQGTrTzjEqMl0E8T6KQ5Pt3J7oO 4PA8wYCAhzp+ccdm9DDdj1cwgiqcb5Ot47WD1rGt03waMxZv0J04mWB92hQyUhS34s+E nl8SwPnESzR0VKnFdRhgml9h1QtmaRu05ZsbFrF0kuHqJTSaOr6rCNmVg/26M5xU0j0Z pfVa2WQVkxoJeEoxkBxy1+FtdwJFVkhDLabqgAFy6ewEF1WULj8bgw0VI45wxdISowHt bmUA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@dell.com header.s=smtpout header.b=JnQan3Lx; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=dell.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 3-v6si5216854plh.34.2018.05.17.06.02.58; Thu, 17 May 2018 06:03:24 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@dell.com header.s=smtpout header.b=JnQan3Lx; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=dell.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752062AbeEQNB2 (ORCPT + 99 others); Thu, 17 May 2018 09:01:28 -0400 Received: from esa8.dell-outbound.iphmx.com ([68.232.149.218]:20820 "EHLO esa8.dell-outbound.iphmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751457AbeEQNBY (ORCPT ); Thu, 17 May 2018 09:01:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1526562084; x=1558098084; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Si/wsxV+ioMipRfY2SVr9P+Np4gStd9yR5KNzsbyYjE=; b=JnQan3LxPprbAWcOvXhdJIQB9z6pexboYv85A+fh7VLNRzcs442Yk1xD cZz5RB6jVIHmu5UAzbNxBcLtl1axxo02OTmmYhNUjnweU1vgIb6Y/C8ed GJXGkZpPv/jLPAi6HlFgAwv4CiVeqhOpF9eCaSoTdEzUEq+mJ+5tEe16I c=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2EQAQCMeP1amGKa6ERcGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYQWgQsoCphlgXmBD5NKgWQLhGwCghAhOBQBAgEBAQEBAQIBAQI?= =?us-ascii?q?QAQEBAQEICwsGKC+CNSKCUwEBAQMBOj8MBAIBCBEEAQEBHgkHRgMBBQgCBA4FC?= =?us-ascii?q?BaDBYF5CKkOiEyCJ4gughOBD4MMgUGCehwIhWgChxsZLIVgg1KHNgcChleHdYE?= =?us-ascii?q?/g2qHVyuFTIp7gSUzgXRwgxOCIA4JjhdvAY1bgS2BGAEB?= X-IPAS-Result: =?us-ascii?q?A2EQAQCMeP1amGKa6ERcGQEBAQEBAQEBAQEBAQcBAQEBAYQ?= =?us-ascii?q?WgQsoCphlgXmBD5NKgWQLhGwCghAhOBQBAgEBAQEBAQIBAQIQAQEBAQEICwsGK?= =?us-ascii?q?C+CNSKCUwEBAQMBOj8MBAIBCBEEAQEBHgkHRgMBBQgCBA4FCBaDBYF5CKkOiEy?= =?us-ascii?q?CJ4gughOBD4MMgUGCehwIhWgChxsZLIVgg1KHNgcChleHdYE/g2qHVyuFTIp7g?= =?us-ascii?q?SUzgXRwgxOCIA4JjhdvAY1bgS2BGAEB?= Received: from esa4.dell-outbound2.iphmx.com ([68.232.154.98]) by esa8.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 May 2018 08:01:22 -0500 From: Received: from ausc60pc101.us.dell.com ([143.166.85.206]) by esa4.dell-outbound2.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 May 2018 19:01:21 +0600 X-LoopCount0: from 10.166.132.190 X-IronPort-AV: E=Sophos;i="5.49,390,1520917200"; d="scan'208";a="1252252013" X-DLP: DLP_GlobalPCIDSS To: CC: , , , Subject: RE: `ucsi_acpi: probe of USBC000:00 failed with error -12` on Dell XPS 13 9370 Thread-Topic: `ucsi_acpi: probe of USBC000:00 failed with error -12` on Dell XPS 13 9370 Thread-Index: AQHT7FnacruSscNvFUKixxVl6UQN9aQxRuSAgAANFYCAAP+ZAIAAQeIA///t/DCAAXJpAP//7vrw Date: Thu, 17 May 2018 13:01:20 +0000 Message-ID: <91a3c211cc8547ccb8eab844abd3b095@ausx13mpc120.AMER.DELL.COM> References: <9365397f-7206-728e-ee76-146629bfd186@molgen.mpg.de> <20180515160047.GB26720@kroah.com> <69da4aa4-3d4b-0ffc-81ce-500713cd3743@molgen.mpg.de> <20180516080226.GC3536@kroah.com> <20180516115814.GB11469@kuha.fi.intel.com> <20180517085930.GD11469@kuha.fi.intel.com> In-Reply-To: <20180517085930.GD11469@kuha.fi.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.143.18.86] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > -----Original Message----- > From: Heikki Krogerus [mailto:heikki.krogerus@linux.intel.com] > Sent: Thursday, May 17, 2018 4:00 AM > To: Limonciello, Mario > Cc: greg@kroah.com; pmenzel+linux-usb@molgen.mpg.de; linux- > usb@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: Re: `ucsi_acpi: probe of USBC000:00 failed with error -12` on De= ll XPS 13 > 9370 >=20 > Hi, >=20 > On Wed, May 16, 2018 at 04:13:31PM +0000, Mario.Limonciello@dell.com wrot= e: > > > > > > > -----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; Limoncie= llo, Mario > > > Subject: Re: `ucsi_acpi: probe of USBC000:00 failed with error -12` o= n 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-s= torage > > > > > > > [ 0.441367] usbcore: registered new interface driver usbse= rial_generic > > > > > > > [ 0.441369] usbserial: USB Serial support registered for g= eneric > > > > > > > [ 0.441383] ioremap error for 0x3f799000-0x3f79a000, reque= sted 0x2, > got > > > > > > > 0x0 > > > > > > > [ 0.441518] ucsi_acpi: probe of USBC000:00 failed with err= or -12 > > > > > > > [???] > > > > > > > ``` > > > > > > > > > > > > > > 1. Are the ioremap and ucsi_acpi error related or is a separ= ate report > > > > > > > needed? > > > > > > > > > > > > The ioremap error is what causes ucsi_acpi to fail the probe ca= ll (-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 l= aptop > > > > > during my test. > > > > > > > > > > But, from other boots, the Dell docking station TB16 kind of work= s 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 fo= r > > > > 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 th= e > > > 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+. >=20 > Just to double check: "UCSI was confirmed working properly", so not > "the Type-C ports were confirmed working properly"? UCSI was confirmed working properly. FWIW it's a certification requirement in Windows. >=20 > > 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. >=20 > OK. >=20 > > Intel should internally have some XPS 9370 you can remotely access if > > you would like to poke around ACPI tables some. >=20 > I will try get access to XPS 9370, but with the acpi tables, if > somebody could just send me acpidump, that would be enough: >=20 > % acpidump -o xps9370_acpi.dump >=20 > > > 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 norma= l USB > > > > > devices are? > > > > > > > > If you plug a USB typeC device into this port, does it work? A doc= king > > > > station is a little bit "different" in that it usually uses the PCI= e > > > > 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 devic= e. > > Some examples: > > There are Dell docking stations with Thunderbolt (TB16) or without (WD1= 5). > > > > 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. >=20 > Anything non-Thunderbolt and non-display. >=20 > With the display adapters you would be in DisplayPort alternate mode, > and you would again not be testing a normal USB device. >=20 > It never hurts to check that, but I think it's safe to assume that the > ports are functioning normally if the Thunderbolt dock was working. > Unless I'm mistaken, even the xHCI USB host controller behind the > USB Type-C (thunderbolt) ports is actually part of the thunderbolt > controller. In this laptop yes that's true, but isn't a general statement. It's possibl= e to have USB split mode (ie XHCI comes from PCH).