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: Thu, 03 Mar 2016 08:16:06 +0100	[thread overview]
Message-ID: <8737s8uj49.fsf@gmail.com> (raw)
In-Reply-To: <CADjb_WQQdrFFpyRghk=nvZKeXA_ZY_dCYbEDtVGrEEk0LhVN=w@mail.gmail.com>

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.

Best,

Tamas

  reply	other threads:[~2016-03-03  7:16 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
2016-03-02 14:44     ` yu chen
2016-03-03  7:16       ` Tamas Papp [this message]
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=8737s8uj49.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).