All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Maxim Skokov <skokovmaksimevg@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: rtw89: WOW_CPUIO_RX_CTRL is never answered on RTL8851B
Date: Tue, 15 Sep 2026 00:40:11 +0000	[thread overview]
Message-ID: <95af665973144da2b527b9d6d445a6ca@realtek.com> (raw)
In-Reply-To: <20260912193939.5565-1-skokovmaksimevg@gmail.com>

Maxim Skokov <skokovmaksimevg@gmail.com> wrote:
> 
> but rtw89_fw_feat_list only carries
> 
>         __CFG_FW_FEAT(RTL8852A, lt, 0, 13, 37, 0, NO_WOW_CPU_IO_RX),
>         __CFG_FW_FEAT(RTL8852B, lt, 0, 29, 30, 0, NO_WOW_CPU_IO_RX),
> 
> and nothing for RTL8851B.

I'll send a patch to add this:

__CFG_FW_FEAT(RTL8851B, lt, 0, 29, 57, 0, NO_WOW_CPU_IO_RX),

> 
> One unrelated note from the same trace: "Unknown wakeup reason 0" is not
> a failed AoAC read. AOAC_RPT_1 and AOAC_RPT_2 both succeed, and
> rtw89_wow_show_wakeup_reason() reads the reason straight from
> wow_reason_reg, which holds 0 because the card was not the wake source
> here, the RTC alarm was. The switch has no case for that and falls
> through to the warning.

I'll check this internally if it is possible to avoid the "reason 0" 
message. 



      reply	other threads:[~2026-09-15  0:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-12 19:39 rtw89: WOW_CPUIO_RX_CTRL is never answered on RTL8851B Maxim Skokov
2026-09-15  0:40 ` Ping-Ke Shih [this message]

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=95af665973144da2b527b9d6d445a6ca@realtek.com \
    --to=pkshih@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=skokovmaksimevg@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.