From: Florian Achleitner <flo@fopen.at>
To: linux-wireless@vger.kernel.org
Cc: Amitkumar Karwar <akarwar@marvell.com>,
Avinash Patil <patila@marvell.com>,
Maithili Hinge <maithili@marvell.com>
Subject: [RFC/PATCH] mwifiex: Driver - Firmware Glitches
Date: Thu, 16 Apr 2015 11:10:02 +0200 [thread overview]
Message-ID: <3169170.GKjfvNuGRf@r90b40zn> (raw)
Hi,
we are using a Marvell SD8787-based module by Lesswire, which is connected to
an imx28 through sdio. We are testing with the most recent kernel from
wireless-drivers-next and Firmware 14.66.35.p52.
Frequently, we see 'glitches' between driver and Firmware. The most recent
driver answers most of them with an attempt to reset the module, reload the
firmware, and start over.
However, this only works for us, because our sdio interface triggers a
hardware reset for the wireless module whenever it probes the device. Without
this hardware reset (sdio reset only), the module fails to restart.
Is the necessity of frequent hardware resets a commonly known issue with this
chip/firmware? Anybody else experiencing these?
Currently, we see three different scenarios. One of them is currently not
answered by reset. Refer to the upcoming patch.
(1) mwifiex_cmd_timeout_func: Timeout cmd .. Ok, after reset.
(2) Firmware wakeup failed.. Ok, after reset.
(3) DNLD_CMD: host to card failed. No reset triggered. See patch.
I can provide detailed logs, if you want.
Regards,
Florian
next reply other threads:[~2015-04-16 9:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 9:10 Florian Achleitner [this message]
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
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=3169170.GKjfvNuGRf@r90b40zn \
--to=flo@fopen.at \
--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;
as well as URLs for NNTP newsgroup(s).