From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
Avery Pennarun <apenwarr@gmail.com>
Subject: Re: ath10k driver crashes whenever firmware crashes on ARM SoC
Date: Tue, 11 Mar 2014 10:13:01 +0200 [thread overview]
Message-ID: <87siqpi25u.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAJ-Vmo=AX9MzrCuwv_LMBkD6mT97S+c1K1cbLiJLKWx=2im5=A@mail.gmail.com> (Adrian Chadd's message of "Tue, 11 Mar 2014 00:52:54 -0700")
(Fixing top posting)
Adrian Chadd <adrian@freebsd.org> writes:
> On 11 March 2014 00:40, Avery Pennarun <apenwarr@gmail.com> wrote:
>
>> We do have a separate reset line controlled by a GPIO. Using that
>> crashes the SoC's PCIe host implementation (whee!). But I got help
>> from the SoC manufacturer and was able to get some instructions for
>> resetting their PCIe host controller. When I do all the magic
>> incantations in the right order, the system can recover, albeit with a
>> fully reset ath10k chip. This workaround is unfortunately specific to
>> the host device platform so it won't do you much good.
>
> ... it's not a complete loss!
>
> This to me says "we need a hook from the driver to call the host
> "reset the bus" thing".
>
> We also kinda need it for ath9k/ath5k (if it's not there) so AHB
> attached things can be reset by actually poking an SoC reset register.
Yeah, that kind of hook would be good to have.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-03-11 8:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 17:18 ath10k driver crashes whenever firmware crashes on ARM SoC Avery Pennarun
2014-01-28 18:20 ` Ben Greear
2014-01-28 18:34 ` Avery Pennarun
2014-01-28 19:01 ` Ben Greear
2014-01-28 19:11 ` Avery Pennarun
2014-01-28 20:10 ` Janusz Dziedzic
2014-01-28 20:51 ` Avery Pennarun
2014-01-29 16:44 ` Kalle Valo
[not found] ` <CAJ-VmokorbJ2iU4rGNYdRj+A22NR9cV-5h-tDN0pD2FCurZDpA@mail.gmail.com>
2014-01-28 20:55 ` Avery Pennarun
2014-01-29 16:41 ` Kalle Valo
2014-01-29 18:44 ` Adrian Chadd
2014-01-30 2:41 ` Avery Pennarun
2014-02-09 8:00 ` Avery Pennarun
2014-02-27 15:48 ` Missing memory barriers Kalle Valo
2014-02-28 6:10 ` Avery Pennarun
2014-03-06 13:34 ` Kalle Valo
2014-03-11 7:33 ` ath10k driver crashes whenever firmware crashes on ARM SoC Kalle Valo
2014-03-11 7:40 ` Avery Pennarun
2014-03-11 7:52 ` Adrian Chadd
2014-03-11 7:59 ` Avery Pennarun
2014-03-11 8:13 ` Kalle Valo [this message]
2014-03-11 8:37 ` Michal Kazior
2014-03-11 8:10 ` Kalle Valo
2014-03-11 19:01 ` Ben Greear
2014-03-12 8:22 ` Kalle Valo
2014-03-12 16:01 ` Ben Greear
2014-03-12 23:28 ` Avery Pennarun
2014-03-13 5:09 ` Kalle Valo
2014-03-13 17:34 ` Adrian Chadd
2014-03-13 17:39 ` Kalle Valo
2014-03-13 17:42 ` Ben Greear
2014-03-14 6: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=87siqpi25u.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=adrian@freebsd.org \
--cc=apenwarr@gmail.com \
--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