From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <balbi@ti.com>
Cc: linux-usb@vger.kernel.org, linux-omap@vger.kernel.org
Subject: [PATCH 0/8] Allow multiple MUSB glue layers to be built in
Date: Mon, 24 Nov 2014 11:04:58 -0800 [thread overview]
Message-ID: <1416855906-13931-1-git-send-email-tony@atomide.com> (raw)
Hi all,
I noticed MUSB did not work for me as loadable modules and it was
because of the iffdeffery that breaks things with multiple glue
layers enabled as loadable modules.
I've set up function pointers for the PIO functions that now allow
building in multiple glue layers as modules or built-in.
Note that this series still does not sort out the DMA related issues,
I have a series in works for that too. But that will take some more
debugging.
So far this has been tested to work on omap3, am335x and tusb6010.
Regards,
Tony
Tony Lindgren (8):
usb: musb: Add function pointers for IO access functions
usb: musb: Populate new IO functions for tusb6010
usb: musb: Populate new IO functions for blackfin
usb: musb: Change to use new IO access
usb: musb: Change end point selection to use new IO access
usb: musb: Pass fifo_mode in platform data
usb: musb: Allow multiple glue layers to be built in
usb: musb: Use IS_ENABLED for tusb6010
drivers/usb/musb/Kconfig | 5 +-
drivers/usb/musb/am35x.c | 4 +-
drivers/usb/musb/blackfin.c | 48 ++++++++++-
drivers/usb/musb/da8xx.c | 2 +
drivers/usb/musb/jz4740.c | 2 +
drivers/usb/musb/musb_core.c | 199 ++++++++++++++++++++++++++++++++++++-------
drivers/usb/musb/musb_core.h | 86 ++++++++++---------
drivers/usb/musb/musb_dsps.c | 1 +
drivers/usb/musb/musb_io.h | 106 ++++++-----------------
drivers/usb/musb/musb_regs.h | 26 ------
drivers/usb/musb/musbhsdma.c | 7 +-
drivers/usb/musb/tusb6010.c | 58 ++++++++++++-
drivers/usb/musb/ux500.c | 2 +
drivers/usb/musb/ux500_dma.c | 4 +-
14 files changed, 356 insertions(+), 194 deletions(-)
--
2.1.3
next reply other threads:[~2014-11-24 19:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 19:04 Tony Lindgren [this message]
2014-11-24 19:05 ` [PATCH 2/8] usb: musb: Populate new IO functions for tusb6010 Tony Lindgren
2014-11-24 19:05 ` [PATCH 3/8] usb: musb: Populate new IO functions for blackfin Tony Lindgren
[not found] ` <1416855906-13931-1-git-send-email-tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2014-11-24 19:04 ` [PATCH 1/8] usb: musb: Add function pointers for IO access functions Tony Lindgren
2014-11-24 19:05 ` [PATCH 4/8] usb: musb: Change to use new IO access Tony Lindgren
2014-11-24 19:12 ` Felipe Balbi
2014-11-24 19:26 ` Tony Lindgren
[not found] ` <1416855906-13931-5-git-send-email-tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2014-11-25 9:46 ` Linus Walleij
2014-11-24 19:05 ` [PATCH 5/8] usb: musb: Change end point selection " Tony Lindgren
2014-11-24 23:38 ` Apelete Seketeli
2014-11-24 23:52 ` Tony Lindgren
2014-11-25 15:02 ` Lars-Peter Clausen
2014-11-28 13:50 ` Linus Walleij
2014-11-24 19:05 ` [PATCH 6/8] usb: musb: Pass fifo_mode in platform data Tony Lindgren
2014-11-24 23:40 ` Apelete Seketeli
2014-11-28 13:40 ` Linus Walleij
2014-11-24 19:05 ` [PATCH 7/8] usb: musb: Allow multiple glue layers to be built in Tony Lindgren
2014-11-24 19:05 ` [PATCH 8/8] usb: musb: Use IS_ENABLED for tusb6010 Tony Lindgren
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=1416855906-13931-1-git-send-email-tony@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@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).