From: Martin Kaiser <martin@kaiser.cx>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Phillip Potter <phil@philpotter.co.uk>,
Michael Straube <straube.linux@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Martin Kaiser <martin@kaiser.cx>
Subject: [PATCH 0/8] staging: r8188eu: more rf cleanups
Date: Sat, 5 Feb 2022 12:37:33 +0100 [thread overview]
Message-ID: <20220205113741.379070-1-martin@kaiser.cx> (raw)
Here's another set with cleanups of the rf configuration code.
The last of the patches is "testing the water". It seems that this driver
uses only RF_PATH_A and we can eventually drop all RF_PATH_B handling. At
the moment, the only way to access RF_PATH_B registers is via private
ioctls. I'd like to restrict them to path A.
As usual, this series was t ested with EdimaxV2 on an arm32 embedded system.
Martin Kaiser (8):
staging: r8188eu: TXPowercount is set but not used
staging: r8188eu: TXPowerTrackingCallbackCnt is set but not used
staging: r8188eu: bTXPowerTrackingInit is set but not used
staging: r8188eu: bTXPowerTracking is set but not used
staging: r8188eu: remove constant rf variable
staging: r8188eu: RfRegChnlVal[1] is set but not used
staging: r8188eu: use a define for the radio path
staging: r8188eu: limit rf register writes to path a
drivers/staging/r8188eu/hal/HalPhyRf_8188e.c | 24 ++++++-------------
drivers/staging/r8188eu/hal/odm.c | 3 ---
drivers/staging/r8188eu/hal/rtl8188e_phycfg.c | 4 ++--
drivers/staging/r8188eu/hal/rtl8188e_rf6052.c | 8 +++----
drivers/staging/r8188eu/hal/usb_halinit.c | 3 +--
drivers/staging/r8188eu/include/odm.h | 4 ----
.../staging/r8188eu/include/rtl8188e_hal.h | 2 +-
drivers/staging/r8188eu/os_dep/ioctl_linux.c | 3 +++
8 files changed, 18 insertions(+), 33 deletions(-)
--
2.30.2
next reply other threads:[~2022-02-05 11:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 11:37 Martin Kaiser [this message]
2022-02-05 11:37 ` [PATCH 1/8] staging: r8188eu: TXPowercount is set but not used Martin Kaiser
2022-02-05 11:37 ` [PATCH 2/8] staging: r8188eu: TXPowerTrackingCallbackCnt " Martin Kaiser
2022-02-05 11:37 ` [PATCH 3/8] staging: r8188eu: bTXPowerTrackingInit " Martin Kaiser
2022-02-05 11:37 ` [PATCH 4/8] staging: r8188eu: bTXPowerTracking " Martin Kaiser
2022-02-05 11:37 ` [PATCH 5/8] staging: r8188eu: remove constant rf variable Martin Kaiser
2022-02-05 11:37 ` [PATCH 6/8] staging: r8188eu: RfRegChnlVal[1] is set but not used Martin Kaiser
2022-02-05 11:37 ` [PATCH 7/8] staging: r8188eu: use a define for the radio path Martin Kaiser
2022-02-05 11:37 ` [PATCH 8/8] staging: r8188eu: limit rf register writes to path a Martin Kaiser
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=20220205113741.379070-1-martin@kaiser.cx \
--to=martin@kaiser.cx \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=phil@philpotter.co.uk \
--cc=straube.linux@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
all inboxes | Powered by JetHome®