From: Marek Vasut <marex@denx.de>
To: Kalle Valo <kvalo@kernel.org>
Cc: Ajay.Kathat@microchip.com, alexis.lothore@bootlin.com,
linux-wireless@vger.kernel.org, claudiu.beznea@tuxon.dev
Subject: Re: [PATCH] wifi: wilc1000: Keep slot powered on during suspend/resume
Date: Fri, 6 Sep 2024 20:23:13 +0200 [thread overview]
Message-ID: <49541dc5-e2ab-4d7d-aaa8-ae76e580a39e@denx.de> (raw)
In-Reply-To: <87tteuimqc.fsf@kernel.org>
On 9/5/24 9:27 AM, Kalle Valo wrote:
> Marek Vasut <marex@denx.de> writes:
>
>>>>> Are you also taking into account hibernation? During hibernation the
>>>>> device will be powered off. I can't remember the details right now but
>>>>> wanted to mention this.
>>>>
>>>> I don't think I am. Isn't hibernation actually a full shutdown, so the
>>>> hardware does get reinitialized ?
>>> I don't know how it works exactly nor what you exactly mean with
>>> reinitalized.
>>
>> My understanding is that hibernation is suspend-to-disk, isn't it ?
>
> Yes, that's what I mean.
>
>> (that's not something that is even available on my hardware)
>
> Yeah, I'm guessing wilc1000 is used more in embedded enviroments where
> hibernation is not really an important, it's used more in laptops. So I
> guess it won't be a big problem if wilc1000 doesn't support hibernation
> but please try to keep it in mind still.
>
>> Doesn't the hardware get completely turned OFF during suspend-to-disk
>> and then turned ON (and therefore initialized again) on
>> resume-from-disk?
>
> I'm not sure how it works exactly but my experience is that for
> hibernation a driver cannot assume that the firmware is running during
> resume.
>
>>> But at least with ath11k hibernation didn't work when it
>>> left the firmware running during suspend.
>>
>> Is there a thread on lore or some details of this you could point me to?
>
> See commit 166a490f59ac ("wifi: ath11k: support hibernation") and the
> commits before that. I'm sure that there's more info about hibernation
> but don't have any pointers.
Ah, thank you.
The firmware reloading support should be addressed by some sort of
future variant of patch Ajay sent as attachment in [1], that should then
also deal with the hibernation part. I asked them to post the patch
properly to the ML.
What about this patch, it fixes suspend/resume for me and with a fix to
the atmel controller I suggested to Alexis in this thread, it should not
have any adverse effects .
[1]
https://lore.kernel.org/all/2bbdc690-aec5-4a11-893e-01270c6d5b84@microchip.com/
next prev parent reply other threads:[~2024-09-06 18:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 18:37 [PATCH] wifi: wilc1000: Keep slot powered on during suspend/resume Marek Vasut
2024-08-27 9:53 ` Alexis Lothoré
2024-08-27 15:20 ` Marek Vasut
2024-08-28 7:42 ` Alexis Lothoré
2024-08-29 1:45 ` Ajay.Kathat
2024-08-29 2:45 ` Marek Vasut
2024-08-29 5:51 ` Ajay.Kathat
2024-08-29 15:38 ` Marek Vasut
2024-08-29 16:32 ` Kalle Valo
2024-08-29 22:23 ` Marek Vasut
2024-09-02 16:32 ` Kalle Valo
2024-09-02 16:43 ` Marek Vasut
2024-09-05 7:27 ` Kalle Valo
2024-09-06 18:23 ` Marek Vasut [this message]
2024-08-31 5:22 ` Ajay.Kathat
2024-08-31 21:18 ` Marek Vasut
2024-09-04 17:09 ` Ajay.Kathat
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=49541dc5-e2ab-4d7d-aaa8-ae76e580a39e@denx.de \
--to=marex@denx.de \
--cc=Ajay.Kathat@microchip.com \
--cc=alexis.lothore@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.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