linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: How does rfkill work?
Date: Thu, 02 Apr 2009 23:39:45 +0200	[thread overview]
Message-ID: <1238708385.22126.4.camel@johannes.local> (raw)
In-Reply-To: <49D52D27.4010607@lwfinger.net>

[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]

On Thu, 2009-04-02 at 16:24 -0500, Larry Finger wrote:

> > Actually. Are you positive it works without my patch? The confusing this
> > is that this code never seems to call led_trigger_event() outside of
> > rfkill_led_trigger_activate() which is only called once... Can you try
> > this patch please?
> 
> No, it hasn't worked for some time, but until you rationalized the rfkill code,
> I didn't want to mess with it. :)

Ah, ok :) And I thought I broke it.

> This patch does the trick. Not only is the set brightness callback routine being
> called, but the LED is going on/off as expected. 

Wohoo!

> It even ends up in the off
> state when the module is loaded with the switch off. 

Yeah I'd fixed that earlier by calling the right thing.

> It toggles on/off in that
> case, but I'm not going to complain as long as it ends up off. That part broke
> first, then everything broke later..

Hm, don't see a good way to fix that really. Nor am I sure why it
happens, but if it just flashes once doesn't really matter I guess.

I'll roll this into my rework patch.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2009-04-02 21:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-02  4:59 How does rfkill work? Larry Finger
2009-04-02  9:56 ` Johannes Berg
2009-04-02 14:44   ` Larry Finger
2009-04-02 15:02     ` Johannes Berg
2009-04-02 15:22       ` Larry Finger
2009-04-02 15:55         ` Johannes Berg
2009-04-02 16:27         ` Johannes Berg
2009-04-02 18:18           ` Larry Finger
2009-04-02 18:28             ` Johannes Berg
2009-04-03 15:15               ` Richard Purdie
2009-04-03 19:22                 ` Johannes Berg
2009-04-02 18:29             ` Johannes Berg
2009-04-02 18:42               ` Larry Finger
2009-04-02 18:48                 ` Johannes Berg
2009-04-02 18:57                   ` Johannes Berg
2009-04-02 20:36                     ` Larry Finger
2009-04-02 20:50                       ` Johannes Berg
2009-04-02 21:24                         ` Larry Finger
2009-04-02 21:39                           ` Johannes Berg [this message]
2009-04-02 21:59                             ` Larry Finger
2009-04-02 22:09                               ` Johannes Berg
2009-04-03  4:37                       ` Marcel Holtmann
2009-04-03  4:57                         ` Larry Finger
2009-04-03  5:09                         ` Kay Sievers
2009-04-03  4:35       ` Marcel Holtmann
2009-04-03  9:01         ` Johannes Berg

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=1238708385.22126.4.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=Larry.Finger@lwfinger.net \
    --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;
as well as URLs for NNTP newsgroup(s).