linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Chen, Chien-Chia" <machen@suse.com>
To: IvDoorn@gmail.com, helmut.schaa@googlemail.com,
	users@rt2x00.serialmonkey.com
Cc: linux-wireless@vger.kernel.org
Subject: [rt2x00-users] [PATCH] rt2x00: rt2x00dev: move rfkill_polling register to proper place
Date: Tue, 27 Mar 2012 14:28:00 +0800	[thread overview]
Message-ID: <1332829680-32457-1-git-send-email-machen@suse.com> (raw)

Move rt2x00rfkill_register(rt2x00dev) to rt2x00lib_probe_dev().
It fixes of starting rfkill_poll function at the right time if
sets hard rfkill block and reboot. rt2x00mac_rfkill_poll should
be starting before bringing up the wireless interface.

Signed-off-by: Kevin Chou <kevin.chou@mediatek.com>
---
 drivers/net/wireless/rt2x00/rt2x00dev.c |    6 +-----
 1 files changed, 1 insertions(+), 5 deletions(-)

diff --git a/drivers/net/wireless/rt2x00/rt2x00dev.c b/drivers/net/wireless/rt2x00/rt2x00dev.c
index fc9901e..90cc5e7 100644
--- a/drivers/net/wireless/rt2x00/rt2x00dev.c
+++ b/drivers/net/wireless/rt2x00/rt2x00dev.c
@@ -1062,11 +1062,6 @@ static int rt2x00lib_initialize(struct rt2x00_dev *rt2x00dev)
 
 	set_bit(DEVICE_STATE_INITIALIZED, &rt2x00dev->flags);
 
-	/*
-	 * Register the extra components.
-	 */
-	rt2x00rfkill_register(rt2x00dev);
-
 	return 0;
 }
 
@@ -1210,6 +1205,7 @@ int rt2x00lib_probe_dev(struct rt2x00_dev *rt2x00dev)
 	rt2x00link_register(rt2x00dev);
 	rt2x00leds_register(rt2x00dev);
 	rt2x00debug_register(rt2x00dev);
+	rt2x00rfkill_register(rt2x00dev);
 
 	return 0;
 
-- 
1.7.3.4


             reply	other threads:[~2012-03-27  6:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27  6:28 Chen, Chien-Chia [this message]
2012-03-27 11:51 ` [rt2x00-users] [PATCH] rt2x00: rt2x00dev: move rfkill_polling register to proper place Helmut Schaa
2012-03-27 12:38 ` Stanislaw Gruszka
2012-03-28  2:33   ` Matt Chen
2012-03-29  2:50     ` Matt Chen
2012-03-29  9:40       ` Stanislaw Gruszka
2012-03-29 10:21         ` Matt Chen

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=1332829680-32457-1-git-send-email-machen@suse.com \
    --to=machen@suse.com \
    --cc=IvDoorn@gmail.com \
    --cc=helmut.schaa@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=users@rt2x00.serialmonkey.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).