linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Achleitner <flo@fopen.at>
To: James Cameron <quozl@laptop.org>
Cc: linux-wireless@vger.kernel.org,
	Amitkumar Karwar <akarwar@marvell.com>,
	Avinash Patil <patila@marvell.com>,
	Maithili Hinge <maithili@marvell.com>
Subject: Re: [RFC/PATCH] mwifiex: Driver - Firmware Glitches
Date: Thu, 16 Apr 2015 12:43:14 +0200	[thread overview]
Message-ID: <3204550.d2SRA167I8@r90b40zn> (raw)
In-Reply-To: <20150416101913.GA26748@us.netrek.org>

On Thursday 16 April 2015 20:19:13 James Cameron wrote:
> On Thu, Apr 16, 2015 at 11:10:02AM +0200, Florian Achleitner wrote:
> > Is the necessity of frequent hardware resets a commonly known issue
> > with this chip/firmware? Anybody else experiencing these?
> 
> Yes, but how frequent?

Depends on the specific hardware. Averages follow.

> 
> > 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.
> 
> See this a lot during heavy testing.

Also a lot, maybe once a day in low load.

> 
> > (2)  Firmware wakeup failed.. Ok, after reset.
> 
> Never see this.

Once a day.

> 
> > (3) DNLD_CMD: host to card failed. No reset triggered. See patch.
> 
> Very rarely see this.

Also very rarely. Once a week, probably.

> 
> However, our experience may not be comparable; we are using 8787 with
> a 3.5 kernel, because we haven't the resources to use a later kernel
> or get backports working.
> 
> Also, we use WOL (wake on lan) heavily; frequent automatic suspends,
> with a GPIO wakeup in addition to the SDHCI.

We don't use WOL or suspends.

Regards,
Florian


  reply	other threads:[~2015-04-16 10:43 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
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 [this message]
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=3204550.d2SRA167I8@r90b40zn \
    --to=flo@fopen.at \
    --cc=akarwar@marvell.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maithili@marvell.com \
    --cc=patila@marvell.com \
    --cc=quozl@laptop.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;
as well as URLs for NNTP newsgroup(s).