From: Florian Fainelli <florian@openwrt.org>
To: Samuel Ortiz <samuel@sortiz.org>
Cc: "Gábor Stefanik" <netrolller.3d@gmail.com>,
"Bob Copeland" <me@bobcopeland.com>,
linux-wireless@vger.kernel.org, pierre@ossman.eu,
kalle.valo@iki.fi, san@google.com
Subject: Re: [PATCH/RFC 0/7] wl12xx SDIO interface
Date: Thu, 11 Jun 2009 16:59:26 +0200 [thread overview]
Message-ID: <200906111659.29575.florian@openwrt.org> (raw)
In-Reply-To: <1244732120.2465.3.camel@sortiz-mobl>
Le Thursday 11 June 2009 16:55:20 Samuel Ortiz, vous avez écrit :
> On Thu, 2009-06-11 at 16:38 +0200, Gábor Stefanik wrote:
> > On Thu, Jun 11, 2009 at 4:02 AM, Bob Copeland<me@bobcopeland.com> wrote:
> > > Here's v2 of the SDIO interface for wl12xx, still with a FIXME or two.
> > >
> > > For my part, this is mainly a port of the Google/TI Android SDIO
> > > interface logic to the existing SPI driver. I have confirmed that
> > > the driver associates and sends some traffic.
> > >
> > > Pierre, hoping to get your perspective on the SDIO bits in patch 7,
> > > since I very likely don't know what I'm doing :) Especially regarding
> > > the platform code setup, in which the correct GPIOs have to be written
> > > to turn on the device before probe will work. For the SPI interface,
> > > we use spi_register_board_info() for a similar purpose, but I'm not
> > > sure if there is a standard way to do that for SDIO. This copies
> > > Google's platform driver for now.
> > >
> > > Conversion to readl/writel etc where appropriate is TODO.
> > >
> > > Bob Copeland (7):
> > > wl12xx: separate bus i/o code into io.c
> > > wl12xx: use wiphy_dev instead of wl->spi->dev
> > > wl12xx: introduce wl12xx_if_operations struct
> > > wl12xx: make wl12xx_set_partition bus agnostic
> > > wl12xx: move module probe methods into spi.c
> > > wl12xx: split spi interface into separate module
> > > wl12xx: add sdio support
> > >
> > > drivers/net/wireless/wl12xx/Kconfig | 24 +++-
> > > drivers/net/wireless/wl12xx/Makefile | 10 +-
> > > drivers/net/wireless/wl12xx/acx.c | 3 +-
> > > drivers/net/wireless/wl12xx/boot.c | 3 +-
> > > drivers/net/wireless/wl12xx/cmd.c | 15 +-
> > > drivers/net/wireless/wl12xx/event.c | 6 +-
> > > drivers/net/wireless/wl12xx/io.c | 181 +++++++++++++++++++++
> > > drivers/net/wireless/wl12xx/io.h | 62 +++++++
> > > drivers/net/wireless/wl12xx/main.c | 152 ++++--------------
> > > drivers/net/wireless/wl12xx/ps.c | 3 +-
> > > drivers/net/wireless/wl12xx/rx.c | 10 +-
> > > drivers/net/wireless/wl12xx/sdio.c | 250
> > > +++++++++++++++++++++++++++++ drivers/net/wireless/wl12xx/spi.c |
> > > 289 ++++++++++++++------------------- drivers/net/wireless/wl12xx/spi.h
> > > | 40 -----
> > > drivers/net/wireless/wl12xx/tx.c | 64 ++++----
> > > drivers/net/wireless/wl12xx/wl1251.c | 9 +-
> > > drivers/net/wireless/wl12xx/wl12xx.h | 14 ++-
> > > 17 files changed, 752 insertions(+), 383 deletions(-)
> > > create mode 100644 drivers/net/wireless/wl12xx/io.c
> > > create mode 100644 drivers/net/wireless/wl12xx/io.h
> > > create mode 100644 drivers/net/wireless/wl12xx/sdio.c
> >
> > Can we expect vlynq any time soon?
>
> I guess we need:
>
> 1) A linux vlynq driver for that, and last thing I saw [1], it wasnt
> really pretty/ready
That driver is perfectly functionnal on a TI AR7 and we have used it in
OpenWrt for months with the acx100/111 driver. What makes you think it is not
yet ready ? There was a couple of suggestions from a TI employee, which are
perfectly valid, but I have no hardware to implement what he is suggesting
(no daisy chaining ...).
> 2) A device that would have a wl12xx chip connected to the host through
> vlynq.
>
> Cheers,
> Samuel.
>
> [1] http://lkml.indiana.edu/hypermail/linux/kernel/0906.0/00155.html
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless"
> in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Best regards, Florian Fainelli
Email : florian@openwrt.org
http://openwrt.org
-------------------------------
next prev parent reply other threads:[~2009-06-11 14:59 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 2:02 [PATCH/RFC 0/7] wl12xx SDIO interface Bob Copeland
2009-06-11 2:02 ` [PATCH/RFC 1/7] wl12xx: separate bus i/o code into io.c Bob Copeland
2009-06-11 2:02 ` [PATCH/RFC 2/7] wl12xx: use wiphy_dev instead of wl->spi->dev Bob Copeland
2009-06-11 2:02 ` [PATCH/RFC 3/7] wl12xx: introduce wl12xx_if_operations struct Bob Copeland
2009-06-11 2:02 ` [PATCH/RFC 4/7] wl12xx: make wl12xx_set_partition bus agnostic Bob Copeland
2009-06-11 2:02 ` [PATCH/RFC 5/7] wl12xx: move module probe methods into spi.c Bob Copeland
2009-06-11 2:02 ` [PATCH/RFC 6/7] wl12xx: split spi interface into separate module Bob Copeland
2009-06-11 2:03 ` [PATCH/RFC 7/7] wl12xx: add sdio support Bob Copeland
2009-06-13 11:21 ` Pierre Ossman
2009-06-13 16:00 ` Kalle Valo
2009-06-13 19:41 ` Marcel Holtmann
2009-06-13 20:13 ` Kalle Valo
2009-06-13 20:24 ` Marcel Holtmann
2009-06-13 20:44 ` Kalle Valo
2009-06-13 20:09 ` Pierre Ossman
2009-06-13 20:57 ` Bob Copeland
2009-06-18 2:25 ` Bob Copeland
2009-06-19 19:24 ` Pierre Ossman
2009-06-19 20:31 ` Bob Copeland
2009-06-20 4:29 ` Kalle Valo
2009-06-21 18:38 ` Pierre Ossman
2009-06-22 0:05 ` Bob Copeland
2009-06-22 6:09 ` Pierre Ossman
2009-06-22 6:14 ` Pierre Ossman
2009-06-23 2:18 ` Bob Copeland
2009-07-15 7:12 ` Ohad Ben-Cohen
2009-07-15 12:08 ` Bob Copeland
2009-06-11 14:38 ` [PATCH/RFC 0/7] wl12xx SDIO interface Gábor Stefanik
2009-06-11 14:54 ` Florian Fainelli
2009-06-11 17:06 ` Bob Copeland
2009-06-11 14:55 ` Samuel Ortiz
2009-06-11 14:59 ` Florian Fainelli [this message]
2009-06-11 15:04 ` Gábor Stefanik
2009-06-11 15:08 ` Florian Fainelli
2009-06-11 15:03 ` Samuel Ortiz
2009-06-11 15:54 ` Kalle Valo
2009-06-11 17:08 ` Bob Copeland
2009-06-11 17:14 ` Kalle Valo
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=200906111659.29575.florian@openwrt.org \
--to=florian@openwrt.org \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=netrolller.3d@gmail.com \
--cc=pierre@ossman.eu \
--cc=samuel@sortiz.org \
--cc=san@google.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 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.