From: Florian Achleitner <achleitner.florian@fronius.com>
To: Amitkumar Karwar <akarwar@marvell.com>
Cc: Avinash Patil <patila@marvell.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Maithili Hinge <maithili@marvell.com>
Subject: Re: [RFC/PATCH] mwifiex: Driver - Firmware Glitches
Date: Fri, 17 Apr 2015 10:29:59 +0200 [thread overview]
Message-ID: <1675638.uTIoPdU2hg@r90b40zn> (raw)
In-Reply-To: <2293982.N26UvI80V5@r90b40zn>
On Thursday 16 April 2015 15:19:27 Florian Achleitner wrote:
> I will try to figure out whether the root cause is the MMC interface.
> Probably in this case, the reset actually recovers from a bug in the mmc
> driver.
Anyways, we have a virtually identical hardware with a Marvell SD8688 based
wireless module, which uses the libertas driver. Running kernel 3.10.41 we
have no problems for 50 days.
Running the same kernel with mwifiex with the SD8788 we see a freeze which
requires a hw-reset within about a day. Similar to the most recent kernel.
Are there known sdio issues with SD8788?
Will try to get useful information from the mmc system..
Regards,
Florian
next prev parent reply other threads:[~2015-04-17 8:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 9:10 [RFC/PATCH] mwifiex: Driver - Firmware Glitches Florian Achleitner
2015-04-16 9:14 ` [PATCH] mwifiex: Trigger a card reset on "DNLD_CMD: host to card failed" Florian Achleitner
2015-05-09 13:35 ` Kalle Valo
2015-05-09 16:18 ` Florian Achleitner
2015-05-11 6:35 ` Kalle Valo
2015-04-16 9:30 ` [RFC/PATCH] mwifiex: Driver - Firmware Glitches Amitkumar Karwar
2015-04-16 10:34 ` Florian Achleitner
2015-04-16 11:21 ` Amitkumar Karwar
2015-04-16 13:19 ` Florian Achleitner
2015-04-17 8:29 ` Florian Achleitner [this message]
2015-04-17 9:45 ` Amitkumar Karwar
2015-04-23 8:33 ` Florian Achleitner
2015-04-23 8:43 ` James Cameron
2015-04-23 9:48 ` Avinash Patil
2015-04-16 10:19 ` James Cameron
2015-04-16 10:43 ` Florian Achleitner
2015-04-16 11:11 ` Avinash Patil
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=1675638.uTIoPdU2hg@r90b40zn \
--to=achleitner.florian@fronius.com \
--cc=akarwar@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=maithili@marvell.com \
--cc=patila@marvell.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