linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Kalle Valo <kvalo@qca.qualcomm.com>
Cc: Wu Fengguang <fengguang.wu@intel.com>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] rtlwifi: rtl8192ee: simplify coding
Date: Wed, 18 May 2016 07:02:49 -0500	[thread overview]
Message-ID: <573C59E9.8090902@lwfinger.net> (raw)
In-Reply-To: <1463532238-13135-1-git-send-email-xypron.glpk@gmx.de>

On 05/17/2016 07:43 PM, Heinrich Schuchardt wrote:
> Simplify _rtl92ee_phy_path_adda_on.
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> ---
>   drivers/net/wireless/realtek/rtlwifi/rtl8192ee/phy.c | 13 ++-----------
>   1 file changed, 2 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/net/wireless/realtek/rtlwifi/rtl8192ee/phy.c b/drivers/net/wireless/realtek/rtlwifi/rtl8192ee/phy.c
> index 018340a..c2bf8d1 100644
> --- a/drivers/net/wireless/realtek/rtlwifi/rtl8192ee/phy.c
> +++ b/drivers/net/wireless/realtek/rtlwifi/rtl8192ee/phy.c
> @@ -2414,19 +2414,10 @@ static void _rtl92ee_phy_reload_mac_registers(struct ieee80211_hw *hw,
>   static void _rtl92ee_phy_path_adda_on(struct ieee80211_hw *hw, u32 *addareg,
>   				      bool is_patha_on, bool is2t)
>   {
> -	u32 pathon;
>   	u32 i;
>
> -	pathon = is_patha_on ? 0x0fc01616 : 0x0fc01616;
> -	if (!is2t) {
> -		pathon = 0x0fc01616;
> -		rtl_set_bbreg(hw, addareg[0], MASKDWORD, 0x0fc01616);
> -	} else {
> -		rtl_set_bbreg(hw, addareg[0], MASKDWORD, pathon);
> -	}
> -
> -	for (i = 1; i < IQK_ADDA_REG_NUM; i++)
> -		rtl_set_bbreg(hw, addareg[i], MASKDWORD, pathon);
> +	for (i = 0; i < IQK_ADDA_REG_NUM; i++)
> +		rtl_set_bbreg(hw, addareg[i], MASKDWORD, 0x0fc01616);
>   }
>
>   static void _rtl92ee_phy_mac_setting_calibration(struct ieee80211_hw *hw,

Initially the thought was that addareg[0] would need to be set differently for 
devices with 2 TX paths. For that reason, this routine was coded as shown. As 
that assumption is no longer valid, this change should be made.

Acked-by: Larry Finger <Larry.Finger@lwfinger.net>


  reply	other threads:[~2016-05-18 12:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18  0:43 [PATCH 1/1] rtlwifi: rtl8192ee: simplify coding Heinrich Schuchardt
2016-05-18 12:02 ` Larry Finger [this message]
2016-06-14 14:23 ` [1/1] " Kalle Valo

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=573C59E9.8090902@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=fengguang.wu@intel.com \
    --cc=kvalo@qca.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=xypron.glpk@gmx.de \
    /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).