From: Ivo van Doorn <ivdoorn@gmail.com>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] mac80211: Add radio led trigger
Date: Wed, 9 Jan 2008 17:50:47 +0100 [thread overview]
Message-ID: <200801091750.47672.IvDoorn@gmail.com> (raw)
In-Reply-To: <1ba2fa240801081618u1ba01720rbd89a4c4b8d80a8c@mail.gmail.com>
Hi,
> > @@ -651,6 +652,7 @@ static int ieee80211_ioctl_siwtxpower(struct net_device *dev,
> > if (local->hw.conf.radio_enabled != !(data->txpower.disabled)) {
> > local->hw.conf.radio_enabled = !(data->txpower.disabled);
> > need_reconfig = 1;
> > + ieee80211_led_radio(local, local->hw.conf.radio_enabled);
>
> Not sure but isn't it cleaner to push it to ieee80211_hw_config().
> This will cover also ieee80211_open and maybe in the future also
> cfg80211
> Will it be so bad to call led_radio even the led is already lit?
Well that means it will be called quite often, and although it would perhaps
not matter that much, I don't consider it a clean solution.
We could move it to ieee80211_hw_config() eventually, but I think we should
first implement some kind of "what config option changed" handling. That
would benefit drivers as well since they should now handle that to prevent
configuring _everything_ when hw_config() is called.
Ivo
next prev parent reply other threads:[~2008-01-09 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-06 13:10 [PATCH] mac80211: Add radio led trigger Ivo van Doorn
2008-01-06 18:19 ` Tomas Winkler
2008-01-06 18:22 ` Michael Buesch
2008-01-06 18:25 ` Ivo van Doorn
2008-01-06 23:14 ` Tomas Winkler
2008-01-07 18:44 ` Ivo van Doorn
2008-01-07 18:45 ` [PATCH v2] " Ivo van Doorn
2008-01-09 0:18 ` Tomas Winkler
2008-01-09 16:50 ` Ivo van Doorn [this message]
2008-01-09 17:07 ` Tomas Winkler
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=200801091750.47672.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomasw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.