From: Vasanthakumar Thiagarajan <vasanth@atheros.com>
To: Bob Copeland <bcopeland@gmail.com>
Cc: Vasanth Thiagarajan <Vasanth.Thiagarajan@Atheros.com>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
Jouni Malinen <Jouni.Malinen@Atheros.com>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
Subject: Re: [PATCH] ath9k: Fix LED blink pattern
Date: Sat, 31 Jan 2009 14:10:45 +0530 [thread overview]
Message-ID: <20090131084044.GA5999@vasanth-laptop> (raw)
In-Reply-To: <b6c5339f0901290717m760c4704x7f9df7502f772a17@mail.gmail.com>
On Thu, Jan 29, 2009 at 08:47:04PM +0530, Bob Copeland wrote:
> > + struct delayed_work ath_led_blink_work;
> > + int led_on_duration;
> > + int led_off_duration;
> > + int led_on_cnt;
> > + int led_off_cnt;
>
> This is something that has come up from time to time from users for
> ath5k as well. Half of the drivers now have their own timers for
> turning leds on or off.
>
> Can we just add a decent blink algorithm to mac80211? Right now for
> rx it just toggles every other packet. For tx, it's slightly smarter
> but not overly so. It seems like this is one of those things everyone
> wants to do and we could easily make it a standard service.
ath9k maps all four led functionality (radio, assoc, rx and
tx) into a single LED, I think ath5k is also doing in the similar way.
But other drivers can map their led functionality differently in
their h/w where the pattern will differ. mac80211 is already signalling
appropriate leds, imho it is up to the driver to define the pattern
based on the number of leds available/configured.
>
> --
> Bob Copeland %% www.bobcopeland.com
prev parent reply other threads:[~2009-01-31 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 12:22 [PATCH] ath9k: Fix LED blink pattern Vasanthakumar Thiagarajan
2009-01-29 15:17 ` Bob Copeland
2009-01-29 15:19 ` Johannes Berg
2009-01-31 8:40 ` Vasanthakumar Thiagarajan [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=20090131084044.GA5999@vasanth-laptop \
--to=vasanth@atheros.com \
--cc=Jouni.Malinen@Atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=Vasanth.Thiagarajan@Atheros.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=bcopeland@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).