linux-kernel - Re: `ucsi_acpi: probe of USBC000:00 failed with error -12` on Dell XPS 13 9360/9370

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20180518212857.GA21732@kuha.fi.intel.com>
Date:   Sat, 19 May 2018 00:28:57 +0300
From:   Heikki Krogerus <heikki.krogerus@...ux.intel.com>
To:     "Rafael J. Wysocki" <rafael@...nel.org>
Cc:     "Rafael J. Wysocki" <rjw@...ysocki.net>,
        Paul Menzel <pmenzel+linux-usb@...gen.mpg.de>,
        Mario Limonciello <mario.limonciello@...l.com>,
        "open list:ULTRA-WIDEBAND (UWB) SUBSYSTEM:" 
        <linux-usb@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Thorsten Leemhuis <linux@...mhuis.info>,
        ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: `ucsi_acpi: probe of USBC000:00 failed with error -12` on Dell
 XPS 13 9360/9370

On Fri, May 18, 2018 at 10:04:02PM +0200, Rafael J. Wysocki wrote:
> On Fri, May 18, 2018 at 5:15 PM, Greg Kroah-Hartman
> > Given that Windows works with this same set of ACPI tables, perhaps the
> > requirement isn't that this memory location be uncached?
> >
> > We shouldn't have to fix up ACPI tables just for Linux, we've been down
> > that path before :(
> 
> Yes, pretty much.

That's not what I'm suggesting. AFAIK these Dell laptops are the only
ones with this problem, so if we accept this, I fear it means we have
to start maintaining DMI quirk table in the driver, and then:

if (dell)
        ioremap_cache()
else
        ioremap_nocache()

I was really hoping we could avoid that. Or is there something else we
can do in the driver?

I have no idea how the windows driver works, so I will double check
and test this next week, but our driver has really worked fine so far.


Thanks,

-- 
heikki