From: wgong@codeaurora.org
To: Justin Capella <justincapella@gmail.com>
Cc: linux-wireless@vger.kernel.org, ath10k <ath10k@lists.infradead.org>
Subject: Re: [PATCH v2 2/2] ath10k: start recovery process when payload length exceeds max htc length for sdio
Date: Wed, 01 Jan 2020 20:50:49 -0800 [thread overview]
Message-ID: <8ad12580aae4ed23778693dd483144db@codeaurora.org> (raw)
In-Reply-To: <CAMrEMU9ZVV-yotvH2Odn+sb1HiiL_tN_GASSeSnhAOzCUjLZ7Q@mail.gmail.com>
On 2019-12-25 14:56, Justin Capella wrote:
> Does the SDIO bus require addresses to be word aligned like the PCI
> bus does? I'm thinking of how netdev alloc uses skb_push to ensure
> that the payload is aligned.
>
>
>>> if (ar->state == ATH10K_STATE_ON)
>
> What about the other STATEs: RESTARTED/ING
>
> The value you mentioned 57005, is 0xDEAD is that a special case?
> Perhaps a result of fw crash? Maybe a lookahead gone wong? I see its
> the WMI PEER ALIVE/DEAD indicator but I'm not sure why it would be
> trailer of the other
>
i have removed "if (ar->state == ATH10K_STATE_ON)"
and v3 sent:
patch v3:
https://patchwork.kernel.org/patch/11313853/
https://patchwork.kernel.org/patch/11313859/
>> 2.23.0
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2020-01-02 4:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 12:00 [PATCH v2 0/2] start recovery process when payload length overflow for sdio Wen Gong
2019-12-25 12:00 ` [PATCH v2 1/2] ath10k: add refcount for ath10k_core_restart Wen Gong
2019-12-25 15:14 ` Justin Capella
2019-12-31 9:37 ` wgong
2020-01-02 3:10 ` Justin Capella
2020-01-02 4:46 ` wgong
2019-12-25 12:00 ` [PATCH v2 2/2] ath10k: start recovery process when payload length exceeds max htc length for sdio Wen Gong
2019-12-25 22:56 ` Justin Capella
2020-01-02 4:50 ` wgong [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=8ad12580aae4ed23778693dd483144db@codeaurora.org \
--to=wgong@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=justincapella@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox