Hi,
I am relatively a newbie at USB development.
My doubts are simple . Can any one shed some lights on these.
1) What is the relevance of "suspend and resume" call backs that we
find in struct device_driver.? There are also the same call backs in
struct hc_driver?. What are they used for. ? Are the "suspend/resume"
call backs are in hc_driver are supported for PCI controllers only..
?
2) When we write a EHCI-HCD driver for a non-pci controller driver ,
like that one for ARM-AMBA bus, which driver registration structure
should we use ,
Is it
struct platform_driver (As used in omap_ohci.c)
or
struct device_driver (As used in ehci-auxxx.c )
3) ARC controller has an embedded TT (transaction translators) built
in to it.? This allows Low Speed and Full Speed devices to be directly
connected to it, which can be identified from the PSPD(port speed
bit). My doubt is whether the ehci-hub.c and ehci-hcd.c in linux
2.6.15 and above have been modified to support the operational
differnces with respect to QH setup( like setting TTHA).
4) To put the above doubt briefly ,, can i reuse the files in the
2.6.15 and above kernel usb-ehci tree for implementing my controller
driver. Please remember that my controller has an embedded TT.
(Please has any one worked on ARC USB-OTG controller drivers). This
would be of great help... Please mention the files which can be
re-used as it is.. ?
Thanks
Rakesh
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
