From: Kalle Valo <kvalo@kernel.org>
To: Manikanta Pubbisetty <quic_mpubbise@quicinc.com>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v4 3/3] ath11k: Enable low power mode when WLAN is not active
Date: Mon, 27 Feb 2023 13:59:02 +0200 [thread overview]
Message-ID: <87v8jnqpyx.fsf@kernel.org> (raw)
In-Reply-To: <9efc2082-d46d-5d57-d275-1cb47277f639@quicinc.com> (Manikanta Pubbisetty's message of "Mon, 27 Feb 2023 16:19:08 +0530")
Manikanta Pubbisetty <quic_mpubbise@quicinc.com> writes:
>> Also I want to mention that I suspect eventually we have to always power
>> off the firmware during suspend to get hibernation working:
>
> This patch will power off the firmware for WCN6750. I'm not sure how
> to get that working for other ath11k devices.
Oh, I didn't release that. If you can, try to clarify the commit log on
this part. For example, "for suspend we run command FOO_OFF which means
that the power from the firmware is complete turned off". Or maybe just
read them too hastily, but still having clear (and simple) commit logs
help understanding the issue.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-02-27 11:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 6:01 [PATCH v4 0/3] Enable low power mode when WLAN is not active Manikanta Pubbisetty
2023-02-03 6:01 ` [PATCH v4 1/3] ath11k: Fix double free issue during SRNG deinit Manikanta Pubbisetty
2023-02-03 6:01 ` [PATCH v4 2/3] ath11k: Move hardware initialization logic to start() Manikanta Pubbisetty
2023-02-03 6:01 ` [PATCH v4 3/3] ath11k: Enable low power mode when WLAN is not active Manikanta Pubbisetty
2023-02-24 14:46 ` Kalle Valo
2023-02-27 10:42 ` Manikanta Pubbisetty
2023-03-13 7:19 ` Manikanta Pubbisetty
2023-02-24 14:50 ` Kalle Valo
2023-02-27 10:49 ` Manikanta Pubbisetty
2023-02-27 11:59 ` Kalle Valo [this message]
2023-02-24 14:54 ` [PATCH v4 0/3] " Kalle Valo
2023-02-27 10:49 ` Manikanta Pubbisetty
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=87v8jnqpyx.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_mpubbise@quicinc.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).