From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
bcm43xx-dev@lists.berlios.de
Subject: Re: [RFC][PATCH] b43: LP-PHY: always adjust gain table on channel switch
Date: Fri, 05 Feb 2010 12:09:55 -0600 [thread overview]
Message-ID: <4B6C5EF3.5060006@lwfinger.net> (raw)
In-Reply-To: <69e28c911002050841x20053c6jbe768c19e983ef50@mail.gmail.com>
On 02/05/2010 10:41 AM, Gábor Stefanik wrote:
> On Fri, Feb 5, 2010 at 4:24 AM, Larry Finger <Larry.Finger@lwfinger.net> wrote:
>> On 02/04/2010 02:57 PM, Rafał Miłecki wrote:
>>> ---
>>> Gábor: I think you missed specs here. Could you check whole routine just for
>>> sure, please? I don't understand whole radio and chanspec magic yet.
>>> ---
>>> drivers/net/wireless/b43/phy_lp.c | 2 +-
>>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/drivers/net/wireless/b43/phy_lp.c b/drivers/net/wireless/b43/phy_lp.c
>>> index 185219e..61009ee 100644
>>> --- a/drivers/net/wireless/b43/phy_lp.c
>>> +++ b/drivers/net/wireless/b43/phy_lp.c
>>> @@ -2655,8 +2655,8 @@ static int b43_lpphy_op_switch_channel(struct b43_wldev *dev,
>>> if (err)
>>> return err;
>>> lpphy_set_analog_filter(dev, new_channel);
>>> - lpphy_adjust_gain_table(dev, channel2freq_lp(new_channel));
>>> }
>>> + lpphy_adjust_gain_table(dev, channel2freq_lp(new_channel));
>>>
>>> lpphy->channel = new_channel;
>>> b43_write16(dev, B43_MMIO_CHANNEL, new_channel);
>>
>> Both the lpphy_set_analog_filter() and lpphy_adjust_gain_table() calls should be
>> outside the if statement. I changed the spec a little. It used to test "radio
>> enabled", but I have found that is always true for our driver.
>>
>> Larry
>>
>>
>
> Isn't set_analog_filter() rev0/1-specific?
It was in the 4.174.64.19 driver that I RE'd when you wrote the LP PHY code.
That as changed in 5.10.56.46, which I am now doing. It will take me a while to
complete the new routine "LP PHY TX Filter Init" and a routine that it calls.
Certainly, there is no hurry that these changes be made. Whenever you or Rafał
have time. There is no guarantee that these changes will have any effect on the
LP PHY operations. Hitting a moving target is not easy.
Larry
next prev parent reply other threads:[~2010-02-05 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 20:57 [RFC][PATCH] b43: LP-PHY: always adjust gain table on channel switch Rafał Miłecki
2010-02-05 3:24 ` Larry Finger
2010-02-05 16:27 ` Gábor Stefanik
2010-02-06 0:06 ` Larry Finger
2010-02-06 19:24 ` Gábor Stefanik
2010-02-05 16:41 ` Gábor Stefanik
2010-02-05 18:09 ` Larry Finger [this message]
2010-02-05 18:46 ` Gábor Stefanik
2010-02-05 19:19 ` Larry Finger
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=4B6C5EF3.5060006@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netrolller.3d@gmail.com \
--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).