netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: wu zhangjin <wuzhangjin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Hin-Tak Leung <htl10-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Cc: Herton Ronaldo Krzesinski
	<herton-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>,
	Larry Finger
	<Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>,
	linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Roman Mamedov <rm-pzoh41kZ4TQvJsYlp49lxw@public.gmane.org>
Subject: Re: [RFC PATCH] rtl8187: Fix led support for rfkill
Date: Fri, 1 Apr 2011 00:03:09 +0800	[thread overview]
Message-ID: <AANLkTin48KZ0wc6SiB+E3VOkVAZ5-Xj9WdhstsgEO14z@mail.gmail.com> (raw)
In-Reply-To: <4D8E8B1E.3030709-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>

On Sun, Mar 27, 2011 at 8:55 AM, Hin-Tak Leung
<htl10-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org> wrote:
[...]
>
> Hmm, I seem to have the impression that there is code somewhere for
> switching a singular LED's behavior of the driver between one or the other,
> by echo'ing into sysfs or some other trickery? Or would that be a desired
> approach if that's not done at the moment?

Do you mean the interface: /sys/class/rfkill/rfkill0/state? or
something like /sys/class/leds/...::/brightness?

Seems the LED behavior can be triggered automatically by the rfkill
input event with the kernel config option(MAC80211_LEDS, RFKILL_LEDS),
so, echo'ing to such interface may be not a good idea ;-)

Best Regards,
Wu Zhangjin
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2011-03-31 16:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-26 21:19 [RFC PATCH] rtl8187: Fix led support for rfkill Wu Zhangjin
     [not found] ` <1301174394-12642-1-git-send-email-wuzhangjin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-03-26 21:33   ` Hin-Tak Leung
2011-03-26 22:25     ` wu zhangjin
     [not found]       ` <AANLkTind3Va9J_tvZBDAPfbuyQtgxoAE+ZzG6VpU1b1q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-27  0:55         ` Hin-Tak Leung
     [not found]           ` <4D8E8B1E.3030709-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
2011-03-27 22:47             ` Larry Finger
2011-03-28 15:40               ` Herton Ronaldo Krzesinski
2011-03-31 16:22                 ` wu zhangjin
2011-03-31 17:19                   ` Herton Ronaldo Krzesinski
2011-04-01  3:12                     ` wu zhangjin
     [not found]               ` <4D8FBE88.3050907-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2011-03-31 16:04                 ` wu zhangjin
2011-03-31 16:03             ` wu zhangjin [this message]

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=AANLkTin48KZ0wc6SiB+E3VOkVAZ5-Xj9WdhstsgEO14z@mail.gmail.com \
    --to=wuzhangjin-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org \
    --cc=herton-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
    --cc=htl10-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rm-pzoh41kZ4TQvJsYlp49lxw@public.gmane.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).