All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Forest Bond <forest@alittletooquiet.net>
Cc: John W Linville <linville@tuxdriver.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rtlwifi: rtl8192de: Fix phy-based version calculation
Date: Fri, 13 Jul 2012 11:09:50 -0500	[thread overview]
Message-ID: <5000484E.9070700@lwfinger.net> (raw)
In-Reply-To: <20120713143551.GF9489@alittletooquiet.net>

On 07/13/2012 09:35 AM, Forest Bond wrote:
> From: Forest Bond <forest.bond@rapidrollout.com>
>
> Commit d83579e2a50ac68389e6b4c58b845c702cf37516 incorporated some
> changes from the vendor driver that made it newly important that the
> calculated hardware version correctly include the CHIP_92D bit, as all
> of the IS_92D_* macros were changed to depend on it.  However, this bit
> was being unset for dual-mac, dual-phy devices.  The vendor driver
> behavior was modified to not do this, but unfortunately this change was
> not picked up along with the others.  This caused scanning in the 2.4GHz
> band to be broken, and possibly other bugs as well.
>
> This patch brings the version calculation logic in parity with the
> vendor driver in this regard, and in doing so fixes the regression.
> However, the version calculation code in general continues to be largely
> incoherent and messy, and needs to be cleaned up.
>
> Signed-off-by: Forest Bond <forest.bond@rapidrollout.com>
> ---
>   drivers/net/wireless/rtlwifi/rtl8192de/phy.c |    6 +++---
>   1 files changed, 3 insertions(+), 3 deletions(-)

The code changes are OK; however, please resubmit with a "Cc: Stable 
<stable@vger.kernel.org> [v3.2+]" When you make that change, you can also add a 
Signed-off-by for me.

John,

If possible, please include this in the changes for 3.5.

Thanks,

Larry

>
> diff --git a/drivers/net/wireless/rtlwifi/rtl8192de/phy.c b/drivers/net/wireless/rtlwifi/rtl8192de/phy.c
> index 18380a7..4420312 100644
> --- a/drivers/net/wireless/rtlwifi/rtl8192de/phy.c
> +++ b/drivers/net/wireless/rtlwifi/rtl8192de/phy.c
> @@ -3345,21 +3345,21 @@ void rtl92d_phy_config_macphymode_info(struct ieee80211_hw *hw)
>   	switch (rtlhal->macphymode) {
>   	case DUALMAC_SINGLEPHY:
>   		rtlphy->rf_type = RF_2T2R;
> -		rtlhal->version |= CHIP_92D_SINGLEPHY;
> +		rtlhal->version |= RF_TYPE_2T2R;
>   		rtlhal->bandset = BAND_ON_BOTH;
>   		rtlhal->current_bandtype = BAND_ON_2_4G;
>   		break;
>
>   	case SINGLEMAC_SINGLEPHY:
>   		rtlphy->rf_type = RF_2T2R;
> -		rtlhal->version |= CHIP_92D_SINGLEPHY;
> +		rtlhal->version |= RF_TYPE_2T2R;
>   		rtlhal->bandset = BAND_ON_BOTH;
>   		rtlhal->current_bandtype = BAND_ON_2_4G;
>   		break;
>
>   	case DUALMAC_DUALPHY:
>   		rtlphy->rf_type = RF_1T1R;
> -		rtlhal->version &= (~CHIP_92D_SINGLEPHY);
> +		rtlhal->version &= RF_TYPE_1T1R;
>   		/* Now we let MAC0 run on 5G band. */
>   		if (rtlhal->interfaceindex == 0) {
>   			rtlhal->bandset = BAND_ON_5G;
>



  reply	other threads:[~2012-07-13 16:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13 14:35 [PATCH] rtlwifi: rtl8192de: Fix phy-based version calculation Forest Bond
2012-07-13 16:09 ` Larry Finger [this message]
2012-07-13 16:26   ` [PATCH resubmit] " 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=5000484E.9070700@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=forest@alittletooquiet.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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.