From: Alex Hacker <hacker@epn.ru>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AR9380 - Transmit power control per packet
Date: Mon, 11 Jul 2011 22:27:13 +0600 [thread overview]
Message-ID: <20110711162713.GA2964@infinet.ru> (raw)
In-Reply-To: <CAD2nsn1AgTZVVF7W5-iVFOT6nF-w0RFxkvNRJzhnQjyU5Pr6Og@mail.gmail.com>
Yes, the EEPROM power calibration is implemented (oh excuse me, retyped from ath9k :).
Any way power detector calibration can not be a reason, so plain (not per packet) power
control is works as expected.
Best regards,
Alex.
On Mon, Jul 11, 2011 at 08:51:48PM +0530, Mohammed Shafi wrote:
> On Mon, Jul 11, 2011 at 8:43 PM, Alex Hacker <hacker@epn.ru> wrote:
> > On Mon, Jul 11, 2011 at 10:39:46PM +0800, Adrian Chadd wrote:
> >> Have you just manually tried setting the relevant register using the
> >> debug register read/write setup?
> >>
> > The TPC code is written aproximately 2 years ago in our propiertary AR5416/AR92xx driver
> > which I currently adopt for AR9300. For AR5416/AR92xx chips it works fine.
>
> I think this module has to be taken into acoount ar9003_eeprom.c ?
>
> static int ar9003_hw_power_control_override(struct ath_hw *ah,
> int frequency,
> int *correction,
> int *voltage, int *temperature)
>
>
>
> >
> >> Or when you set bit 6 in 0x993c, bit 6 doesn't stay set?
> >
> > Yes, exactly the following are happens:
> > ?REG_WRITE(0X993c,0x7f);
> > ?REG_READ(0X993c) -> 0x00367044;
> > ?REG_WRITE(0X993c,<somethin>);
> > ?REG_READ(0X993c) -> 0x0000007f;
> >
> >> adrian
> > Best regards,
> > Alex.
> > _______________________________________________
> > ath9k-devel mailing list
> > ath9k-devel at lists.ath9k.org
> > https://lists.ath9k.org/mailman/listinfo/ath9k-devel
> >
>
>
>
> --
> shafi
next prev parent reply other threads:[~2011-07-11 16:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 8:18 [ath9k-devel] AR9380 - Transmit power control per packet Robert Budde
2011-07-08 9:24 ` Robert Budde
2011-07-08 10:49 ` Mohammed Shafi
2011-07-08 11:27 ` Alex Hacker
2011-07-08 14:19 ` Alex Hacker
2011-07-09 0:21 ` Adrian Chadd
2011-07-11 10:48 ` Aleksey Shevkov
2011-07-11 14:39 ` Adrian Chadd
2011-07-11 15:13 ` Alex Hacker
2011-07-11 15:21 ` Mohammed Shafi
2011-07-11 15:23 ` Adrian Chadd
2011-07-11 16:37 ` Alex Hacker
2011-07-11 16:27 ` Alex Hacker [this message]
2011-07-12 7:03 ` Alex Hacker
2011-07-12 7:26 ` Adrian Chadd
2011-07-12 7:33 ` Robert Budde
2011-07-12 7:39 ` Mohammed Shafi
2011-07-11 15:11 ` Mohammed Shafi
2011-07-08 11:59 ` Mohammed Shafi
2011-07-08 12:57 ` Robert Budde
2011-07-08 13:06 ` Mohammed Shafi
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=20110711162713.GA2964@infinet.ru \
--to=hacker@epn.ru \
--cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.