From: Daniel Mack <zonque@gmail.com>
To: Paul Stewart <pstew@chromium.org>
Cc: Bing Zhao <bzhao@marvell.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>,
Sven Neumann <s.neumann@raumfeld.com>,
Andreas Fenkart <afenkart@gmail.com>,
Dylan Reid <dgreid@chromium.org>,
Amitkumar Karwar <akarwar@marvell.com>
Subject: Re: [PATCH 3.12] mwifiex: fix SDIO interrupt lost issue
Date: Sat, 28 Sep 2013 11:46:20 +0200 [thread overview]
Message-ID: <5246A56C.6030909@gmail.com> (raw)
In-Reply-To: <CAMcMvsjFurVFS2f1zCPt0uqh2gCYAvHOvos-pY=k06=ynDH=aQ@mail.gmail.com>
On 27.09.2013 23:11, Paul Stewart wrote:
> On Fri, Sep 27, 2013 at 11:55 AM, Daniel Mack <zonque@gmail.com
> <mailto:zonque@gmail.com>> wrote:
>
> On 27.09.2013 19 <tel:27.09.2013%2019>:55, Bing Zhao wrote:
> > From: Amitkumar Karwar <akarwar@marvell.com
> <mailto:akarwar@marvell.com>>
> >
> > 601216e "mwifiex: process RX packets in SDIO IRQ thread directly"
> > introduced a command timeout issue which can be reproduced easily on
> > an AM33xx platform using a test application written by Daniel Mack:
> >
> > https://gist.github.com/zonque/6579314
>
> Actually, just out of pure curiosity, I would be interested whether the
> issue is also as easily reproducible on other platform like Chromebooks.
> Could anyone give that a try maybe?
>
> I would hesitate to say "easily". Even on a kernel before your change,
> running your test application
That might be a dumb remark, but you noticed that the interface name in
the code doesn't actually match the name of the interface mwifiex
creates by default? We changed that to "wlan0" in our system to bring it
in line with other platforms.
I changed the test tool in the gist so it requires you to pass the name
as first argument.
Daniel
next prev parent reply other threads:[~2013-09-28 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 17:55 [PATCH 3.12] mwifiex: fix SDIO interrupt lost issue Bing Zhao
2013-09-27 18:55 ` Daniel Mack
[not found] ` <CAMcMvsjFurVFS2f1zCPt0uqh2gCYAvHOvos-pY=k06=ynDH=aQ@mail.gmail.com>
2013-09-28 9:46 ` Daniel Mack [this message]
2013-10-15 10:38 ` Daniel Mack
2013-10-15 16:59 ` John W. Linville
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=5246A56C.6030909@gmail.com \
--to=zonque@gmail.com \
--cc=afenkart@gmail.com \
--cc=akarwar@marvell.com \
--cc=bzhao@marvell.com \
--cc=dgreid@chromium.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=pstew@chromium.org \
--cc=s.neumann@raumfeld.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).