Re: STI problem and workaround for Dell XPS 13 (Skylake, 2016) / Broadcom BCM4350

[Tamas Papp <tkpapp@gmail.com>]

On Fri, Mar 04 2016, yu chen wrote:

> On Thu, Mar 3, 2016 at 3:16 PM, Tamas Papp <tkpapp@gmail.com> 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