public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH rtw-next 6/7] wifi: rtw89: 8922d: add set channel of BB part
Date: Tue, 24 Mar 2026 00:49:37 +0000	[thread overview]
Message-ID: <620d877ececd4af497e196166102f06d@realtek.com> (raw)
In-Reply-To: <897a086c-437b-44d7-8433-8c0feea814f3@gmail.com>

Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> On 23/03/2026 05:25, Ping-Ke Shih wrote:
> > The set channel of BB part is the main part, which according to channel
> > and bandwidth to configure CCK SCO, RX gain of LNA and TIA programmed
> > in efuse for CCK and OFDM rate, and spur elimination of CSI and NBI tones.
> >
> > Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
> > ---
> >  drivers/net/wireless/realtek/rtw89/core.h     |   2 +
> >  drivers/net/wireless/realtek/rtw89/reg.h      |  64 +-
> >  drivers/net/wireless/realtek/rtw89/rtw8922d.c | 820 ++++++++++++++++++
> >  3 files changed, 885 insertions(+), 1 deletion(-)
> >
> 
> [..]
> 
> > +
> > +static const struct rtw89_nbi_reg_def rtw8922d_nbi_reg_def[] = {
> > +     [RF_PATH_A] = {
> > +             .notch1_idx = {0x241A0, 0xFF},
> > +             .notch1_frac_idx = {0x241A0, 0xC00},
> > +             .notch1_en = {0x241A0, 0x1000},
> > +             .notch2_idx = {0x241AC, 0xFF},
> > +             .notch2_frac_idx = {0x241AC, 0xC00},
> > +             .notch2_en = {0x241AC, 0x1000},
> > +     },
> > +     [RF_PATH_B] = {
> > +             .notch1_idx = {0x245A0, 0xFF},
> > +             .notch1_frac_idx = {0x241A0, 0xC00},
> 
> Is that supposed to be 0x245A0 ?

Thanks for the finding. I'll fix it by v2.

> 
> > +             .notch1_en = {0x245A0, 0x1000},
> > +             .notch2_idx = {0x245AC, 0xFF},
> > +             .notch2_frac_idx = {0x245AC, 0xC00},
> > +             .notch2_en = {0x245AC, 0x1000},
> > +     },
> > +};
> > +
> 
> [...]

  reply	other threads:[~2026-03-24  0:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23  3:25 [PATCH rtw-next 0/7] wifi: rtw89: 8922d: add RTL8922D common routine part 1 Ping-Ke Shih
2026-03-23  3:25 ` [PATCH rtw-next 1/7] wifi: rtw89: 8922d: add definition of quota, registers and efuse block Ping-Ke Shih
2026-03-23  3:25 ` [PATCH rtw-next 2/7] wifi: rtw89: 8922d: add power on/off functions Ping-Ke Shih
2026-03-23  3:25 ` [PATCH rtw-next 3/7] wifi: rtw89: 8922d: define efuse map and read necessary fields Ping-Ke Shih
2026-03-23  3:25 ` [PATCH rtw-next 4/7] wifi: rtw89: 8922d: read and configure RF by calibration data from efuse physical map Ping-Ke Shih
2026-03-23  3:25 ` [PATCH rtw-next 5/7] wifi: rtw89: 8922d: add set channel of MAC part Ping-Ke Shih
2026-03-23  3:25 ` [PATCH rtw-next 6/7] wifi: rtw89: 8922d: add set channel of BB part Ping-Ke Shih
2026-03-23 10:53   ` Bitterblue Smith
2026-03-24  0:49     ` Ping-Ke Shih [this message]
2026-03-23  3:25 ` [PATCH rtw-next 7/7] wifi: rtw89: 8922d: add set channel of RF part Ping-Ke Shih

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=620d877ececd4af497e196166102f06d@realtek.com \
    --to=pkshih@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rtl8821cerfe2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox