From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: Christian Lamparter <chunkeey@googlemail.com>,
linux-wireless@vger.kernel.org
Subject: Re: carl9170 1.0.9
Date: Sun, 23 May 2010 01:30:16 -0400 [thread overview]
Message-ID: <4BF8BD68.9030006@dlasys.net> (raw)
In-Reply-To: <201005230334.29866.chunkeey@googlemail.com>
On 05/22/2010 09:34 PM, Christian Lamparter wrote:
>> I beleive the timer_init() routine in carlfw/src/timer.c can not be
>> called for more than one timer. Any subsequent call will clear the
>> interrupt and mode bits for the previous timer.
>>
> there's more than that.
> Take a look at the (timer<< 2) and so forth...
>
The control and interrupt registers are bitmasks.
When you set the bit for the current timer you are clearing all the
others.
> based on observation: Some timers(1-4) are *driven* by the cpu clock.
> Which is of course determined by the operation mode and phy band.
> As you know there are 7 (1 + 2 * 3) possible AHB/CPU clock settings:
> * 40MHz (refclock)
> * 20MHz (PSM, 5GHz)& 22MHz (PSM, 2.4GHz)
> * 40MHz (11an, 5GHz, HT20)& 44Mhz (11bgn, 2.4GHz, HT20)
> * 80MHz (11an, 5GHz, HT40)& 88MHz (11bgn, 2.4GHz, HT40)
>
Thanks I have been working alot more with the timers today.
TSF follows the docs and is 1us.
My docs say that CCR is 25ns and only 16 bit.
But your code and that of the original ar9710-fw has it as 2 16 bit
registers making 32bits.
I have verified that and verified that it is pretty close to 25ns.
in my system.
But the remainder of the timers seem to be much much slower. My dos
do not specify that they are tied to anything specific.
I tripped over the AHB/CPU clock in the code. I need to look much
more thoroughly at that, and I am going to need to work out exactly how
it effects the other timers. I need the fastest timer I can get for my
application.
Thanks alot.
i will pull 1.0.9.1 shortly
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.587.7774 dhlii@dlasys.net http://www.dlasys.net
Over 25 years' experience in platforms, languages, and technologies too numerous to list.
"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein
next prev parent reply other threads:[~2010-05-23 5:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-01 10:19 ar9170-fw II David H. Lynch Jr.
2010-05-01 17:19 ` Christian Lamparter
2010-05-01 18:23 ` David H. Lynch Jr.
2010-05-01 20:45 ` Christian Lamparter
2010-05-02 7:47 ` Benoit Papillault
2010-05-02 11:14 ` David H. Lynch Jr.
2010-05-02 12:52 ` Christian Lamparter
2010-05-02 13:47 ` David H. Lynch Jr.
2010-05-05 18:41 ` carl9170 1.0.5.1 David H. Lynch Jr.
2010-05-05 19:59 ` 2.6.34-rc6 pci bridge problems Christian Lamparter
2010-05-06 15:09 ` Bjorn Helgaas
2010-05-07 15:46 ` Bjorn Helgaas
2010-05-07 18:44 ` Christian Lamparter
2010-05-06 0:11 ` carl9170 1.0.5.1 Luis R. Rodriguez
2010-05-11 22:02 ` ar9170-fw II David H. Lynch Jr.
2010-05-11 23:27 ` Christian Lamparter
2010-05-21 7:50 ` carl9170 1.0.6 David H. Lynch Jr.
2010-05-21 21:35 ` carl9170 1.0.6 carl9170_tx_superdesc David H. Lynch Jr.
2010-05-21 22:55 ` Christian Lamparter
2010-05-22 1:09 ` David H. Lynch Jr.
2010-05-22 19:13 ` carl9170 1.0.9 David H. Lynch Jr.
2010-05-23 1:34 ` Christian Lamparter
2010-05-23 5:30 ` David H. Lynch Jr. [this message]
2010-05-23 6:30 ` carl9170 1.0.9.1 David H. Lynch Jr.
2010-05-03 21:39 ` ar9170-fw II Luis R. Rodriguez
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=4BF8BD68.9030006@dlasys.net \
--to=dhlii@dlasys.net \
--cc=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.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.