linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Michael Büsch" <m@bues.ch>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>,
	b43-dev@lists.infradead.org
Subject: Re: [PATCH 1/4] b43: HT-PHY: fix masks in radio ctl
Date: Sun, 17 Jul 2011 10:05:04 -0500	[thread overview]
Message-ID: <4E22FA20.3090503@lwfinger.net> (raw)
In-Reply-To: <20110717104359.72a27182@maggie>

On 07/17/2011 03:43 AM, Michael Büsch wrote:
> On Sun, 17 Jul 2011 10:30:31 +0200
> Rafał Miłecki<zajec5@gmail.com>  wrote:
>
>> Old masks were causing ugly, delayed lock ups.
>>
>> Signed-off-by: Rafał Miłecki<zajec5@gmail.com>
>> ---
>>   drivers/net/wireless/b43/phy_ht.c |   10 +++++-----
>>   1 files changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/net/wireless/b43/phy_ht.c b/drivers/net/wireless/b43/phy_ht.c
>> index 2982103..0cc293a 100644
>> --- a/drivers/net/wireless/b43/phy_ht.c
>> +++ b/drivers/net/wireless/b43/phy_ht.c
>> @@ -277,12 +277,12 @@ static void b43_phy_ht_op_software_rfkill(struct b43_wldev *dev,
>>   		b43err(dev->wl, "MAC not suspended\n");
>>
>>   	if (blocked) {
>> -		b43_phy_mask(dev, B43_PHY_HT_RF_CTL1, ~0);
>> +		b43_phy_mask(dev, B43_PHY_HT_RF_CTL1, 0);
>>   	} else {
>> -		b43_phy_mask(dev, B43_PHY_HT_RF_CTL1, ~0);
>> -		b43_phy_maskset(dev, B43_PHY_HT_RF_CTL1, ~0, 0x1);
>> -		b43_phy_mask(dev, B43_PHY_HT_RF_CTL1, ~0);
>> -		b43_phy_maskset(dev, B43_PHY_HT_RF_CTL1, ~0, 0x2);
>> +		b43_phy_mask(dev, B43_PHY_HT_RF_CTL1, 0);
>> +		b43_phy_maskset(dev, B43_PHY_HT_RF_CTL1, 0, 0x1);
>> +		b43_phy_mask(dev, B43_PHY_HT_RF_CTL1, 0);
>> +		b43_phy_maskset(dev, B43_PHY_HT_RF_CTL1, 0, 0x2);
>>
>>   		if (dev->phy.radio_ver == 0x2059)
>>   			b43_radio_2059_init(dev);
>
> Why are we using mask/maskset here at all, if the mask is zero?
> You could just use phy_write.
>
> (And mask() with ~0 should always ring a bell anyway, because it does
> nothing except for possible side effects of the register read/write).

All of the Broadcom mask and maskset routines are called with the complement of 
the mask. It has been a constant battle during the RE work to keep that straight.

Larry

  reply	other threads:[~2011-07-17 15:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-17  8:30 [PATCH 1/4] b43: HT-PHY: fix masks in radio ctl Rafał Miłecki
2011-07-17  8:30 ` [PATCH 2/4] b43: HT-PHY: switch to channel after enabling radio Rafał Miłecki
2011-07-17  8:30 ` [PATCH 3/4] b43: HT-PHY: find channel entry with regs data Rafał Miłecki
2011-07-17  8:30 ` [PATCH 4/4] b43: HT-PHY: fix typo in 0x2059 radio init Rafał Miłecki
2011-07-17  8:43 ` [PATCH 1/4] b43: HT-PHY: fix masks in radio ctl Michael Büsch
2011-07-17 15:05   ` Larry Finger [this message]
2011-07-17 16:42   ` Rafał Miłecki
2011-07-17 16:56   ` Rafał Miłecki
  -- strict thread matches above, loose matches on Subject: below --
2011-07-18  0:13 Rafał Miłecki

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=4E22FA20.3090503@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=m@bues.ch \
    --cc=zajec5@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;
as well as URLs for NNTP newsgroup(s).