Linux wireless drivers development
 help / color / mirror / Atom feed
From: Elvis Dowson <elvis.dowson@mac.com>
To: "David Lynch Jr." <dhlii@dlasys.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: WL1271
Date: Tue, 21 Dec 2010 23:39:54 +0400	[thread overview]
Message-ID: <A285AB50-982B-478D-A8A1-9153560175BD@mac.com> (raw)
In-Reply-To: <1292957433.20560.109.camel@t-dhlii>

Hi,

On Dec 21, 2010, at 10:50 PM, David Lynch Jr. wrote:

> 	I am essentially doing exactly the same thing as you are - but I am a
> few days behind you. I noted a post of yours about 10 days ago in
> linux-omap that you were having voltage/SDIO detection problems. I am
> having exactly that problem at this moment.  
> 	How did you work arround it ?
> 	The WL1271 is attached to MMC2 on my system. All the examples in the
> linux wireless tree are on SPI or MMC3. But I think I managed changing
> things correctly - except that the error reports are mmc1:
> 	Also the comments suggest that the WL1271 has its own internal voltage
> regulation. 
> 	That and a CY8CTMG-200 touch screen are the only major items I need
> working to polish off this project. 

If you could send me the schematics, I could comment on it.

There were a couple of hardware related problems that prevented the device from
booting up. 

Here are some of the key things to watch out for:

a. You need a slow clock (SYS 32K signal from the omap processor) to the wlan module

b. You need to ensure that you have a 26Mhz TXCO signal coming in for the fast clock.

This would be controlled by a fixed voltage regulator. The wlan module asserts a WL_CLK_REQ
signal high, which is a signal sent to the LDO to turn on the 26MHz TXCO.

c. You need to probe MMC2 CLK signals to ensure that a 24MHz signal is being generated at the 
output, when the MMC2 controller is initialized.

d. You need to update the mux settings to ensure that the MMC2 CMD, CLK, DAT 0 to DAT3, plus
GPIO pins for WLAN_EN and WLAN_IRQ are muxed correctly.

This should take care of it. 

The SDIO detection problems occured because the 26MHZ TXCO was not being turn on.

You should also be aware of the TI WL1271 power up sequence, which is 10ms pulse high, 64us low,
and then asserted high for atleast 64ms. This is taken care of in the driver code.

Also use the linux-2.6.37-rc6 kernel patch, and apply the patch to read the MAC address from the nvs file.

Also put the firmware and nvs file in /lib/firmware folder, and configure wpa_supplicant.conf to connect
to a secured access point.

Best regards,

Elvis

  reply	other threads:[~2010-12-21 19:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0826983CC0CB074798C42E77D8ACD07F01AE4A@pdtms1.pdt.com>
     [not found] ` <1292843841.13129.9.camel@chilepepper>
2010-12-20 17:12   ` WL1271 chip Brzezowski, Karen
2010-12-20 17:47     ` Arend Van Spriel
     [not found]       ` <0826983CC0CB074798C42E77D8ACD07F01AF50@pdtms1.pdt.com>
2010-12-20 19:58         ` Arend Van Spriel
2010-12-20 21:00     ` Elvis Dowson
2010-12-20 21:04     ` WL1271 David Lynch Jr.
2010-12-20 21:31       ` WL1271 Elvis Dowson
2010-12-21 18:50         ` WL1271 David Lynch Jr.
2010-12-21 19:39           ` Elvis Dowson [this message]
2010-12-20 22:07       ` WL1271 Bob Copeland

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=A285AB50-982B-478D-A8A1-9153560175BD@mac.com \
    --to=elvis.dowson@mac.com \
    --cc=dhlii@dlasys.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox