From: Christian Lamparter <chunkeey@web.de>
To: Fabio Rossi <rossi.f@inwind.it>
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 2/3] p54: more SoftLED updates
Date: Tue, 14 Apr 2009 18:20:21 +0200 [thread overview]
Message-ID: <200904141820.21965.chunkeey@web.de> (raw)
In-Reply-To: <200904141712.34220.rossi.f@inwind.it>
On Tuesday 14 April 2009 17:12:33 Fabio Rossi wrote:
> On Wednesday 25 March 2009, Christian Lamparter wrote:
>
> > This patch hopefully finishes the SoftLED code:
> > - It adds two more LEDs (rx and radio).
> > (the FW claims it can support up to 16 LEDs,
> > but I doubt that any vendor put more than 4 on a board)
> > - update the LEDs in a _delayed_ workqueue.
> > No one reported any more crashes.
> > (see: "PATCH] p54: fix race condition in memory management")
> > So we can stop burning the mm code.
>
> My device has 2 LEDs and I can see 4 registrations (assoc, tx, rx and radio).
> Does it make sense to register LEDs which are not available?
Well, trouble is that you can look (with your eyes) at your device and see the
number of LEDs... This is something we cannot do with the driver.
(Unless we find a EEPROM field which stores the # of LEDs and
maybe even what they are used for?)
4 is just a "save" guess which should cover most - if not all - customer devices.
Regards,
Chr
prev parent reply other threads:[~2009-04-14 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 2:12 [PATCH 2/3] p54: more SoftLED updates Christian Lamparter
2009-03-25 3:32 ` Larry Finger
2009-04-14 15:12 ` Fabio Rossi
2009-04-14 16:20 ` Christian Lamparter [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=200904141820.21965.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rossi.f@inwind.it \
/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).