From: Daniel Golle <dgolle@allnet.de>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"users@rt2x00.serialmonkey.com" <users@rt2x00.serialmonkey.com>,
"gwingerde@gmail.com" <gwingerde@gmail.com>,
"heinold@inf.fu-berlin.de" <heinold@inf.fu-berlin.de>
Subject: Re: [PATCH v2] rt2x00: add MediaTek/RaLink Rt3352 WiSoC
Date: Tue, 28 Aug 2012 15:52:08 +0300 [thread overview]
Message-ID: <503CBEF8.7010505@allnet.de> (raw)
In-Reply-To: <20120828124214.GA8426@redhat.com>
Hi Stanislaw,
On 28/08/12 15:42, Stanislaw Gruszka wrote:
> Thanks. Could you also provide information what was the source
> (registers programming) you based when writing this patch?
The vendor-driver Allnet got for that board (which is not publicly available and
we can't release its source)
>> + if (rt2x00_rt(rt2x00dev, RT3352)) {
>> + rt2800_bbp_write(rt2x00dev, 27, 0x0);
>> + rt2800_bbp_write(rt2x00dev, 62, 0x26 + rt2x00dev->lna_gain);
>> + rt2800_bbp_write(rt2x00dev, 27, 0x20);
>> + rt2800_bbp_write(rt2x00dev, 62, 0x26 + rt2x00dev->lna_gain);
>
> Writes two times to the same registers are intended?
Yes, as this is how it is done in the vendor driver, to me it looks like
register 27 acts as a switch selecting the destination for the value written to
register 62 or something like that.
Thank you!
Daniel
next prev parent reply other threads:[~2012-08-28 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 23:53 [PATCH v1] rt2x00: add MediaTek/RaLink Rt3352 WiSoC Daniel Golle
2012-08-22 10:51 ` Stanislaw Gruszka
2012-08-24 15:25 ` [PATCH v2] " Daniel Golle
2012-08-28 12:42 ` Stanislaw Gruszka
2012-08-28 12:52 ` Daniel Golle [this message]
2012-09-07 18:54 ` John W. Linville
2012-09-09 11:24 ` Daniel Golle
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=503CBEF8.7010505@allnet.de \
--to=dgolle@allnet.de \
--cc=gwingerde@gmail.com \
--cc=heinold@inf.fu-berlin.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sgruszka@redhat.com \
--cc=users@rt2x00.serialmonkey.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).