From: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: "sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org"
<sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
"jedu-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org"
<jedu-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org>,
"lrg-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org"
<lrg-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org>,
"gg-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org"
<gg-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH V1] mfd: tps65910: Add wakeup support
Date: Fri, 20 Jan 2012 13:13:55 +0000 [thread overview]
Message-ID: <20120120131355.GG18297@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F19671E.7030003-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On Fri, Jan 20, 2012 at 06:37:42PM +0530, Laxman Dewangan wrote:
> On Friday 20 January 2012 06:32 PM, Mark Brown wrote:
> >No, that's it - when you call those userspace will get control via sysfs
> >for turning on and off the wakeup support.
> So should I call them in driver by default without taking parameter
> from platform data?
That's the normal behaviour for drivers unless there's some specific
reason for doing something different. The choice may well depend on the
application software running on the system rather than the kernel.
next prev parent reply other threads:[~2012-01-20 13:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 11:09 [PATCH V1] mfd: tps65910: Add wakeup support Laxman Dewangan
[not found] ` <1327057770-6688-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-01-20 12:51 ` Mark Brown
[not found] ` <20120120125152.GE18297-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-01-20 13:00 ` Laxman Dewangan
[not found] ` <4F196568.1080503-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-01-20 13:02 ` Mark Brown
[not found] ` <20120120130201.GF18297-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-01-20 13:07 ` Laxman Dewangan
[not found] ` <4F19671E.7030003-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-01-20 13:13 ` Mark Brown [this message]
[not found] ` <20120120131355.GG18297-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-01-21 8:10 ` Laxman Dewangan
2012-01-21 11:24 ` Laxman Dewangan
[not found] ` <4F1AA084.9080502-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-01-21 12:51 ` Mark Brown
[not found] ` <20120121125123.GB10206-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-01-21 12:57 ` Laxman Dewangan
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=20120120131355.GG18297@opensource.wolfsonmicro.com \
--to=broonie-yzvpicuk2aatku/dhu1wvuem+bqzidxxqq4iyu8u01e@public.gmane.org \
--cc=gg-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org \
--cc=jedu-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org \
--cc=ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lrg-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org \
--cc=sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.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 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).