fusbh200: Use ehci_dbg_port struct
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 <chris@rorvick.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
parent
e004631a4f
commit
da5d5c58f3
|
@ -86,7 +86,7 @@ struct fusbh200_hcd { /* one per controller */
|
|||
/* glue to PCI and HCD framework */
|
||||
struct fusbh200_caps __iomem *caps;
|
||||
struct fusbh200_regs __iomem *regs;
|
||||
struct fusbh200_dbg_port __iomem *debug;
|
||||
struct ehci_dbg_port __iomem *debug;
|
||||
|
||||
__u32 hcs_params; /* cached register copy */
|
||||
spinlock_t lock;
|
||||
|
@ -287,17 +287,6 @@ struct fusbh200_regs {
|
|||
#define BMIER_VBUS_ERR_EN (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 fusbh200_dbg_port {
|
||||
u32 control;
|
||||
u32 pids;
|
||||
u32 data03;
|
||||
u32 data47;
|
||||
u32 address;
|
||||
};
|
||||
|
||||
/*-------------------------------------------------------------------------*/
|
||||
|
||||
#define QTD_NEXT(fusbh200, dma) cpu_to_hc32(fusbh200, (u32)dma)
|
||||
|
|
Loading…
Reference in New Issue