From: Juuso Oikarinen <juuso.oikarinen@nokia.com>
To: ext Ohad Ben-Cohen <ohad@wizery.com>
Cc: coelho@ti.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wl12xx: Allow wl12xx interrupts to wake up the host
Date: Mon, 07 Feb 2011 14:58:54 +0200 [thread overview]
Message-ID: <1297083534.2064.19.camel@wimaxnb.nmp.nokia.com> (raw)
In-Reply-To: <AANLkTim2H+s0mM+7HBubEHbYj5O+PRHDkeJefx64zRKx@mail.gmail.com>
On Mon, 2011-02-07 at 14:38 +0200, ext Ohad Ben-Cohen wrote:
> On Mon, Feb 7, 2011 at 2:29 PM, Juuso Oikarinen
> <juuso.oikarinen@nokia.com> wrote:
> > On Mon, 2011-02-07 at 14:09 +0200, ext Ohad Ben-Cohen wrote:
> >> On Mon, Feb 7, 2011 at 1:30 PM, <juuso.oikarinen@nokia.com> wrote:
> >> >
> >> > From: Juuso Oikarinen <juuso.oikarinen@nokia.com>
> >> >
> >> > Currently the wl12xx interrupts are not configured to wake up the host, which
> >> > leads to reduced performance.
> >>
> >> Can you elaborate what do you mean ?
> >>
> >> Today the chip is powered off at system suspend, so it won't trigger
> >> any interrupts anyway.
> >>
> >> When additional suspend modes will be introduced (e.g. WoWL) this will
> >> be needed of course.
> >
> > These are not just for suspend, AFAIK, but apply also to power saving
> > states.
>
> What power states do you mean ? do you mean the cpuidle path ? I don't
> think it's related.
>
> Can you please describe what was the reduced performance that this
> solved for you ? performance is a hot topic for us now :)
Actually this I don't see any performance impact for better or worse of
this patch on brief testing. I was instructed by some of our other
kernel-dudes that this is actually needed for the cpuidle path too, or
there might be some implications.
I'm currently trying to find out if this is really needed or not.
-Juuso
next prev parent reply other threads:[~2011-02-07 12:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 11:30 [PATCH] wl12xx: Allow wl12xx interrupts to wake up the host juuso.oikarinen
2011-02-07 12:09 ` Ohad Ben-Cohen
2011-02-07 12:29 ` Juuso Oikarinen
2011-02-07 12:38 ` Ohad Ben-Cohen
2011-02-07 12:58 ` Juuso Oikarinen [this message]
2011-02-07 14:56 ` Ohad Ben-Cohen
2011-02-08 7:57 ` Juuso Oikarinen
2011-02-08 8:43 ` Ohad Ben-Cohen
2011-02-08 10:13 ` Kalle Valo
2011-02-08 11:13 ` Juuso Oikarinen
2011-02-08 11:47 ` Kalle Valo
2011-02-08 12:38 ` Juuso Oikarinen
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=1297083534.2064.19.camel@wimaxnb.nmp.nokia.com \
--to=juuso.oikarinen@nokia.com \
--cc=coelho@ti.com \
--cc=linux-wireless@vger.kernel.org \
--cc=ohad@wizery.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