Linux wireless drivers development
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@adurom.com>
To: Juuso Oikarinen <juuso.oikarinen@nokia.com>
Cc: ext Ohad Ben-Cohen <ohad@wizery.com>,
	coelho@ti.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wl12xx: Allow wl12xx interrupts to wake up the host
Date: Tue, 08 Feb 2011 13:47:10 +0200	[thread overview]
Message-ID: <8762su929t.fsf@purkki.adurom.net> (raw)
In-Reply-To: <1297163582.3389.7.camel@wimaxnb.nmp.nokia.com> (Juuso Oikarinen's message of "Tue\, 08 Feb 2011 13\:13\:02 +0200")

Juuso Oikarinen <juuso.oikarinen@nokia.com> writes:

> On Tue, 2011-02-08 at 12:13 +0200, ext Kalle Valo wrote:
>> Juuso Oikarinen <juuso.oikarinen@nokia.com> writes:
>> 
>> To me platform specific changes in drivers are always problematic.
>
> Yeah I tend to agree.
>
> But then for some reason there is this interface in interrupts.h to do
> this, and AFAIU the one requesting the IRQ and controlling enabling and
> disabling of it is supposed to also tune this wakeing on/off. Apparently
> it should even do this when just enabling/disabling the interrupt -
> which are things performed in the driver.

Yeah, you have a point. There has to be some reason for adding this.
Unfortunately the documentation I found was scarse and I didn't get
how it should be used. For example, wakeup from what? Only from
suspend? Or also from sleep states? But then again, isn't it obvious
that an irq from the device should wake the cpu from sleep states?

And to make this more generic: should all wifi drivers use
enable_irq_wake()?

(Just trying to understand this.)

-- 
Kalle Valo

  reply	other threads:[~2011-02-08 11:47 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
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 [this message]
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=8762su929t.fsf@purkki.adurom.net \
    --to=kvalo@adurom.com \
    --cc=coelho@ti.com \
    --cc=juuso.oikarinen@nokia.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