All of lore.kernel.org
 help / color / mirror / Atom feed
From: vichy <vichy.kuo@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-pm@vger.kernel.org
Subject: Re: Auto suspend not working on usb hid devices
Date: Mon, 12 Jan 2015 18:45:21 +0800	[thread overview]
Message-ID: <CAOVJa8HHwa-ZmwqgBozVuwWUZaBiVHb3-81sn3tOOp0_x5HNGw@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1501111049520.31181-100000@netrider.rowland.org>

hi alan:

2015-01-11 23:53 GMT+08:00 Alan Stern <stern@rowland.harvard.edu>:
> On Sun, 11 Jan 2015, vichy wrote:
>
>> hi all:
>> I list below environment I have that autosuspend seems doesn't work on
>> my platform.
>> 1. kernel version 3.10.30
>> 2. compile kernel with CONFIG_PM_RUNTIME=y
>> 3. "echo 'rpm:rpm_suspend' > set_event"
>> 4. insert hid devices and "echo auto > /sys/bus/usb/devices/6-1/power/control"
>> 5. there is no any usb related runtime suspend output in trace.
>>
>> Did I miss any kernel configuration to let it work?
>> Or where is the proper debug entry I can check why rpm_suspend isn't
>> been called on my system?
>
> There are lots of reasons why a device might not be runtime suspended.
> There is no single debug entry that presents them.  Some information
> can be seen in the files in the device's /sys/.../power directory.

I found the power/runtime_usage = 2 when device plug in and do nothing.
Except update_autosuspend will increase runtime_usage, is there any
function will increase it when we did not enable runtime
suspend/resume?

Thanks for your kind help,

  reply	other threads:[~2015-01-12 10:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-11 13:23 Auto suspend not working on usb hid devices vichy
2015-01-11 15:53 ` Alan Stern
2015-01-12 10:45   ` vichy [this message]
2015-01-12 12:45     ` vichy
2015-01-12 15:18       ` Alan Stern
2015-01-13  9:35         ` vichy
2015-01-13 12:11           ` vichy
2015-01-13 15:37           ` Alan Stern
2015-01-16 11:21             ` vichy
2015-01-16 15:23               ` Alan Stern

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=CAOVJa8HHwa-ZmwqgBozVuwWUZaBiVHb3-81sn3tOOp0_x5HNGw@mail.gmail.com \
    --to=vichy.kuo@gmail.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.