All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <linux-wireless@emagii.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, ath6kl-devel@qca.qualcomm.com
Subject: Re: ath6kl_sdio blocked by RFKILL
Date: Wed, 05 Jun 2013 13:17:59 +0200	[thread overview]
Message-ID: <51AF1E67.8030407@emagii.com> (raw)
In-Reply-To: <8738t2nh6a.fsf@kamboji.qca.qualcomm.com>

On 2013-06-01 14:34, Kalle Valo wrote:
> Ulf Samuelsson <ntp@emagii.com> writes:
>
>> Have built the ath6kl_sdio driver for an Cortex-A5 chip using the
>> linux-3.6.9 kernel
>> File system built using Yocto  and Busybox RF-Kill.
>>
>> Kernel Config contains:
>>
>> CONFIG_RFKILL=m
>> CONFIG_RFKILL_LEDS=y
>> CONFIG_RFKILL_INPUT=y
>> # CONFIG_RFKILL_GPIO is not set
>>
>> When I do
>>
>> # ifconfig wlan0 up.
>>
>> I get the error message:
>>
>> ifconfig: SIOCSIFFLAGS: Operation not possible due to RF-kill
>>
>> If I run "rfkill list" I get
>>
>> 1: phy1: wlan
>>          Soft blocked: yes
>>          Hard blocked: no
>>
>>
>> If I try to unblock using "rfkill unblock all" or "wifi" or "wlan",
>> the soft block remains.
> Have you tried "rfkill unblock 1"?
>

Yes, I have now been able to reproduce on another board.

The System has an MMC connector, and if I boot with my SD51 SDIO card in 
the connector, then

"rfkill unblock <x>"

won't work, with x = {all,wifi,1 ...}

If I boot without the SD51 card beeing inserted, and then insert if 
after theboot has been completed,
then rfkill works as expected.

The MMC host driver is  built as a module, maybe it shouldn't.

BR
Ulf Samuelsson

      reply	other threads:[~2013-06-05 11:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28 15:01 ath6kl_sdio blocked by RFKILL Ulf Samuelsson
2013-06-01 12:34 ` Kalle Valo
2013-06-05 11:17   ` Ulf Samuelsson [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=51AF1E67.8030407@emagii.com \
    --to=linux-wireless@emagii.com \
    --cc=ath6kl-devel@qca.qualcomm.com \
    --cc=kvalo@qca.qualcomm.com \
    --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 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.