From: Magnus Damm <magnus.damm@gmail.com>
To: Trilok Soni <soni.trilok@gmail.com>
Cc: linux-input@vger.kernel.org, lethal@linux-sh.org,
linux-sh@vger.kernel.org
Subject: Re: [PATCH] input: add suspend wakeup support to sh_keysc
Date: Tue, 10 Mar 2009 19:01:58 +0900 [thread overview]
Message-ID: <aec7e5c30903100301n3ed24395i3d72fd956b4b7f@mail.gmail.com> (raw)
In-Reply-To: <5d5443650903100124g2bbc4837gaa5d9a9f17cd56f0@mail.gmail.com>
Hi Trilok,
Thanks for your comments!
On Tue, Mar 10, 2009 at 5:24 PM, Trilok Soni <soni.trilok@gmail.com> wrote:
> Hi Magnus,
>
>> +
>> + device_init_wakeup(&pdev->dev, 1);
>> return 0;
>
>
> 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.
>> err5:
>> free_irq(irq, pdev);
>> @@ -253,17 +255,36 @@ static int __devexit sh_keysc_remove(str
>> return 0;
>> }
>>
>> +static int sh_keysc_suspend(struct device *dev)
>> +{
>> + struct platform_device *pdev;
>> + struct sh_keysc_priv *priv;
>> + unsigned short value;
>> +
>> + pdev = container_of(dev, struct platform_device, dev);
>> + priv = platform_get_drvdata(pdev);
>
> to_platform_device(...) ?
Thanks, much better!
/ magnus
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-03-10 10:02 UTC|newest]
Thread overview: 5+ 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 8:24 ` Trilok Soni
2009-03-10 10:01 ` Magnus Damm [this message]
2009-03-10 10:43 ` Trilok Soni
[not found] ` <aec7e5c30903100352o611e6cake0ddd50fed1d6975@mail.gmail.com>
2009-03-10 11:10 ` 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=aec7e5c30903100301n3ed24395i3d72fd956b4b7f@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=lethal@linux-sh.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=soni.trilok@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).