From: Adrian Hunter <adrian.hunter@intel.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Arend van Spriel <arend@broadcom.com>
Cc: linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH 0/2] sdio: Prevent re-tuning conflicting with custom sleep
Date: Thu, 26 Nov 2015 14:58:38 +0200 [thread overview]
Message-ID: <565701FE.9010403@intel.com> (raw)
In-Reply-To: <1430232341-8307-1-git-send-email-adrian.hunter@intel.com>
On 28/04/15 17:45, Adrian Hunter wrote:
> Here are 2 patches that allow brcmfmac to awake from a
> custom sleep state that conflicts with re-tuning.
>
> The first patch adds sdio_retune_hold_now() and
> sdio_retune_release(). They are used in the 2nd patch
> to prevent re-tuning for the 'wake-up' command.
>
>
> Adrian Hunter (2):
> mmc: core: Add functions for SDIO to hold re-tuning
> brcmfmac: Prevent re-tuning conflicting with 'wake-up'
>
> drivers/mmc/core/host.c | 6 ++++++
> drivers/mmc/core/host.h | 1 +
> drivers/mmc/core/sdio_io.c | 13 +++++++++++++
> drivers/net/wireless/brcm80211/brcmfmac/sdio.c | 6 ++++++
> include/linux/mmc/sdio_func.h | 3 +++
> 5 files changed, 29 insertions(+)
Hi
These patches still apply and are still needed.
Can they be applied?
Regards
Adrian
next prev parent reply other threads:[~2015-11-26 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 14:45 [PATCH 0/2] sdio: Prevent re-tuning conflicting with custom sleep Adrian Hunter
2015-04-28 14:45 ` [PATCH 1/2] mmc: core: Add functions for SDIO to hold re-tuning Adrian Hunter
2015-04-28 14:45 ` [PATCH 2/2] brcmfmac: Prevent re-tuning conflicting with 'wake-up' Adrian Hunter
2015-11-26 12:58 ` Adrian Hunter [this message]
2015-11-27 14:06 ` [PATCH 0/2] sdio: Prevent re-tuning conflicting with custom sleep Ulf Hansson
2016-01-19 9:51 ` Adrian Hunter
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=565701FE.9010403@intel.com \
--to=adrian.hunter@intel.com \
--cc=arend@broadcom.com \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.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).