From: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>
To: Felix Fietkau <nbd@openwrt.org>, <ath10k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>, Kalle Valo <kvalo@qca.qualcomm.com>
Subject: Re: [PATCH] ath10k: Add QCA99X0 to supported device list
Date: Thu, 6 Aug 2015 13:13:53 +0530 [thread overview]
Message-ID: <55C31039.6030201@qti.qualcomm.com> (raw)
In-Reply-To: <55C1FFBC.7070905@openwrt.org>
On Wednesday 05 August 2015 05:51 PM, Felix Fietkau wrote:
> On 2015-07-21 13:36, Vasanthakumar Thiagarajan wrote:
>> Add vendor/device id of QCA99X0 V2.0 to pci id table and
>> QCA99X0_HW_2_0_CHIP_ID_REV to ath10k_pci_supp_chips[] for
>> QCA99X0 to get detected by the driver.
>>
>> Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>
> I just tested a 99X0 card, and I'm getting this:
>
> [ 8.742514] ath10k_pci 0000:01:00.0: enabling device (0140 -> 0142)
> [ 8.747173] ath10k_pci 0000:01:00.0: pci irq msi interrupts 1 irq_mode 0 reset_mode 0
> [ 11.793314] ath10k_pci 0000:01:00.0: failed to receive initialized event from target: 00000000
> [ 11.793344] ath10k_pci 0000:01:00.0: failed to wait for target after cold reset: -110
> [ 11.800814] ath10k_pci 0000:01:00.0: failed to reset chip: -110
> [ 11.809228] ath10k_pci: probe of 0000:01:00.0 failed with error -110
>
> This is on an AP148 board with Linux 3.18, backports generated from
> latest wireless-testing (2015-08-03) + all patches from kvalo's ath
> tree.
Any idea about the version of AP148 that you are using?. By any chance did
you check if QCA988X is working on the same board?.
Vasanth
next prev parent reply other threads:[~2015-08-06 7:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 11:36 [PATCH] ath10k: Add QCA99X0 to supported device list Vasanthakumar Thiagarajan
2015-07-30 14:04 ` Kalle Valo
2015-08-05 12:21 ` Felix Fietkau
2015-08-06 7:43 ` Vasanthakumar Thiagarajan [this message]
2015-08-06 7:59 ` Felix Fietkau
2015-08-06 18:45 ` Peter Oh
2015-08-06 22:00 ` Felix Fietkau
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=55C31039.6030201@qti.qualcomm.com \
--to=vthiagar@qti.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.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).