Marek Vasut <marex@xxxxxxx> writes: > The WILC3000 can suspend and enter low power state. According to local > measurements, the WILC3000 consumes the same amount of power if the slot > is powered up and WILC3000 is suspended, and if the WILC3000 is powered > off. Use the former option, keep the WILC3000 powered up as that allows > for things like WoWlan to work. > > Note that this is tested on WILC3000 only, not on WILC1000 . > > Signed-off-by: Marek Vasut <marex@xxxxxxx> > --- > Cc: Ajay Singh <ajay.kathat@xxxxxxxxxxxxx> > Cc: Alexis Lothoré <alexis.lothore@xxxxxxxxxxx> > Cc: Claudiu Beznea <claudiu.beznea@xxxxxxxxx> > Cc: Kalle Valo <kvalo@xxxxxxxxxx> > Cc: Marek Vasut <marex@xxxxxxx> > Cc: linux-wireless@xxxxxxxxxxxxxxx > --- > V2: Rebase on next-20240926 BTW I recommend using wireless-next as the baseline for wireless patches. For example, wireless-next is not pulled to linux-next during merge windows or other patches in linux-next might create unnecessary conflicts. Of course most of the cases using linux-next is fine. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
