* Query on the ci_udc driver for USB client implementation
@ 2014-10-30 6:53 Sanchayan Maity
0 siblings, 0 replies; 2+ messages in thread
From: Sanchayan Maity @ 2014-10-30 6:53 UTC (permalink / raw)
To: kernelnewbies
Hello,
I am currently implementing USB Host and client support for Freescale Vybrid platform in u-boot. I managed to get the host implementation working.
For the host side, usb start calls usb_init(), which in turns call, usb_lowlevel_init(), from there into the ehic_hcd_init() of my implementation. So, setting up the necessary clocks and plls for USB in my implementation and then setting up the usb_ehci, ehci_hccr and echi_hcor structures was all. The flow and setup required i was able to trace.
The USB client part is not clear to me. I was thinking i can use the ci_udc driver somehow to implement the client part. How can i use the ci_udc driver to implement client functionality?. From what i could see, the usb_gadget_driver_register() is suppose to be the first call. But, i couldn't trace from where this gets called or the flow and setup is suppose to be. OR Is a separate client driver required and nothing generic can be used akin to how it could be done for host?
Sorry if i am asking this question in the wrong place. I couldn't find anyone in the u-boot IRC channel nor find something similar to the kernel-newbies mailing list.
Hope i am asking the right questions.
Thanks & Regards,
Sanchayan Maity.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Query on the ci_udc driver for USB client implementation
@ 2014-10-30 7:54 Victor Ascroft
0 siblings, 0 replies; 2+ messages in thread
From: Victor Ascroft @ 2014-10-30 7:54 UTC (permalink / raw)
To: kernelnewbies
Hello,
I am currently implementing USB Host and client support for Freescale Vybrid platform in u-boot. I managed to get the host implementation working.
For the host side, usb start calls usb_init(), which in turns call, usb_lowlevel_init(), from there into the ehic_hcd_init() of my implementation. So, setting up the necessary clocks and plls for USB in my implementation and then setting up the usb_ehci, ehci_hccr and echi_hcor structures was all. The flow and setup required i was able to trace.
The USB client part is not clear to me. I was thinking i can use the ci_udc driver somehow to implement the client part. How can i use the ci_udc driver to implement client functionality?. From what i could see, the usb_gadget_driver_register() is suppose to be the first call. But, i couldn't trace from where this gets called or the flow and setup is suppose to be. OR Is a separate client driver required and nothing generic can be used akin to how it could be done for host?
Sorry if i am asking this question in the wrong place. I couldn't find anyone in the u-boot IRC channel nor find something similar to the kernel-newbies mailing list.
Hope i am asking the right questions. Sorry if this mail ends up two times in this list, i mistakenly tried sending it from the mail ID not registered with this mailing list.
Thanks & Regards,
Sanchayan Maity.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-10-30 7:54 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-10-30 6:53 Query on the ci_udc driver for USB client implementation Sanchayan Maity
-- strict thread matches above, loose matches on Subject: below --
2014-10-30 7:54 Victor Ascroft
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).