Linux wireless drivers development
 help / color / mirror / Atom feed
From: Luciano Coelho <coelho@ti.com>
To: coelho@ti.com
Cc: linux-wireless@vger.kernel.org
Subject: [PATCH 0/8] wl12xx: forward ported Balbi's bus driver refactor
Date: Thu,  6 Oct 2011 22:10:51 +0300	[thread overview]
Message-ID: <1317928259-26437-1-git-send-email-coelho@ti.com> (raw)

Hi,

Felipe sent this series of patches a long time ago with very good
suggestion on how to avoid the duplicate code we have in the sdio and
spi drivers.

With this, we create a platform device that is handled by a platform
driver.  The bus-specific module, creates a platform device and the
core module implements the driver that supports both platform devices
(namely "wl12xx-sdio" and "wl12xx-spi").

I didn't apply this earlier because I had concerns about the change in
the platform data, but now I'm convinced it's not a real problem.  It
may affect compat-wireless, but it's easy to solve.

I have now forward-ported the patches, fixed some bugs, removed some
style changes and moved some other things around.  For the changes I
made, see the commit message of each patch.  Some changes are not in
the commit message, but are explained in the patch emails, after the
Signed-off-by area.

I'm keeping Felipe as the author, since most of the work is his.  I
have just tested and fixed it up.

Cheers,
Luca.

Felipe Balbi (8):
  wl12xx: add an sdio glue struct to keep wl and device side-by-side
  wl12xx: add an spi glue struct to keep wl and device side-by-side
  wl12xx: add a platform device to the sdio module
  wl12xx: add a platform device to the spi module
  wl12xx: add platform driver to the core module
  wl12xx: move common init code from bus modules to main
  wl12xx: mark some symbols static
  wl12xx: drop unneeded plat_dev

 drivers/net/wireless/wl12xx/io.c                   |   11 +-
 drivers/net/wireless/wl12xx/io.h                   |   23 +--
 drivers/net/wireless/wl12xx/main.c                 |  271 +++++++++++++-------
 drivers/net/wireless/wl12xx/sdio.c                 |  217 +++++++----------
 drivers/net/wireless/wl12xx/spi.c                  |  194 ++++++---------
 drivers/net/wireless/wl12xx/wl12xx.h               |   18 +-
 drivers/net/wireless/wl12xx/wl12xx_platform_data.c |    4 +-
 include/linux/wl12xx.h                             |    5 +-
 8 files changed, 370 insertions(+), 373 deletions(-)


             reply	other threads:[~2011-10-06 19:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06 19:10 Luciano Coelho [this message]
2011-10-06 19:10 ` [PATCH 1/8] wl12xx: add an sdio glue struct to keep wl and device side-by-side Luciano Coelho
2011-10-06 19:10 ` [PATCH 2/8] wl12xx: add an spi " Luciano Coelho
2011-10-06 19:10 ` [PATCH 3/8] wl12xx: add a platform device to the sdio module Luciano Coelho
2011-10-06 19:10 ` [PATCH 4/8] wl12xx: add a platform device to the spi module Luciano Coelho
2011-10-06 19:10 ` [PATCH 5/8] wl12xx: add platform driver to the core module Luciano Coelho
2011-10-06 19:10 ` [PATCH 6/8] wl12xx: move common init code from bus modules to main Luciano Coelho
2011-10-06 19:10 ` [PATCH 7/8] wl12xx: mark some symbols static Luciano Coelho
2011-10-06 19:10 ` [PATCH 8/8] wl12xx: drop unneeded plat_dev Luciano Coelho
2011-10-11 13:05 ` [PATCH 0/8] wl12xx: forward ported Balbi's bus driver refactor Luciano Coelho

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=1317928259-26437-1-git-send-email-coelho@ti.com \
    --to=coelho@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