From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] usb: ehci: more bus glues as separate modules
Date: Mon, 11 Feb 2013 18:45:19 +0000 [thread overview]
Message-ID: <51193C3F.6000908@codethink.co.uk> (raw)
In-Reply-To: <5117edda.860e440a.097c.3507@mx.google.com>
On 10/02/13 18:58, manjunath.goudar at linaro.org wrote:
> From: Manjunath Goudar<manjunath.goudar@linaro.org>
>
> Separate the SOC On-Chip host controller driver from ehci-hcd
> host code into its own driver module
>
> Manjunath Goudar (8):
> USB: EHCI: make ehci-spear a separate driver
> USB: EHCI: make ehci-atmel a separate driver
> USB: EHCI: make ehci-s5p a separate driver
> USB: EHCI: make ehci-mv a separate driver
> USB: EHCI: make ehci-vt8500 a separate driver
> USB: EHCI: make ehci-msm a separate driver
> USB: EHCI: make ehci-w90X900 a separate driver
> USB: EHCI: make ehci-orion a separate driver
>
> drivers/usb/host/Kconfig | 42 +++++++++++--
> drivers/usb/host/Makefile | 9 ++-
> drivers/usb/host/ehci-atmel.c | 77 ++++++++++++-----------
> drivers/usb/host/ehci-hcd.c | 52 +++-------------
> drivers/usb/host/ehci-msm.c | 85 +++++++++++--------------
> drivers/usb/host/ehci-mv.c | 80 +++++++++++-------------
> drivers/usb/host/ehci-orion.c | 91 +++++++++++++--------------
> drivers/usb/host/ehci-s5p.c | 69 ++++++++++++---------
> drivers/usb/host/ehci-spear.c | 131 ++++++++++++++++++++-------------------
> drivers/usb/host/ehci-vt8500.c | 73 ++++++++++------------
> drivers/usb/host/ehci-w90x900.c | 90 ++++++++++++---------------
> drivers/usb/host/ehci.h | 2 +-
> 12 files changed, 392 insertions(+), 409 deletions(-)
Having looked at this, we will end up with a number of modules,
each having very similar code in them.#
How about we add drivers/usb/host/ehci-platform.c for all
the platform based drivers.
I think it is possible to remove all the specific names, as
we certainly don't need the driver advertising itself for each
system. Also, does anyone rely on the name field in the HC info,
or can it just be "Platform EHCI" ?
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
prev parent reply other threads:[~2013-02-11 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-10 18:58 [PATCH 0/8] usb: ehci: more bus glues as separate modules manjunath.goudar at linaro.org
2013-02-10 21:28 ` Jason Cooper
2013-02-11 18:45 ` Ben Dooks [this message]
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=51193C3F.6000908@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=linux-arm-kernel@lists.infradead.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).