From: Kalle Valo <kvalo@codeaurora.org>
To: Claire Chang <tientzu@chromium.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Brian Norris <briannorris@chromium.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Sriram R <srirrama@codeaurora.org>,
Linux PM <linux-pm@vger.kernel.org>,
Pradeep Kumar Chitrapu <pradeepc@codeaurora.org>,
"open list\:NETWORKING DRIVERS \(WIRELESS\)"
<linux-wireless@vger.kernel.org>,
ath10k@lists.infradead.org,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Todd Brandt <todd.e.brandt@intel.com>
Subject: Re: [PATCH] ath10k: Drop WARN_ON()s that always trigger during system resume
Date: Mon, 29 Apr 2019 17:12:39 +0300 [thread overview]
Message-ID: <87ef5ksxwo.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CALiNf2_qV+iViHbS0tQquTMZfu6XfFvQCH14mdT5bixn94DZ2Q@mail.gmail.com> (Claire Chang's message of "Mon, 29 Apr 2019 18:41:50 +0800")
Claire Chang <tientzu@chromium.org> writes:
> Tested-by: Claire Chang <tientzu@chromium.org>
>
>> Still, I'm quite sure that the WARN_ON()s trigger during system resume
>> regardless of the hw/fw combination.
>
> Also see this on sido:
>
> [ 4.925278] ath10k_sdio mmc1:0001:1: qca6174 hw3.2 sdio target
> 0x05030000 chip_id 0x00000000 sub 0000:0000
> [ 4.935721] ath10k_sdio mmc1:0001:1: kconfig debug 1 debugfs 1
> tracing 1 dfs 0 testmode 1
> [ 4.948750] ath10k_sdio mmc1:0001:1: firmware ver
> WLAN.RMH.4.4.1-00007-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32
> b98adaf8
> [ 5.132728] ath10k_sdio mmc1:0001:1: board_file api 2 bmi_id 0:4
> crc32 6364cfcc
Great, thanks. I added your Tested-by as well.
--
Kalle Valo
next prev parent reply other threads:[~2019-04-29 14:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 17:24 [PATCH] ath10k: Drop WARN_ON()s that always trigger during system resume Rafael J. Wysocki
2019-04-03 19:57 ` Brian Norris
2019-04-03 21:44 ` Rafael J. Wysocki
2019-04-03 21:54 ` Brian Norris
2019-04-04 4:06 ` Kalle Valo
2019-04-04 8:28 ` Rafael J. Wysocki
2019-04-26 7:18 ` Kalle Valo
2019-04-29 8:48 ` Rafael J. Wysocki
2019-04-29 10:41 ` Claire Chang
2019-04-29 14:12 ` Kalle Valo [this message]
2019-04-29 14:10 ` Kalle Valo
2019-04-29 14:26 ` 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=87ef5ksxwo.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=briannorris@chromium.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pradeepc@codeaurora.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=srirrama@codeaurora.org \
--cc=tientzu@chromium.org \
--cc=todd.e.brandt@intel.com \
/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).