Linux wireless drivers development
 help / color / mirror / Atom feed
From: Alexander Fischer <alexander@fischermail.me>
To: linux-wireless@vger.kernel.org
Cc: Arend van Spriel <arend.vanspriel@broadcom.com>,
	brcm80211@lists.linux.dev, brcm80211-dev-list.pdl@broadcom.com,
	linux-kernel@vger.kernel.org, Andre Eikmeyer <dev@deq.rocks>,
	Alexander Fischer <alexander@fischermail.me>
Subject: Re: [PATCH wireless-next] wifi: brcmfmac: allow opting into PM_MAX power management
Date: Fri, 14 Aug 2026 22:51:15 +0200	[thread overview]
Message-ID: <20260814205115.799977-1-alexander@fischermail.me> (raw)
In-Reply-To: <20260810150552.25375-1-alexander@fischermail.me>

Hello,

I would like to withdraw this patch.

Further testing on BCM4364 showed intermittent latency spikes of about
50-250 ms with PM_MAX. The connection can work normally for extended
periods, but the issue is reproducible and disappears after switching
back to PM_FAST. This invalidates my earlier statement that I had
observed no latency regression.

Given this trade-off, I no longer think exposing PM_MAX through this new
module parameter is worthwhile, and I do not plan to send a v2. Please
drop the patch.

pw-bot: changes-requested

Sorry for the noise, and thanks for your time.

Regards,
Alexander

  reply	other threads:[~2026-08-14 20:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-10 15:05 [PATCH wireless-next] wifi: brcmfmac: allow opting into PM_MAX power management Alexander Fischer
2026-08-14 20:51 ` Alexander Fischer [this message]
2026-08-16  9:27   ` Arend van Spriel

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=20260814205115.799977-1-alexander@fischermail.me \
    --to=alexander@fischermail.me \
    --cc=arend.vanspriel@broadcom.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=brcm80211@lists.linux.dev \
    --cc=dev@deq.rocks \
    --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