From: Oleksij Rempel <linux@rempel-privat.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AR9271 Clock rate
Date: Fri, 19 Dec 2014 14:25:14 +0100 [thread overview]
Message-ID: <5494273A.4090901@rempel-privat.de> (raw)
In-Reply-To: <CAMfcBUSEBf6839-A8tuvZ6J2J7ZfZSQ83=smxZuA47MtD_Sd=g@mail.gmail.com>
Am 19.12.2014 um 10:21 schrieb Adrian Nicolau:
> Hello,
>
> I am using a TL-WN722N for a Wi-Fi ToF project; the SOC is AR9271 and I
> obtained the ath9k_htc source code via backports version 3.17.1-1. For
> ToF measurements, the higher the clock rate of the SOC, the better, and
> I know that AR9271 has a 117 MHz one.
> Reading through the code, in file ath/ath9k/hw.c, function
> ath9k_hw_set_clockrate [1] there is no entry for AS_SREV_9271, leaving
> the clockrate to be 44MHz in the common structure and throughout execution.
> The 117MHz setting is done later in the code by writing to a registry [2].
>
> I am wondering why the writing to the registry is not reflected in the
> common structure as well.
>
> [1] https://github.com/torvalds/linux/blob/master/drivers/net/wireless/ath/ath9k/hw.c#L39
> [2] https://github.com/torvalds/linux/blob/master/drivers/net/wireless/ath/ath9k/hw.c#L864
Because you are writing to wrong offset.
REG_WRITE will do it to a memory region mapped to mac core for this SoC.
--
Regards,
Oleksij
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: OpenPGP digital signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20141219/af5237d3/attachment.pgp
next prev parent reply other threads:[~2014-12-19 13:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 9:21 [ath9k-devel] AR9271 Clock rate Adrian Nicolau
2014-12-19 13:25 ` Oleksij Rempel [this message]
2014-12-19 13:53 ` Adrian Nicolau
2014-12-19 15:10 ` Oleksij Rempel
2014-12-19 15:14 ` Oleksij Rempel
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=5494273A.4090901@rempel-privat.de \
--to=linux@rempel-privat.de \
--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.