From: Vasanthakumar Thiagarajan <vasanth@atheros.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: Vasanth Thiagarajan <Vasanth.Thiagarajan@Atheros.com>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 03/22] ath9k_hw: Introduce a bool for 25mhz clock and populate it
Date: Tue, 12 Apr 2011 19:30:36 +0530 [thread overview]
Message-ID: <20110412140035.GA15609@vasanth-laptop> (raw)
In-Reply-To: <4DA458A8.5030205@openwrt.org>
On Tue, Apr 12, 2011 at 07:20:32PM +0530, Felix Fietkau wrote:
> On 2011-04-12 3:17 PM, Vasanthakumar Thiagarajan wrote:
> > pll configuration will differ for 25mhz clock.
> >
> > Signed-off-by: Vasanthakumar Thiagarajan<vasanth@atheros.com>
> > ---
> > drivers/net/wireless/ath/ath9k/hw.c | 11 +++++++++++
> > drivers/net/wireless/ath/ath9k/hw.h | 2 ++
> > 2 files changed, 13 insertions(+), 0 deletions(-)
> >
> > diff --git a/drivers/net/wireless/ath/ath9k/hw.c b/drivers/net/wireless/ath/ath9k/hw.c
> > index d98b4c6..8b90b9c 100644
> > --- a/drivers/net/wireless/ath/ath9k/hw.c
> > +++ b/drivers/net/wireless/ath/ath9k/hw.c
> > @@ -481,6 +481,9 @@ static void ath9k_hw_attach_ops(struct ath_hw *ah)
> > /* Called for all hardware families */
> > static int __ath9k_hw_init(struct ath_hw *ah)
> > {
> > +#define AR9340_SOC_SEL_25M_40M 0xB80600B0
> > +#define AR9340_REF_CLK_40 (1<< 4) /* 0 - 25MHz 1 - 40 MHz */
> > +
> > struct ath_common *common = ath9k_hw_common(ah);
> > int r = 0;
> >
> > @@ -508,6 +511,14 @@ static int __ath9k_hw_init(struct ath_hw *ah)
> >
> > ath9k_hw_attach_ops(ah);
> >
> > + if (AR_SREV_9340(ah)) {
> > + if (*((volatile u32 *) AR9340_SOC_SEL_25M_40M)&
> > + AR9340_REF_CLK_40)
> > + ah->is_clk_25mhz = false;
> > + else
> > + ah->is_clk_25mhz = true;
> > + }
> > +
> > if (!ath9k_hw_setpower(ah, ATH9K_PM_AWAKE)) {
> > ath_err(common, "Couldn't wakeup chip\n");
> > return -EIO;
> I think this flag should be passed down from the arch code through
> platform data instead. Also, dereferencing volatile u32 pointers for
> reading registers is somewhat hackish, readl or ioread32 would be better.
Yeah, I was also not comfortable with this part of code. I'll fix
that. thanks for the comments.
Vasanth
next prev parent reply other threads:[~2011-04-12 14:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 13:17 [PATCH 03/22] ath9k_hw: Introduce a bool for 25mhz clock and populate it Vasanthakumar Thiagarajan
2011-04-12 13:17 ` [PATCH 04/22] ath9k_hw: Configure pll control register accordingly for AR9340 Vasanthakumar Thiagarajan
2011-04-12 13:17 ` [PATCH 06/22] ath9k_hw: Initialize mode registers from initvals.h " Vasanthakumar Thiagarajan
2011-04-12 13:17 ` [PATCH 07/22] ath9k_hw: Don't do ani initialization " Vasanthakumar Thiagarajan
2011-04-12 13:17 ` [PATCH 09/22] ath9k_hw: Read spur frequency information from eeprom " Vasanthakumar Thiagarajan
2011-04-12 13:17 ` [PATCH 10/22] ath9k_hw: Configure RF channel freqency " Vasanthakumar Thiagarajan
2011-04-12 13:17 ` [PATCH 11/22] ath9k_hw: Clean up rx/tx chain configuration before AGC/IQ cal Vasanthakumar Thiagarajan
2011-04-12 13:17 ` [PATCH 14/22] ath9k_hw: Skip internal regulator configuration for AR9340 Vasanthakumar Thiagarajan
2011-04-12 13:17 ` [PATCH 15/22] ath9k_hw: Configure tuning capacitance value for AR9340 as well Vasanthakumar Thiagarajan
2011-04-12 13:17 ` [PATCH 17/22] ath9k_hw: Configure chain switch table and attenuation control only for active chains Vasanthakumar Thiagarajan
2011-04-12 13:17 ` [PATCH 18/22] ath9k_hw: Read iq calibration data " Vasanthakumar Thiagarajan
2011-04-12 13:17 ` [PATCH 21/22] ath9k_hw: Disable INTR_HOST1_FATAL to avoid interrupt strom with ar9430 Vasanthakumar Thiagarajan
2011-04-12 13:17 ` [PATCH 22/22] ath9k_hw: Enable AR9340 support Vasanthakumar Thiagarajan
2011-04-12 13:50 ` [PATCH 03/22] ath9k_hw: Introduce a bool for 25mhz clock and populate it Felix Fietkau
2011-04-12 14:00 ` Vasanthakumar Thiagarajan [this message]
2011-04-12 14:33 ` Vasanthakumar Thiagarajan
2011-04-12 14:51 ` John W. Linville
2011-04-19 5:49 ` Vasanthakumar Thiagarajan
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=20110412140035.GA15609@vasanth-laptop \
--to=vasanth@atheros.com \
--cc=Vasanth.Thiagarajan@Atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=nbd@openwrt.org \
/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).