From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Antonio Quartulli <ordex@ritirata.org>
Cc: Gertjan van Wingerde <gwingerde@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
Ivo van Doorn <IvDoorn@gmail.com>,
linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com,
Luis Correia <luis.f.correia@gmail.com>
Subject: Re: [PATCH 6/9] rt2x00: Finish rt3070 support in rt2800 register initialization.
Date: Mon, 26 Apr 2010 13:12:37 +0200 [thread overview]
Message-ID: <201004261312.37432.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <201004261302.14682.helmut.schaa@googlemail.com>
Am Montag 26 April 2010 schrieb Helmut Schaa:
> Am Sonntag 11 April 2010 schrieb Gertjan van Wingerde:
> > rt2x00 had preliminary support for RT3070 based devices, but the support was
> > incomplete.
> > Update the RT3070 register initialization to be similar to the latest Ralink
> > vendor driver.
> >
> > With this patch my rt3070 based devices start showing a sign of life.
>
> Gertjan, this patch breaks rx on my 305x SoC device. See inline comments for
> more details.
Antonio, did that patch also break rx on your PCI device with rt2872?
If not I'm going to enable this code only on SOC devices.
Thanks,
Helmut
> [...]
>
> > @@ -1643,18 +1653,12 @@ int rt2800_init_rfcsr(struct rt2x00_dev *rt2x00dev)
> > {
> > u8 rfcsr;
> > u8 bbp;
> > + u32 reg;
> > + u16 eeprom;
> >
> > - if (rt2x00_is_usb(rt2x00dev) &&
> > - !rt2x00_rt_rev(rt2x00dev, RT3070, REV_RT3070E))
> > + if (!rt2x00_rt(rt2x00dev, RT3070))
> > return 0;
> >
> > - if (rt2x00_is_pci(rt2x00dev) || rt2x00_is_soc(rt2x00dev)) {
> > - if (!rt2x00_rf(rt2x00dev, RF3020) &&
> > - !rt2x00_rf(rt2x00dev, RF3021) &&
> > - !rt2x00_rf(rt2x00dev, RF3022))
> > - return 0;
> > - }
>
> Any reason why you've removed this part? The following code was executed on
> pci and soc devices when they had an 3020, 3021 or 3022 rf.
>
> > /*
> > * Init RF calibration.
> > */
> > @@ -1665,13 +1669,13 @@ int rt2800_init_rfcsr(struct rt2x00_dev *rt2x00dev)
> > rt2x00_set_field8(&rfcsr, RFCSR30_RF_CALIBRATION, 0);
> > rt2800_rfcsr_write(rt2x00dev, 30, rfcsr);
> >
> > - if (rt2x00_is_usb(rt2x00dev)) {
> > + if (rt2x00_rt(rt2x00dev, RT3070)) {
> > rt2800_rfcsr_write(rt2x00dev, 4, 0x40);
> > rt2800_rfcsr_write(rt2x00dev, 5, 0x03);
> > rt2800_rfcsr_write(rt2x00dev, 6, 0x02);
> > rt2800_rfcsr_write(rt2x00dev, 7, 0x70);
> > rt2800_rfcsr_write(rt2x00dev, 9, 0x0f);
> > - rt2800_rfcsr_write(rt2x00dev, 10, 0x71);
> > + rt2800_rfcsr_write(rt2x00dev, 10, 0x41);
> > rt2800_rfcsr_write(rt2x00dev, 11, 0x21);
> > rt2800_rfcsr_write(rt2x00dev, 12, 0x7b);
> > rt2800_rfcsr_write(rt2x00dev, 14, 0x90);
> > @@ -1684,48 +1688,25 @@ int rt2800_init_rfcsr(struct rt2x00_dev *rt2x00dev)
> > rt2800_rfcsr_write(rt2x00dev, 21, 0xdb);
> > rt2800_rfcsr_write(rt2x00dev, 24, 0x16);
> > rt2800_rfcsr_write(rt2x00dev, 25, 0x01);
> > - rt2800_rfcsr_write(rt2x00dev, 27, 0x03);
> > rt2800_rfcsr_write(rt2x00dev, 29, 0x1f);
> > - } else if (rt2x00_is_pci(rt2x00dev) || rt2x00_is_soc(rt2x00dev)) {
> > - rt2800_rfcsr_write(rt2x00dev, 0, 0x50);
> > - rt2800_rfcsr_write(rt2x00dev, 1, 0x01);
> > - rt2800_rfcsr_write(rt2x00dev, 2, 0xf7);
> > - rt2800_rfcsr_write(rt2x00dev, 3, 0x75);
> > - rt2800_rfcsr_write(rt2x00dev, 4, 0x40);
> > - rt2800_rfcsr_write(rt2x00dev, 5, 0x03);
> > - rt2800_rfcsr_write(rt2x00dev, 6, 0x02);
> > - rt2800_rfcsr_write(rt2x00dev, 7, 0x50);
> > - rt2800_rfcsr_write(rt2x00dev, 8, 0x39);
> > - rt2800_rfcsr_write(rt2x00dev, 9, 0x0f);
> > - rt2800_rfcsr_write(rt2x00dev, 10, 0x60);
> > - rt2800_rfcsr_write(rt2x00dev, 11, 0x21);
> > - rt2800_rfcsr_write(rt2x00dev, 12, 0x75);
> > - rt2800_rfcsr_write(rt2x00dev, 13, 0x75);
> > - rt2800_rfcsr_write(rt2x00dev, 14, 0x90);
> > - rt2800_rfcsr_write(rt2x00dev, 15, 0x58);
> > - rt2800_rfcsr_write(rt2x00dev, 16, 0xb3);
> > - rt2800_rfcsr_write(rt2x00dev, 17, 0x92);
> > - rt2800_rfcsr_write(rt2x00dev, 18, 0x2c);
> > - rt2800_rfcsr_write(rt2x00dev, 19, 0x02);
> > - rt2800_rfcsr_write(rt2x00dev, 20, 0xba);
> > - rt2800_rfcsr_write(rt2x00dev, 21, 0xdb);
> > - rt2800_rfcsr_write(rt2x00dev, 22, 0x00);
> > - rt2800_rfcsr_write(rt2x00dev, 23, 0x31);
> > - rt2800_rfcsr_write(rt2x00dev, 24, 0x08);
> > - rt2800_rfcsr_write(rt2x00dev, 25, 0x01);
> > - rt2800_rfcsr_write(rt2x00dev, 26, 0x25);
> > - rt2800_rfcsr_write(rt2x00dev, 27, 0x23);
> > - rt2800_rfcsr_write(rt2x00dev, 28, 0x13);
> > - rt2800_rfcsr_write(rt2x00dev, 29, 0x83);
>
> This part is actually needed for getting rx to work on the SoC devices.
>
> Should I post a patch that adds this code again and is only executed on SoC
> devices with rf3020, 3021 and 3022?
>
> Thanks,
> Helmut
>
next prev parent reply other threads:[~2010-04-26 11:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 12:31 [PATCH v2 0/9] rt2x00: Align with vendor driver and add support for rt3070/rt3071/rt3090/rt3390 Gertjan van Wingerde
2010-04-11 12:31 ` [PATCH 1/9] rt2x00: Let RF chipset decide the RF channel switch method to use in rt2800 Gertjan van Wingerde
2010-04-11 12:31 ` [PATCH 2/9] rt2x00: Update rt2800 register definitions towards latest definitions Gertjan van Wingerde
2010-04-11 12:31 ` [PATCH 3/9] rt2x00: Align RT chipset definitions with vendor driver Gertjan van Wingerde
2010-04-11 12:31 ` [PATCH 4/9] rt2x00: Refactor rt2800 version constants Gertjan van Wingerde
2010-04-11 16:55 ` Ivo van Doorn
2010-04-11 12:31 ` [PATCH 5/9] rt2x00: Align rt2800 register initialization with vendor driver Gertjan van Wingerde
2010-04-11 16:56 ` Ivo van Doorn
2010-04-11 12:31 ` [PATCH 6/9] rt2x00: Finish rt3070 support in rt2800 register initialization Gertjan van Wingerde
2010-04-11 16:56 ` Ivo van Doorn
2010-04-26 11:02 ` Helmut Schaa
2010-04-26 11:11 ` Helmut Schaa
2010-04-27 11:15 ` Antonio Quartulli
2010-04-28 12:47 ` [rt2x00-users] " Antonio Quartulli
2010-04-28 12:56 ` Helmut Schaa
2010-04-28 17:23 ` Antonio Quartulli
2010-04-30 12:20 ` Helmut Schaa
2010-04-26 11:12 ` Helmut Schaa [this message]
2010-04-26 19:52 ` Gertjan van Wingerde
2010-04-26 19:59 ` Helmut Schaa
2010-04-26 21:43 ` Gertjan van Wingerde
2010-04-11 12:31 ` [PATCH 7/9] rt2x00: Add rt3071 " Gertjan van Wingerde
2010-04-11 16:57 ` Ivo van Doorn
2010-04-11 12:31 ` [PATCH 8/9] rt2x00: Add rt3090 " Gertjan van Wingerde
2010-04-11 12:31 ` [PATCH 9/9] rt2x00: Add rt3390 " Gertjan van Wingerde
-- strict thread matches above, loose matches on Subject: below --
2010-04-08 21:50 [PATCH 0/9] rt2x00: Align with vendor driver and add support for rt3070/rt3071/rt3090/rt3390 Gertjan van Wingerde
2010-04-08 21:50 ` [PATCH 6/9] rt2x00: Finish rt3070 support in rt2800 register initialization Gertjan van Wingerde
2010-04-08 22:33 ` Ivo van Doorn
2010-04-10 20:52 ` Gertjan van Wingerde
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=201004261312.37432.helmut.schaa@googlemail.com \
--to=helmut.schaa@googlemail.com \
--cc=IvDoorn@gmail.com \
--cc=gwingerde@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=luis.f.correia@gmail.com \
--cc=ordex@ritirata.org \
--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).