linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: John Linville <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org, bcm43xx-dev@lists.berlios.de,
	Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [PATCH] b43: RF-kill support
Date: Thu, 27 Sep 2007 23:12:43 +0200	[thread overview]
Message-ID: <200709272312.43994.IvDoorn@gmail.com> (raw)
In-Reply-To: <200709272241.06570.mb@bu3sch.de>

On Thursday 27 September 2007, Michael Buesch wrote:
> On Thursday 27 September 2007 22:54:44 Ivo van Doorn wrote:
> > Hi,
> > 
> > > @@ -2401,8 +2401,7 @@ static void b43_periodic_every1sec(struc
> > >  	radio_hw_enable = b43_is_hw_radio_enabled(dev);
> > >  	if (unlikely(dev->radio_hw_enable != radio_hw_enable)) {
> > >  		dev->radio_hw_enable = radio_hw_enable;
> > > -		b43info(dev->wl, "Radio hardware status changed to %s\n",
> > > -			radio_hw_enable ? "ENABLED" : "DISABLED");
> > > +		b43_rfkill_toggled(dev, radio_hw_enable);
> > 
> > Isn't it better to use the input_polldev for scheduled input device checking?
> > 
> > > +static void b43_notify_rfkill_press(struct work_struct *work)
> > > +{
> > > +	struct b43_rfkill *rfk = container_of(work, struct b43_rfkill,
> > > +					      notify_work);
> > > +	struct b43_wl *wl = container_of(rfk, struct b43_wl, rfkill);
> > > +	struct b43_wldev *dev;
> > > +	enum rfkill_state state;
> > 
> > Same here, input_polldev was created especially for hardware
> > devices that don't trigger interrupts when the button was pressed.
> 
> Ah, well. Will change that later. This works for now.

It might work, but this means that userspace is not made aware of
the key toggling and would thus make rfkill useless in this case.

Ivo


  reply	other threads:[~2007-09-27 20:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27 19:35 [PATCH] b43: RF-kill support Michael Buesch
2007-09-27 20:54 ` Ivo van Doorn
2007-09-27 20:41   ` Michael Buesch
2007-09-27 21:12     ` Ivo van Doorn [this message]
2007-09-27 21:03       ` Michael Buesch
2007-09-27 21:23         ` Ivo van Doorn
2007-09-27 21:14           ` Michael Buesch
2007-09-27 21:43             ` Ivo van Doorn
2007-09-27 22:17         ` Larry Finger
2007-09-27 22:33           ` Michael Buesch
2007-09-27 23:08             ` Larry Finger

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=200709272312.43994.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    /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).