From: Alberto Panizzo <maramaopercheseimorto@gmail.com>
To: Amitkumar Karwar <akarwar@marvell.com>
Cc: 'Paul Fox' <pgf@laptop.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"libertas-dev@lists.infradead.org"
<libertas-dev@lists.infradead.org>
Subject: RE: [PATCH] Added support for host sleep feature
Date: Tue, 13 Jul 2010 10:33:42 +0200 [thread overview]
Message-ID: <1279010022.3164.27.camel@realization> (raw)
In-Reply-To: <5FF020A1CFFEEC49BD1E09530C4FF59505DA40D0D6@SC-VEXCH1.marvell.com>
On ven, 2010-07-09 at 06:01 -0700, Amitkumar Karwar wrote:
>
> > amitkumar wrote:
> > > From: Amitkumar Karwar <akarwar@marvell.com>
> > >
> > > Existing "ethtool -s ethX wol X" command configures hostsleep
> > > parameters, but those are activated only during suspend/resume,
> > > there is no way to configure host sleep without actual suspend.
> >
> > as background, can you expand on how this is useful? i just spent
> > a bunch of time debugging issues with HOST_SLEEP_CFG and
> > HOST_SLEEP_ACTIVATE (which doesn't work on an 8388) on the XO-1
> > OLPC laptop, and i'm wondering whether or how this would have
> > helped.
>
> This patch is useful if someone wants to enable host sleep feature without the device entering suspend state.
>
> The host sleep using device suspend feature is also intact.
>
> Thanks,
> Amitkumar Karwar
Regards current consumption, maintaining a wireless connection active,
the device consumes circa 30 mA instead of 180 mA of full power idle
mode.
So for embedded devices powered from battery, enabling the Power Save
mode is a huge battery save task.
Best Regards,
--
Alberto!
Be Persistent!
- Greg Kroah-Hartman (FOSDEM 2010)
prev parent reply other threads:[~2010-07-13 8:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 1:13 [PATCH] Added support for host sleep feature Amitkumar Karwar
2010-07-08 15:11 ` Paul Fox
2010-07-09 13:01 ` Amitkumar Karwar
2010-07-13 8:33 ` Alberto Panizzo [this message]
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=1279010022.3164.27.camel@realization \
--to=maramaopercheseimorto@gmail.com \
--cc=akarwar@marvell.com \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pgf@laptop.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).