From: Kalle Valo <kvalo@codeaurora.org>
To: "Fu\, Zhonghui" <zhonghui.fu@linux.intel.com>
Cc: "brudley\@broadcom.com" <brudley@broadcom.com>,
Arend van Spriel <arend@broadcom.com>,
Franky Lin <frankyl@broadcom.com>,
"meuleman\@broadcom.com" <meuleman@broadcom.com>,
"pieterpg\@broadcom.com" <pieterpg@broadcom.com>,
"hdegoede\@redhat.com" <hdegoede@redhat.com>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>,
"brcm80211-dev-list\@broadcom.com"
<brcm80211-dev-list@broadcom.com>,
"netdev\@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] brcmfmac: prohibit ACPI power management for brcmfmac driver
Date: Tue, 26 May 2015 13:46:50 +0300 [thread overview]
Message-ID: <878ucb39b9.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <555016DC.804@linux.intel.com> (Zhonghui Fu's message of "Mon, 11 May 2015 10:41:32 +0800")
"Fu, Zhonghui" <zhonghui.fu@linux.intel.com> writes:
> ACPI will manage WiFi chip's power state during suspend/resume
> process on some tablet platforms(such as ASUS T100TA). This is
> not supported by brcmfmac driver now, and the context of WiFi
> chip will be damaged after resume. This patch informs ACPI not
> to manage WiFi chip's power state.
>
> Signed-off-by: Zhonghui Fu <zhonghui.fu@linux.intel.com>
> Acked-by: Arend van Spriel <arend@broadcom.com>
Thanks, applied to wireless-drivers-next.git.
--
Kalle Valo
prev parent reply other threads:[~2015-05-26 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 2:41 [PATCH v3] brcmfmac: prohibit ACPI power management for brcmfmac driver Fu, Zhonghui
[not found] ` <555016DC.804-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2015-05-18 6:26 ` Fu, Zhonghui
2015-05-20 9:02 ` Arend van Spriel
2015-05-26 3:52 ` Fu, Zhonghui
2015-05-26 10:46 ` 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=878ucb39b9.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brudley@broadcom.com \
--cc=frankyl@broadcom.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=meuleman@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pieterpg@broadcom.com \
--cc=zhonghui.fu@linux.intel.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).