From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: "miaoqing@codeaurora.org" <miaoqing@codeaurora.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
ath9k-devel <ath9k-devel@qca.qualcomm.com>,
"s.l-h@gmx.de" <s.l-h@gmx.de>
Subject: Re: [PATCH] ath9k: fix AR5416 access GPIO warning
Date: Mon, 15 Aug 2016 10:16:50 +0000 [thread overview]
Message-ID: <877fbicp67.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1470296914-9152-1-git-send-email-miaoqing@codeaurora.org> (miaoqing@codeaurora.org's message of "Thu, 4 Aug 2016 15:48:34 +0800")
<miaoqing@codeaurora.org> writes:
> From: Miaoqing Pan <miaoqing@codeaurora.org>
>
> The warning was seen on AR5416 chip, which invoke ath9k_hw_gio_get()
> before the GPIO initialized correctly.
>
> WARNING: CPU: 1 PID: 1159 at ~/drivers/net/wireless/ath/ath9k/hw.c:2776 ath9k_hw_gpio_get+0x148/0x1a0 [ath9k_hw]
> ...
> CPU: 1 PID: 1159 Comm: systemd-udevd Not tainted 4.7.0-rc7-aptosid-amd64 #1 aptosid 4.7~rc7-1~git92.slh.3
> Hardware name: /DH67CL, BIOS BLH6710H.86A.0160.2012.1204.1156 12/04/2012
> 0000000000000286 00000000f912d633 ffffffff81290fd3 0000000000000000
> 0000000000000000 ffffffff81063fd4 ffff88040c6dc018 0000000000000000
> 0000000000000002 0000000000000000 0000000000000100 ffff88040c6dc018
> Call Trace:
> [<ffffffff81290fd3>] ? dump_stack+0x5c/0x79
> [<ffffffff81063fd4>] ? __warn+0xb4/0xd0
> [<ffffffffa0668fb8>] ? ath9k_hw_gpio_get+0x148/0x1a0 [ath9k_hw]
>
> Signed-off-by: Miaoqing Pan <miaoqing@codeaurora.org>
As discussed in the previous thread I'll add:
Reported-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
Cc: <stable@vger.kernel.org> # 4.7+
I'm also planning to queue this to 4.8.
--
Kalle Valo
next prev parent reply other threads:[~2016-08-15 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 7:48 [PATCH] ath9k: fix AR5416 access GPIO warning miaoqing
2016-08-15 10:16 ` Valo, Kalle [this message]
2016-09-02 16:34 ` Kalle Valo
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=877fbicp67.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=miaoqing@codeaurora.org \
--cc=s.l-h@gmx.de \
/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).