diff options
author | Arnd Bergmann <arnd@arndb.de> | 2013-04-25 19:29:04 +0200 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2013-04-25 10:58:00 -0700 |
commit | 8097804eab55d2dcfadfc821bceeb0faad978ab3 (patch) | |
tree | 18c95d6f486749a23d905442802a61e2f28830d4 /lib/ts_fsm.c | |
parent | c3c683ead3c53c0eb67b72c54e130baf45ac25d2 (diff) | |
download | blackbird-op-linux-8097804eab55d2dcfadfc821bceeb0faad978ab3.tar.gz blackbird-op-linux-8097804eab55d2dcfadfc821bceeb0faad978ab3.zip |
USB: OHCI: avoid conflicting platform drivers
Like the EHCI driver, OHCI supports a large number of different platform
glue drivers by directly including them, which causes problems with
conflicting macro definitions in some cases. As more ARM architecture
specific back-ends are required to coexist in a single build, we should
split those out into separate drivers. Unfortunately, the infrastructure
for that is still under development, so to give us more time, this uses
a separate *_PLATFORM_DRIVER macro for each ARM specific OHCI backend,
just like we already do on PowerPC and some of the other ARM platforms.
In linux-3.10, only the SPEAr and CNS3xxx back-ends would actually conflict
without this patch, but over time we would get more of them, so this
is a way to avoid having to patch the driver every time it breaks. We
should still split out all back-ends into separate loadable modules,
but that work is only needed to improve code size and cleanliness after
this patch, not for correctness.
While we're here, this fixes the incorrectly sorted error path
for the OMAP1 and OMAP3 backends to ensure we always unregister
the exact set of drivers that were registered before erroring out.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Acked-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'lib/ts_fsm.c')
0 files changed, 0 insertions, 0 deletions