Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Arend Van Spriel <arend@broadcom.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: cfg80211 rfkill interface
Date: Mon, 10 Jan 2011 20:45:09 +0100	[thread overview]
Message-ID: <1294688709.3583.25.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <400C43189542CE41BC0A5B252FC90136952F059529@SJEXCHCCR02.corp.ad.broadcom.com>

Hi Arend,

> I am looking into implementing rfkill into our brcm80211 open-source
> driver. Our driver detects disable switch by an interrupt, but
> switching back does not give an interrupt. 

Interesting, but I guess it makes some sense.

> For the latter I wanted to use the rfkill_poll callback and
> wiphy_rfkill_start_polling.

Right, makes sense.

> However, I tried a wiphy_rfkill_stop_polling in the rfkill_poll
> callback when rf is unblocked, and this resulted in a system hang. 

Yeah, I'm not surprised. start_polling will work from anywhere, but
stop_polling needs to actually completely sync the poll stop so it can't
be done from within the poll or from within any rfkill callbacks.

> So I moved the wiphy_rfkill_stop_polling to the start callback. Does
> that make sense or is there another way you would recommend?

I think that makes sense.

However, where do you start polling? You have to poll even if the device
is not start()ed, I guess?

johannes


  reply	other threads:[~2011-01-10 19:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-10 19:33 cfg80211 rfkill interface Arend Van Spriel
2011-01-10 19:45 ` Johannes Berg [this message]
2011-01-14 14:54   ` Arend Van Spriel
2011-01-14 14:57     ` Johannes Berg
2011-01-14 15:05       ` Arend Van Spriel

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=1294688709.3583.25.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arend@broadcom.com \
    --cc=linux-wireless@vger.kernel.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