linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel Krüger" <daniel.krueger@systec-electronic.com>
To: linux-wireless@vger.kernel.org, geryk@ti.com
Cc: Alexander.Stein@systec-electronic.com
Subject: Multiple instances of WL1271
Date: Tue, 23 Aug 2011 13:32:12 +0200	[thread overview]
Message-ID: <4E538FBC.5070801@systec-electronic.com> (raw)

Hello Gery,

we plan to solder up to 4 WL1271 chips on our board (It will be the 
ready-to-use chip from LSR).

After a short look into the driver source code from the vanilla Linux 
kernel, we saw that the driver is not fully capable to handle multiple 
instances.

One critical issue we found are the wl12xx_set_platform_data and 
wl12xx_get_platform_data function calls. They configure the IRQ for the 
WLAN chip.

I think every WL1271 should get a separate IRQ (i.e. interrupt capable 
GPIO line). Does anyone has an idea how to configure the IRQ 
independently for each WL1271 chip? Especially on a X86 platform where 
there is no board specific configuration like on an embedded ARM target.

Another issue: every chip needs a specific NVS file (which holds the MAC 
address plus some other chip-specific settings). Currently, there is 
only one NVS file in the whole system. But it should be very easy to add 
some kind of instance number to the NVS file name to have a separate 
file for each chip.

Are there any other known issues when there are multiple WL1271 chips in 
one system?

Any help is appreciated.

cu,
   Daniel

-- 
SYS TEC electronic GmbH
August-Bebel-Str. 29
D-07973 Greiz

Telefon  : +49 (0) 3661 6279 0
Fax      : +49 (0) 3661 6279 99
Email    : daniel.krueger@systec-electronic.com
Internet : http://www.systec-electronic.com

Managing Director   : Dipl.-Phys. Siegmar Schmidt
Commercial registry : Amtsgericht Jena, HRB 205563

                 reply	other threads:[~2011-08-23 11:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4E538FBC.5070801@systec-electronic.com \
    --to=daniel.krueger@systec-electronic.com \
    --cc=Alexander.Stein@systec-electronic.com \
    --cc=geryk@ti.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 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).