linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tamas Papp <tkpapp@gmail.com>
To: yu chen <yu.chen.surf@gmail.com>
Cc: linux-pm@vger.kernel.org
Subject: Re: STI problem and workaround for Dell XPS 13 (Skylake, 2016) / Broadcom BCM4350
Date: Wed, 02 Mar 2016 15:13:23 +0100	[thread overview]
Message-ID: <87a8mhotmk.fsf@gmail.com> (raw)
In-Reply-To: <CADjb_WQwwGD4wQugeLf=2k7XjtPGt9o6vgqhMdLR+ALDhK7J+Q@mail.gmail.com>

On Wed, Mar 02 2016, yu chen wrote:

> On Wed, Mar 2, 2016 at 5:51 PM, Tamas Papp <tkpapp@gmail.com> wrote:
>> Hi,
>>
>> I have a Dell XPS 13 (Skylake, 2016) and wanted to get STI working, so I
>> followed the instructions at [1]. I found that the Broadcom wireless
>> chip is waking the machine up from STI / freeze.
>>
>> A workaround is
>>
>> INTERFACE=wlp58s0
>> ifconfig $INTERFACE down
>> modprobe -r brcmfmac && echo freeze > /sys/power/state && modprobe brcmfmac
>> ifconfig $INTERFACE up
>>
>> I thought I would ask whether I should report this as a bug, and if yes,
>> where.
>>
> Some device drivers such as brcmac has the ability to wake the system
> up,  you can
> disable it by echo to /proc/acpi/wakeup IMO.

That's what I attempted first, but echo to /proc/acpi/wakeup just makes
the entry occur _twice_ -- what am I doing wrong?

root@tamas:~# cat /proc/acpi/wakeup | grep ena
PXSX      S4    *enabled   pci:0000:3a:00.0
PBTN      S3    *enabled   platform:PNP0C0C:00
root@tamas:~# echo PXSX > /proc/acpi/wakeup 
root@tamas:~# cat /proc/acpi/wakeup | grep ena
PXSX      S4    *enabled   pci:0000:3c:00.0
PXSX      S4    *enabled   pci:0000:3a:00.0
PBTN      S3    *enabled   platform:PNP0C0C:00
root@tamas:~# uname -r
4.5.0-040500rc6-generic

Best,

Tamas

  reply	other threads:[~2016-03-02 14:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02  9:51 STI problem and workaround for Dell XPS 13 (Skylake, 2016) / Broadcom BCM4350 Tamas Papp
2016-03-02 13:08 ` yu chen
2016-03-02 14:13   ` Tamas Papp [this message]
2016-03-02 14:44     ` yu chen
2016-03-03  7:16       ` Tamas Papp
2016-03-04  1:41         ` yu chen
2016-03-04  7:30           ` yu chen
2016-03-04  7:36           ` Tamas Papp
2016-03-04  7:49             ` yu chen

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=87a8mhotmk.fsf@gmail.com \
    --to=tkpapp@gmail.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=yu.chen.surf@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).