From: reinette chatre <reinette.chatre@intel.com>
To: Gregy <p.gregy@gmail.com>
Cc: "Kolekar, Abhijeet" <abhijeet.kolekar@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Iwlwifi and LEDS?
Date: Thu, 27 May 2010 22:39:23 -0700 [thread overview]
Message-ID: <1275025163.2091.20502.camel@rchatre-DESK> (raw)
In-Reply-To: <AANLkTilfa4YPPiroX5yfJ2BNRUVZH6imTvG4I8ukGjBC@mail.gmail.com>
On Thu, 2010-05-27 at 13:14 -0700, Gregy wrote:
> > What did you do before that does not work anymore?
> No, led never gets registered in /sys/class/leds.
Right, and the patch you reference explains why. At no point was support
for LEDs removed.
> Also I found this:
> http://article.gmane.org/gmane.linux.kernel.wireless.general/40328/
The intention and supported LED behavior has always been for a single
LED to blink according to data. The led_mode module parameter was added
to support the additional RF status indication capability.
If you want to be able to manipulate the LED in other ways than the
driver supports you could look into adding a debugfs file that
manipulates the driver's led variables (allow_blinking,
last_blink_time, ...). There is already a readable led file in debugfs,
but not writable.
Reinette
next prev parent reply other threads:[~2010-05-28 5:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 9:11 Iwlwifi and LEDS? Gregy
2010-05-21 18:07 ` Abhijeet Kolekar
2010-05-21 20:49 ` Gregy
2010-05-24 22:30 ` reinette chatre
2010-05-27 20:14 ` Gregy
2010-05-28 5:39 ` reinette chatre [this message]
2010-05-28 11:01 ` Gregy
2010-05-28 11:22 ` Johannes Berg
2010-05-28 14:58 ` Richard Purdie
2010-05-28 15:08 ` 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=1275025163.2091.20502.camel@rchatre-DESK \
--to=reinette.chatre@intel.com \
--cc=abhijeet.kolekar@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=p.gregy@gmail.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