From: Michael Buesch <mb@bu3sch.de>
To: bcm43xx-dev@lists.berlios.de
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 1/5] b43: N-PHY: implement b43_nphy_stay_carrier_search and it's calls
Date: Wed, 6 Jan 2010 16:50:50 +0100 [thread overview]
Message-ID: <201001061650.52062.mb@bu3sch.de> (raw)
In-Reply-To: <op.u54a5ufy9lhzdc@linux-g0th.site>
On Wednesday 06 January 2010 16:40:32 Rafał Miłecki wrote:
> b43: N-PHY: implement b43_nphy_stay_carrier_search and it's calls
Hm, The phrase "stay carrier earch" doesn't make a lot of sense to me.
Is "stray carrier search" or something like that meant?
Not that I care much, but I'm just wondering if this is just a typo.
> +static void b43_nphy_write_clip_detection(struct b43_wldev *dev, u16 *vals)
We know that these values are the clip thresholds, so use a better variable name, please.
> +{
> + b43_phy_write(dev, B43_NPHY_C1_CLIP1THRES, vals[0]);
> + b43_phy_write(dev, B43_NPHY_C2_CLIP1THRES, vals[1]);
> +}
> +
> +static void b43_nphy_read_clip_detection(struct b43_wldev *dev, u16 *vals)
> +{
> + vals[0] = b43_phy_read(dev, B43_NPHY_C1_CLIP1THRES);
> + vals[1] = b43_phy_read(dev, B43_NPHY_C2_CLIP1THRES);
> +}
> +
> +static u16 b43_nphy_classifier(struct b43_wldev *dev, u16 mask, u16 val)
> +{
> + u16 tmp;
> + bool suspended = false;
> +
> + if (dev->dev->id.revision == 16 && dev->mac_suspended == 0) {
Do not check for mac_suspended==0 here. b43_mac_suspended does this internally.
> + b43_mac_suspend(dev);
> + suspended = true;
> + }
> +
> + tmp = b43_phy_read(dev, B43_NPHY_CLASSCTL);
> + tmp &= (B43_NPHY_CLASSCTL_CCKEN | B43_NPHY_CLASSCTL_OFDMEN |
> + B43_NPHY_CLASSCTL_WAITEDEN);
> + tmp &= ~mask;
> + tmp |= (val & mask);
> + b43_phy_maskset(dev, B43_NPHY_CLASSCTL, 0xFFF8, tmp);
> +
> + if (suspended)
> + b43_mac_enable(dev);
> +
> + return tmp;
> +}
> +
> +static void b43_nphy_stay_carrier_search(struct b43_wldev *dev, bool enable)
> +{
> + struct b43_phy *phy = &dev->phy;
> + struct b43_phy_n *nphy = phy->n;
> +
> + if (enable) {
> + u16 clip[] = { 0xFFFF, 0xFFFF };
> + if (nphy->deaf_count++ == 0) {
> + nphy->classifier_state = b43_nphy_classifier(dev, 0, 0);
> + b43_nphy_classifier(dev, 0x7, 0);
> + b43_nphy_read_clip_detection(dev, nphy->clip_state);
> + b43_nphy_write_clip_detection(dev, clip);
> + }
> + b43_nphy_reset_cca(dev);
> + } else {
> + if (--nphy->deaf_count != 0) {
If this test logic correct? The following would make more sense to me:
if (--nphy->deaf_count == 0) {
> + b43_nphy_classifier(dev, 0x7, nphy->classifier_state);
> + b43_nphy_write_clip_detection(dev, nphy->clip_state);
> + }
> + }
> +}
> +
> enum b43_nphy_rf_sequence {
> B43_RFSEQ_RX2TX,
> B43_RFSEQ_TX2RX,
> diff --git a/drivers/net/wireless/b43/phy_n.h b/drivers/net/wireless/b43/phy_n.h
> index e5e402a..6ab07fc 100644
> --- a/drivers/net/wireless/b43/phy_n.h
> +++ b/drivers/net/wireless/b43/phy_n.h
> @@ -932,6 +932,9 @@ struct b43_phy_n {
> u32 deaf_count;
> bool mute;
>
> + u16 classifier_state;
> + u16 clip_state[2];
> +
> u8 iqcal_chanspec_2G;
> u8 rssical_chanspec_2G;
>
--
Greetings, Michael.
next prev parent reply other threads:[~2010-01-06 15:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 15:40 [PATCH 1/5] b43: N-PHY: implement b43_nphy_stay_carrier_search and it's calls Rafał Miłecki
2010-01-06 15:46 ` Rafał Miłecki
2010-01-06 15:50 ` Michael Buesch [this message]
2010-01-06 16:36 ` Larry Finger
2010-01-06 20:11 ` Rafał Miłecki
2010-01-06 20:54 ` [PATCH 1/5] b43: N-PHY: implement b43_nphy_stay_in_carrier_search and it's calls (V2) Rafał Miłecki
2010-01-06 22:35 ` Gábor Stefanik
2010-01-06 22:36 ` Gábor Stefanik
2010-01-06 22:45 ` Rafał Miłecki
2010-01-06 22:49 ` Gábor Stefanik
2010-01-06 22:59 ` Larry Finger
2010-01-06 23:12 ` Rafał Miłecki
2010-01-06 23:32 ` Gábor Stefanik
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=201001061650.52062.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).