From: Rajat Jain <rajatja@google.com>
To: Amitkumar Karwar <akarwar@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>,
Kalle Valo <kvalo@codeaurora.org>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
Xinming Hu <huxm@marvell.com>
Cc: Rajat Jain <rajatja@google.com>,
Brian Norris <briannorris@google.com>,
rajatxjain@gmail.com
Subject: [PATCH 0/3] mwifiex: Make WoWLAN a common feature
Date: Mon, 24 Oct 2016 10:56:50 -0700 [thread overview]
Message-ID: <1477331813-42151-1-git-send-email-rajatja@google.com> (raw)
I have a Marvell card on the PCIe bus that needs to support
WoWLAN (wake-on-wireless-LAN) feature. This is a feature offered
by the "core" mwifiex card and is not specific to an interface
(pcie/sdio/usb).
Currently the code to parse the WowLAN pin, and activate it
resides only in sdio.c [mostly commit ce4f6f0c353b ("mwifiex: add
platform specific wakeup interrupt support")]. I started by
copying all that code & data structures in pcie.c/pcie.h but then
realized that the we should probably have it common since the
feature is not interface specific.
Further, I noticed that interface driver had no interest in
device trees since there are no properties specific to interfaces.
Currently the only properties needed, are the common ones needed
by the core mwifiex.
This patch set thus introduces mwifiex_probe_of() to parse the
common properties, and then moves the WowLAN specific code to the
common module so that all the interfaces can use it. Essentially
this is a single logical patch that has been split up into
multiple patches only for the reason of simplicity and code
reviews.
This is currently rebased on the top of Linus' tree with the
following 2 patches applied:
https://patchwork.kernel.org/patch/9362275/
https://patchwork.kernel.org/patch/9390225/
Rajat Jain (3):
mwifiex: Allow mwifiex early access to device structure
mwifiex: Introduce mwifiex_probe_of() to parse common properties
mwifiex: Enable WoWLAN for both sdio and pcie
drivers/net/wireless/marvell/mwifiex/main.c | 58 ++++++++++++++++++-
drivers/net/wireless/marvell/mwifiex/main.h | 28 ++++++++-
drivers/net/wireless/marvell/mwifiex/pcie.c | 8 ++-
drivers/net/wireless/marvell/mwifiex/sdio.c | 79 +++-----------------------
drivers/net/wireless/marvell/mwifiex/sdio.h | 8 ---
drivers/net/wireless/marvell/mwifiex/sta_cmd.c | 5 +-
drivers/net/wireless/marvell/mwifiex/usb.c | 3 +-
7 files changed, 99 insertions(+), 90 deletions(-)
--
2.8.0.rc3.226.g39d4020
next reply other threads:[~2016-10-24 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 17:56 Rajat Jain [this message]
2016-10-24 17:56 ` [PATCH 1/3] mwifiex: Allow mwifiex early access to device structure Rajat Jain
[not found] ` <1477331813-42151-1-git-send-email-rajatja-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2016-10-24 17:56 ` [PATCH 2/3] mwifiex: Introduce mwifiex_probe_of() to parse common properties Rajat Jain
2016-10-24 17:56 ` [PATCH 3/3] mwifiex: Enable WoWLAN for both sdio and pcie Rajat Jain
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=1477331813-42151-1-git-send-email-rajatja@google.com \
--to=rajatja@google.com \
--cc=akarwar@marvell.com \
--cc=briannorris@google.com \
--cc=huxm@marvell.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nishants@marvell.com \
--cc=rajatxjain@gmail.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).