All of lore.kernel.org
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] input: add suspend wakeup support to sh_keysc
Date: Tue, 10 Mar 2009 10:52:45 +0000	[thread overview]
Message-ID: <aec7e5c30903100352o611e6cake0ddd50fed1d6975@mail.gmail.com> (raw)
In-Reply-To: <20090310062421.22328.68726.sendpatchset@rx1.opensource.se>

On Tue, Mar 10, 2009 at 7:43 PM, Trilok Soni <soni.trilok@gmail.com> wrote:
>>> Please add device_init_wakeup(&pdev->dev, 0) in sh_keysc_remove.
>>
>> Isn't this just flagging the device as wakeup capable? My first guess
>> would be that the the wakeup state of a removed device is irrelevant
>> since it won't be suspended anyway. Or am I misunderstanding? Please
>> explain in more detail.
>
> I may not have complete answer, but I am thinking of someone depending/reading
> on wakeup file state to determine the state of your device in userspace will get
> confused, so better to disable to wakeup capability on remove.

I think the per device wakeup file will disappear from sysfs when the
device gets removed, so resetting the flag in the remove() callback
just makes the driver code more confusing in my opinion. =)

Cheers,

/ magnus

  parent reply	other threads:[~2009-03-10 10:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10  6:24 [PATCH] input: add suspend wakeup support to sh_keysc Magnus Damm
2009-03-10  6:24 ` Magnus Damm
2009-03-10  8:24 ` Trilok Soni
2009-03-10  8:36   ` Trilok Soni
2009-03-10 10:01   ` Magnus Damm
2009-03-10 10:01     ` Magnus Damm
2009-03-10 10:43     ` Trilok Soni
2009-03-10 10:55       ` Trilok Soni
2009-03-10 10:52 ` Magnus Damm [this message]
2009-03-10 11:10   ` Trilok Soni
2009-03-10 11:22     ` Trilok Soni

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=aec7e5c30903100352o611e6cake0ddd50fed1d6975@mail.gmail.com \
    --to=magnus.damm@gmail.com \
    --cc=linux-sh@vger.kernel.org \
    /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.