From: "William Riba" <wriba@wriba.com>
To: 'Adrian Chadd' <adrian@freebsd.org>
Cc: ath10k@lists.infradead.org
Subject: RE: QCA9880/9890 rfkill
Date: Wed, 23 Sep 2015 14:32:53 -0500 [thread overview]
Message-ID: <019e01d0f636$a5b2f4e0$f118dea0$@wriba.com> (raw)
In-Reply-To: <CAJ-VmomTFHgcfKghoYSe_8WJ9gwq+sZg_pYCv3HC2UVxVe2rnQ@mail.gmail.com>
Hi Adrian - thank you for the quick response. I assume you're referring the otp.bin firmware file? Is there a mapping of the OTP to EEPROM settings available? That would be an easy fix if I can make a modification there to activate RFKILL.
-bill
-----Original Message-----
From: adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] On Behalf Of Adrian Chadd
Sent: Wednesday, September 23, 2015 1:58 PM
To: William Riba
Cc: ath10k@lists.infradead.org
Subject: Re: QCA9880/9890 rfkill
Hi,
The GPIO line needs to be hooked in via the relevant EEPROM/OTP setting so the firmware programs things in correctly.
Go dump the OTP and see what the rfkill firmware line is.
-adrian
On 23 September 2015 at 11:55, William Riba <wriba@wriba.com> wrote:
> Does anybody know whether rfkill in its hard block flavor is supported
> in any QCA9880/9890 based device and/or firmware load? While vendors
> refer to the WiFi disable/GPIO line in their reference schematics, it
> is not functional. What I see after testing multiple cards is if the
> line is asserted during operation, there seems to be no effect. If it
> is asserted at boot-up, the device does not enumerate on the PCI bus.
>
> If Qualcomm does not intend to support this functionality anymore it
> would be nice to know. Hard kills are a regulatory requirement for
> certain applications. While we would like to use a QCA9890 in a new
> application, there's no way it could make it through qualifications
> with its current operation. Any additional information on this would be welcome. Thanks.
>
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-09-23 19:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 18:55 QCA9880/9890 rfkill William Riba
2015-09-23 18:57 ` Adrian Chadd
2015-09-23 19:32 ` William Riba [this message]
2015-09-23 20:25 ` Adrian Chadd
2015-09-23 20:37 ` Ben Greear
2015-09-23 21:14 ` William Riba
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='019e01d0f636$a5b2f4e0$f118dea0$@wriba.com' \
--to=wriba@wriba.com \
--cc=adrian@freebsd.org \
--cc=ath10k@lists.infradead.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