From: "Jérôme Pouiller" <jerome.pouiller@silabs.com>
To: linux-wireless@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>
Cc: linux-kernel@vger.kernel.org, Kalle Valo <kvalo@kernel.org>,
linux-devel@silabs.com
Subject: Re: [PATCH v2 0/5] wfx: add support for WoWLAN on Silabs WF200
Date: Tue, 04 Mar 2025 16:22:55 +0100 [thread overview]
Message-ID: <2018315.usQuhbGJ8B@nb0018864> (raw)
In-Reply-To: <f808c48596ae1929c62704c226fb109cc03bbd2a.camel@sipsolutions.net>
On Monday 3 March 2025 09:20:11 CET Johannes Berg wrote:
> On Sun, 2025-03-02 at 15:47 +0100, Jérôme Pouiller wrote:
> > This is the initial support for Wake-on-WLAN of Silicon WF200 chipset. This
> > version focus on the power management control. For now, the filtering
> > capabilities of the chip are not exposed. So any multicast frame (= any ARP
> > request) will wake up the host.
> >
> > I have this series of patches in my git tree for a while. I hesitated to
> > send it because the code is based on a proof of concept and I don't have
> > access to the hardware anymore.
> >
> > Therefore, this feature is experimental. However, the only way to reach
> > this code is to run "iw phy phy0 wowlan enable" or explicitly enable it in
> > /sys. So, I believe it makes sense to merged it in the stable tree. Thus, I
> > hope some users will be able to report their success (or their failure).
> >
> > v2:
> > - Fix compilation issue reported by "kernel test robot"[1]. Member
> > 'wowlan' only exist if CONFIG_PM.
>
> You should probably check patchwork too - now that we're running some
> checks, a missing 'static' jumped out:
>
> https://urldefense.com/v3/__https://patchwork.kernel.org/project/linux-wireless/list/?series=939353__;!!N30Cs7Jr!Ru1BMHVjq3TxTX0c6bA3EDM0EzKM7JcHyeEUJ3_-J4TFLsLpY-jDSudnehLp3DzQ4Nutky9oKreyyjRstvmwuPVT0tM$
Patchwork also reports two warnings that I am going to ignore:
- "Target tree name not specified in the subject", I assume it
is "wireless-next", but in the doubt I prefer to refrain.
- Lines are larger then 80 columns. Checkpatch.pl now accepts up
to 100 columns. I am not aware any local exception in net/, right?
--
Jérôme Pouiller
next prev parent reply other threads:[~2025-03-04 15:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 14:47 [PATCH v2 0/5] wfx: add support for WoWLAN on Silabs WF200 Jérôme Pouiller
2025-03-02 14:47 ` [PATCH v2 1/5] wifi: wfx: align declarations between bus_spi.c and bus_sdio.c Jérôme Pouiller
2025-03-02 14:47 ` [PATCH v2 2/5] wifi: wfx: declare support for WoWLAN Jérôme Pouiller
2025-03-03 15:05 ` kernel test robot
2025-03-03 16:28 ` kernel test robot
2025-03-02 14:47 ` [PATCH v2 3/5] wifi: wfx: allow SPI device to wake up the host Jérôme Pouiller
2025-03-02 14:47 ` [PATCH v2 4/5] wifi: wfx: allow SDIO " Jérôme Pouiller
2025-03-02 14:47 ` [PATCH v2 5/5] wifi: wfx: allow to enable WoWLAN using NL80211 Jérôme Pouiller
2025-03-03 8:20 ` [PATCH v2 0/5] wfx: add support for WoWLAN on Silabs WF200 Johannes Berg
2025-03-04 15:22 ` Jérôme Pouiller [this message]
2025-03-05 7:40 ` Johannes Berg
2025-03-05 15:18 ` Jérôme Pouiller
2025-03-06 8:10 ` Johannes Berg
2025-03-06 8:35 ` Jérôme Pouiller
2025-03-06 8:37 ` Johannes Berg
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=2018315.usQuhbGJ8B@nb0018864 \
--to=jerome.pouiller@silabs.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-devel@silabs.com \
--cc=linux-kernel@vger.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