From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tamas Papp Subject: Re: STI problem and workaround for Dell XPS 13 (Skylake, 2016) / Broadcom BCM4350 Date: Fri, 04 Mar 2016 08:36:13 +0100 Message-ID: <87bn6ubspe.fsf@gmail.com> References: <87h9gpp5rt.fsf@gmail.com> <87a8mhotmk.fsf@gmail.com> <8737s8uj49.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from mail-wm0-f49.google.com ([74.125.82.49]:38056 "EHLO mail-wm0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751557AbcCDHgQ (ORCPT ); Fri, 4 Mar 2016 02:36:16 -0500 Received: by mail-wm0-f49.google.com with SMTP id l68so18578550wml.1 for ; Thu, 03 Mar 2016 23:36:16 -0800 (PST) In-reply-to: Sender: linux-pm-owner@vger.kernel.org List-Id: linux-pm@vger.kernel.org To: yu chen Cc: linux-pm@vger.kernel.org On Fri, Mar 04 2016, yu chen wrote: > On Thu, Mar 3, 2016 at 3:16 PM, Tamas Papp wrote: >> On Wed, Mar 02 2016, yu chen wrote: >> >>> Currently the 0000:3c and 0000:3a might have the same pnp object name PXSX, >>> unfortunately the 'echo' will find the first math device in the >>> wakable list, and maybe >>> 0000:3c was probed before 0000:3a, so... maybe this is a weakness. >>> >>> Maybe you can disabled the wakable feature directly in device sysfs, >>> for example, >>> echo 0 > /sys/devices/pci0000:00/0000:3a:00.0/power/wakeup, >>> you might need to find out where 0000:3a:00.0 is. >> >> I tried that, but the module has problems after wakeup. I have to remove >> and insert it again with modprobe. >> >> Still, this is an OK workaround, thanks for the help. I still don't know >> if I should file this as a bug, and if yes, where. >> > Does the following fix make sense for you: > > cat /proc/acpi/wakeup > PXSX:0 S4 *enabled pci:0000:3a:00.0 > then you need to echo PXSX:0 to disable it, > and for 3c, it would be PXSX:1 Sorry, I am confused --- is this a proposed new syntax for /proc/acpi/wakeup? I guess this could work. BTW, for kernel 4.4.3, I don't need any fix (that's what I am using now), it works out of the box, I just need to fiddle with the broadcom module in 4.5.0-rc6. Best, Tamas