From: Florian Achleitner <flo@fopen.at>
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: Thu, 23 Apr 2015 10:33:02 +0200 [thread overview]
Message-ID: <2079721.JMnuuxDd1J@r90b40zn> (raw)
In-Reply-To: <5FF020A1CFFEEC49BD1E09530C4FF5951B16EB7A39@SC-VEXCH1.marvell.com>
On Friday 17 April 2015 02:45:02 Amitkumar Karwar wrote:
> Known firmware issues are command timeout and wakeup failure. They are not
> specific to SDIO. As Avinash mentioned earlier, we need to check
> CONFIG_MMC_DEBUG enbled dmesg logs for "write iomem (1) failed: -110"
> issue.
Thx.
A kernel with CONFIG_MMC_DEBUG is running since 6 days on 4 devices, but
nothing valuable captured yet. Unfortunately, it looks like the debugging code
modifies the timing, such that the failure doesn't occur..
>
> Regards,
> Amitkumar
Regards,
Flo
next prev parent reply other threads:[~2015-04-23 8:33 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
2015-04-17 9:45 ` Amitkumar Karwar
2015-04-23 8:33 ` Florian Achleitner [this message]
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=2079721.JMnuuxDd1J@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).