From: Kalle Valo <kvalo@codeaurora.org>
To: Amitkumar Karwar <akarwar@marvell.com>
Cc: <linux-wireless@vger.kernel.org>, Cathy Luo <cluo@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>,
chunfan chen <jeffc@marvell.com>,
Amitkumar Karwar <akarwar@marvell.com>
Subject: Re: [v2,1/3] mwifiex: firmware download enhancements
Date: Fri, 29 Jan 2016 09:14:25 +0000 (UTC) [thread overview]
Message-ID: <20160129091425.73F1C6045B@smtp.codeaurora.org> (raw)
In-Reply-To: <1452152449-29803-1-git-send-email-akarwar@marvell.com>
> From: chunfan chen <jeffc@marvell.com>
>
> Same chip is being used by WLAN as well as bluetooth
> drivers. Each driver needs to check during initialisation
> if firmware is already active or it needs to be freshly
> downloaded. If one driver has started downloading the
> firmware, other finds the winner flag as false.
>
> mwifiex_check_fw_status() checks firmware status and also
> check if WLAN is the winner for firmware downloading.
>
> Once we detect that other interface is downloading
> the firmware, we call this routine again with max
> poll count to wait until firmware is ready.
>
> This patch splits the routine to avoid checking
> winner status unnecessarily multiple times and ensures
> that correct messages are displayed to user.
>
> Firmware status poll count is also increased to 150.
>
> Signed-off-by: Chunfan Chen <jeffc@marvell.com>
> Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
Thanks, 3 patches applied to wireless-drivers-next.git:
2fd5c6ed0b4f mwifiex: firmware download enhancements
dc386ce76ded mwifiex: fix IBSS data path issue.
17934b6a32b2 mwifiex: add debugfs file to read chip information
Kalle Valo
prev parent reply other threads:[~2016-01-29 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 7:40 [PATCH v2 1/3] mwifiex: firmware download enhancements Amitkumar Karwar
2016-01-07 7:40 ` [PATCH v2 2/3] mwifiex: fix IBSS data path issue Amitkumar Karwar
2016-01-07 7:40 ` [PATCH v2 3/3] mwifiex: add debugfs file to read chip information Amitkumar Karwar
2016-01-29 9:14 ` Kalle Valo [this message]
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=20160129091425.73F1C6045B@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=akarwar@marvell.com \
--cc=cluo@marvell.com \
--cc=jeffc@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nishants@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.