From: Matt Chen <machen@suse.com>
To: ath9k-devel@lists.ath9k.org,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: ath9k LED behaviors.
Date: Tue, 14 Feb 2012 15:36:40 +0800 [thread overview]
Message-ID: <CALx5=V8fwMpsicRyrSKk3nnZjfo8oMYbCxmrPFxDeps-5JSn+Q@mail.gmail.com> (raw)
Hi list,
I am sorry if I asked this issue before or not.
I meet an issue in my laptop which is using the 168c:0032, driver is
ath9k. I found if I press Fn+F12 to enable/disable the wifi, the LED
would take about 5 or 6 seconds to be ON or OFF. I found the in ath9k
would detect the GPIO status to change the rfkill status. and also
rfkill in ath9k is using polling way to monitor the status of GPIO
status. In other my machines with the same module and driver (ath9k),
press Fn+F12 would be easy to find out the LED is ON or OFF, would not
take too long. ( probably less than 1 second )
So is there any way to find out which driver has the right to change
the GPIO status ?
reply other threads:[~2012-02-14 7:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CALx5=V8fwMpsicRyrSKk3nnZjfo8oMYbCxmrPFxDeps-5JSn+Q@mail.gmail.com' \
--to=machen@suse.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=linux-wireless@vger.kernel.org \
/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).