History log of /drivers/usb/host/fhci-dbg.c
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
27729aadd31dafddaaf64c24f8ef6d0ff750f3aa 24-Apr-2010 Eric Lescouet <Eric.Lescouet@virtuallogix.com> USB: make hcd.h public (drivers dependency)

The usbcore headers: hcd.h and hub.h are shared between usbcore,
HCDs and a couple of other drivers (e.g. USBIP modules).
So, it makes sense to move them into a more public location and
to cleanup dependency of those modules on kernel internal headers.
This patch moves hcd.h from drivers/usb/core into include/linux/usb/

Signed-of-by: Eric Lescouet <eric@lescouet.org>
Cc: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
/drivers/usb/host/fhci-dbg.c
66536ab36895f7da718693c21f2bde3247c8cf07 25-Apr-2009 Greg Kroah-Hartman <gregkh@suse.de> USB: FHCI: use the new usb debugfs directory

All usb debugfs files should be behind the usb directory, not at the
root of debugfs.

Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
/drivers/usb/host/fhci-dbg.c
6866ac9db02ac1ec71f2aa720a1019581f69a725 16-Feb-2009 Sachin Sant <sachinp@in.ibm.com> USB: FHCI: use dev_name() in place of bus_id.

Replace references to bus_id with dev_name() to fix fhci driver build break.

drivers/usb/host/fhci-hcd.c:586: error: struct device has no member named bus_id
drivers/usb/host/fhci-hcd.c:653: error: struct device has no member named bus_id
drivers/usb/host/fhci-dbg.c:111: error: struct device has no member named bus_id

Signed-off-by: Sachin Sant <sachinp@in.ibm.com>
Acked-by: Anton Vorontsov <avorontsov@ru.mvista.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
/drivers/usb/host/fhci-dbg.c
236dd4d18f293e3c9798f35c08272196826a980d 10-Jan-2009 Anton Vorontsov <avorontsov@ru.mvista.com> USB: Driver for Freescale QUICC Engine USB Host Controller

This patch adds support for the FHCI USB controller, as found
in the Freescale MPC836x and MPC832x processors. It can support
Full or Low speed modes.

Quite a lot the hardware is doing by itself (SOF generation, CRC
generation and checking), though scheduling and retransmission is on
software's shoulders.

This controller does not integrate the root hub, so this driver also
fakes one-port hub. External hub is required to support more than
one device.

Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
/drivers/usb/host/fhci-dbg.c