From: Larry Finger <Larry.Finger@lwfinger.net>
To: Forest Bond <forest@alittletooquiet.net>
Cc: linux-wireless@vger.kernel.org,
Chaoming Li <chaoming_li@realsil.com.cn>,
Jingjun Wu <jingjun_wu@realsil.com.cn>
Subject: Re: [PATCH 1/2] rtl8192de: Clean up and fix 92D cut version constants and macros.
Date: Mon, 02 Apr 2012 10:46:42 -0500 [thread overview]
Message-ID: <4F79C9E2.5000109@lwfinger.net> (raw)
In-Reply-To: <20120402142525.GA20611@alittletooquiet.net>
On 04/02/2012 09:25 AM, Forest Bond wrote:
> From: Forest Bond<forest.bond@rapidrollout.com>
>
> The previous definitions included both {B,C,D,E}_CUT_VERSION and
> CHIP_92D_{C,D}_CUT with conflicting values for the C and D cut versions,
> and literal hex values were used in the IS_92D_{C,D,E}_CUT macros. So
> we clean all this up and in doing so enable cut-specific code paths for
> cuts C and D, which would not have been executed because the
> CHIP_92D_{C,D}_CUT constants were wrong and the cut version was thus
> recorded incorrectly.
>
> Signed-off-by: Forest Bond<forest.bond@rapidrollout.com>
Thanks for working on this driver. As there has been no traffic regarding its
usage, I have not done much with it. I am in possession of two models,
RTL8192DE-VC and RTL8192DE-VS. My recollection is that the VS did not work, but
I need to test again. Perhaps your changes are what was needed.
> ---
> drivers/net/wireless/rtlwifi/rtl8192de/def.h | 17 ++++++++---------
> 1 files changed, 8 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/net/wireless/rtlwifi/rtl8192de/def.h b/drivers/net/wireless/rtlwifi/rtl8192de/def.h
> index eafdf76..260ac7e 100644
> --- a/drivers/net/wireless/rtlwifi/rtl8192de/def.h
> +++ b/drivers/net/wireless/rtlwifi/rtl8192de/def.h
> @@ -151,9 +151,6 @@ enum version_8192d {
>
> /* for 92D */
> #define CHIP_92D_SINGLEPHY BIT(9)
> -#define C_CUT_VERSION BIT(13)
> -#define D_CUT_VERSION ((BIT(12)|BIT(13)))
> -#define E_CUT_VERSION BIT(14)
>
> /* Chip specific */
> #define CHIP_BONDING_IDENTIFIER(_value) (((_value)>>22)&0x3)
> @@ -173,7 +170,11 @@ enum version_8192d {
> #define RF_TYPE_1T2R BIT(4)
> #define RF_TYPE_2T2R BIT(5)
> #define CHIP_VENDOR_UMC BIT(7)
> -#define B_CUT_VERSION BIT(12)
> +#define CHIP_92D_A_CUT (0<<12)
> +#define CHIP_92D_B_CUT (1<<12)
> +#define CHIP_92D_C_CUT (2<<12)
> +#define CHIP_92D_D_CUT (3<<12)
> +#define CHIP_92D_E_CUT (4<<12)
Please keep the BIT(X) notation here to make it consistent.
>
> /* MASK */
> #define IC_TYPE_MASK (BIT(0)|BIT(1)|BIT(2))
> @@ -205,15 +206,13 @@ enum version_8192d {
> CHIP_92D) ? true : false)
> #define IS_92D_C_CUT(version) ((IS_92D(version)) ? \
> ((GET_CVID_CUT_VERSION(version) == \
> - 0x2000) ? true : false) : false)
> + CHIP_92D_C_CUT) ? true : false) : false)
> #define IS_92D_D_CUT(version) ((IS_92D(version)) ? \
> ((GET_CVID_CUT_VERSION(version) == \
> - 0x3000) ? true : false) : false)
> + CHIP_92D_D_CUT) ? true : false) : false)
> #define IS_92D_E_CUT(version) ((IS_92D(version)) ? \
> ((GET_CVID_CUT_VERSION(version) == \
> - 0x4000) ? true : false) : false)
> -#define CHIP_92D_C_CUT BIT(10)
> -#define CHIP_92D_D_CUT BIT(11)
> + CHIP_92D_E_CUT) ? true : false) : false)
>
> enum rf_optype {
> RF_OP_BY_SW_3WIRE = 0,
These IS_92D_X_CUT macros are ugly, but I don't see any way to improve them. I
guess we are stuck with them.
Larry
next prev parent reply other threads:[~2012-04-02 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 14:25 [PATCH 1/2] rtl8192de: Clean up and fix 92D cut version constants and macros Forest Bond
2012-04-02 15:46 ` Larry Finger [this message]
2012-04-02 17:54 ` Larry Finger
2012-04-02 17:57 ` Forest Bond
2012-04-02 18:04 ` Larry Finger
2012-04-05 18:06 ` Forest Bond
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=4F79C9E2.5000109@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--cc=forest@alittletooquiet.net \
--cc=jingjun_wu@realsil.com.cn \
--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;
as well as URLs for NNTP newsgroup(s).