The FUSBH200 debug port has a EHCI-compatible register layout so there
is no need to define a custom struct.

Signed-off-by: Chris Rorvick <ch...@rorvick.com>
---
 drivers/usb/host/fotg210.h | 13 +------------
 1 file changed, 1 insertion(+), 12 deletions(-)

diff --git a/drivers/usb/host/fotg210.h b/drivers/usb/host/fotg210.h
index 975d9bb..3bad178 100644
--- a/drivers/usb/host/fotg210.h
+++ b/drivers/usb/host/fotg210.h
@@ -86,7 +86,7 @@ struct fotg210_hcd {                  /* one per controller */
        /* glue to PCI and HCD framework */
        struct fotg210_caps __iomem *caps;
        struct fotg210_regs __iomem *regs;
-       struct fotg210_dbg_port __iomem *debug;
+       struct ehci_dbg_port __iomem *debug;
 
        __u32                   hcs_params;     /* cached register copy */
        spinlock_t              lock;
@@ -295,17 +295,6 @@ struct fotg210_regs {
 #define GMIR_MDEV_INT  (1 << 0)
 };
 
-/* Appendix C, Debug port ... intended for use with special "debug devices"
- * that can help if there's no serial console.  (nonstandard enumeration.)
- */
-struct fotg210_dbg_port {
-       u32     control;
-       u32     pids;
-       u32     data03;
-       u32     data47;
-       u32     address;
-};
-
 /*-------------------------------------------------------------------------*/
 
 #define        QTD_NEXT(fotg210, dma)  cpu_to_hc32(fotg210, (u32)dma)
-- 
1.9.3

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to