[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1415150334-2402-1-git-send-email-chris@rorvick.com>
Date: Tue, 4 Nov 2014 19:18:44 -0600
From: Chris Rorvick <chris@...vick.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Chris Rorvick <chris@...vick.com>,
Alan Stern <stern@...land.harvard.edu>,
Oliver Neukum <oneukum@...e.de>, linux-kernel@...r.kernel.org,
linux-usb@...r.kernel.org
Subject: [PATCH 00/10] Create separate header for ehci-dbgp driver
The FUSBH200 and FOTG210 are not EHCI-compatible and require standalone
drivers. See discussion at:
http://comments.gmane.org/gmane.linux.usb.general/84169
But these controllers do implement an EHCI-compatible debug port and
therefore leverage the ehci-dbgp driver. Rather than pulling in the
necessary declarations from <linux/usb/ehci_def.h>, each driver copies
this code into their own header. The goal of this series is to pull the
ehci-dbgp related code into its own header to remove the need for this
redundancy.
Regards,
Chris Rorvick
Chris Rorvick (10):
usb: Create separate header for ehci-dbgp
fusbh200: Make Xen notification consistent with EHCI
fusbh200: Remove superfluous macro definitions
fusbh200: Remove duplicate ehci-dbgp declarations
fusbh200: Use ehci_dbg_port struct
fotg210: Make Xen notification consistent with EHCI
fotg210: Remove superfluous macro definitions
fotg210: Remove duplicate ehci-dbgp declarations
fotg210: Use ehci_dbg_port struct
usb: Remove __init from early_dbgp_init() prototype
drivers/usb/host/fotg210.h | 62 ++------------------------------
drivers/usb/host/fusbh200.h | 62 ++------------------------------
include/linux/usb/ehci-dbgp.h | 83 +++++++++++++++++++++++++++++++++++++++++++
include/linux/usb/ehci_def.h | 65 ++-------------------------------
4 files changed, 91 insertions(+), 181 deletions(-)
create mode 100644 include/linux/usb/ehci-dbgp.h
--
1.9.3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists