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>,
<devicetree@vger.kernel.org>,
Wei-Ning Huang <wnhuang@chromium.org>,
Xinming Hu <huxm@marvell.com>
Subject: Re: [PATCH v5 2/4] mwifiex: add platform specific wakeup interrupt support
Date: Wed, 30 Mar 2016 15:38:44 +0300 [thread overview]
Message-ID: <87a8lg5eej.fsf@purkki.adurom.net> (raw)
In-Reply-To: <1458299032-31929-2-git-send-email-akarwar@marvell.com> (Amitkumar Karwar's message of "Fri, 18 Mar 2016 04:03:52 -0700")
Amitkumar Karwar <akarwar@marvell.com> writes:
> From: Xinming Hu <huxm@marvell.com>
>
> On some arm-based platforms, we need to configure platform specific
> parameters by device tree node and also define our node as a child
> node of parent SDIO host controller.
> This patch parses these parameters from device tree. It includes
> calibration data dowoload to firmware, wakeup pin configured to firmware,
> and soc specific wake up gpio, which will be set as wakeup interrupt pin.
>
> Signed-off-by: Xinming Hu <huxm@marvell.com>
> Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
I only see patch 2, where are the rest three? Also it's not clear what's
the plan with this patchset.
--
Kalle Valo
next prev parent reply other threads:[~2016-03-30 12:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 11:03 [PATCH v5 1/2] dt: bindings: add MARVELL's sd8xxx wireless device Amitkumar Karwar
2016-03-18 11:03 ` [PATCH v5 2/4] mwifiex: add platform specific wakeup interrupt support Amitkumar Karwar
2016-03-18 17:18 ` Wei-Ning Huang
2016-03-30 12:38 ` Kalle Valo [this message]
2016-03-30 12:50 ` Amitkumar Karwar
2016-03-20 0:50 ` [PATCH v5 1/2] dt: bindings: add MARVELL's sd8xxx wireless device Rob Herring
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=87a8lg5eej.fsf@purkki.adurom.net \
--to=kvalo@codeaurora.org \
--cc=akarwar@marvell.com \
--cc=cluo@marvell.com \
--cc=devicetree@vger.kernel.org \
--cc=huxm@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nishants@marvell.com \
--cc=wnhuang@chromium.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