[U-Boot] CAN support in u-boot
Hello, I have got a CAN controller (*Atmel SAM9263 Board*) which i want to test in u-boot to make sure it covers all the basic test required for its functionalities( like sending CAN frame, receving CAN frame etc). For the time being i cannot test it in kernel as it increases to much abstraction which is not desirable for me. Can you guide me to write some basic test cases in u-boot which can test the Controller on a basic level or give me some links which are doing similar things which i intened. regards -Puneet The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] USB3.0 Interrupt transfer in u-boot
Hello Vivek, I did made use of the patches you added for XHCI support in u-boot and with the help of them only was able to enumerate USB devices connected over USB3.0 port and also do BULK transfer. With respect to Interrupt transfer, i did tried to make use of kernel code but unfortunately couldn't made it work. If you can give some tips or guidance of where should i look that would be very helpful for me. Thanks Puneet On Thu, 2013-04-04 at 16:33 +0530, Vivek Gautam wrote: > Hello Puneet, > > > On Thu, Apr 4, 2013 at 11:55 AM, Puneet Sharma > wrote: > > Hello, > > > > I want to test USB keyboard for XHCI in u-boot and to do that i need the > > Interrupt transfer code in XHCI controller driver in u-boot. If > > possible, can you help me to give that piece of code or can you help me > > to figure out in kernel where can i find it so that i can try to > > replicate it in u-boot and make it work. > > We had posted some patches for XHCI stack driver, but unfortunately > that didn't have support > for interrupt transfer. > Please check in the Linux kernel (drivers/usb/host/xhci*), see if you > can find something for your use > which can be added to this XHCI stack to enable support for interrupt > transfer. > > > -- Puneet Sharma The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] USB3.0 Interrupt transfer in u-boot
Hello, I want to test USB keyboard for XHCI in u-boot and to do that i need the Interrupt transfer code in XHCI controller driver in u-boot. If possible, can you help me to give that piece of code or can you help me to figure out in kernel where can i find it so that i can try to replicate it in u-boot and make it work. Thanks & Regards -- Puneet Sharma The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] USB ehci driver query
Hello, I am new to u-boot code. I am reading the usb host controller code for root hub configuration. I have some queries regarding some code. If anyone has got understanding about it pls explain it to me. In usb.c the core calls the usb controller driver (ehci-hcd.c) by issuing command GET_DESCRIPTOR to know the maximum packet size the endpoint supports. It than once again calls the driver by issuing command SET_ADDRESS to give address 1 to root hub. Than it issues command GET_DESCRIPTOR second time and this time creates a queue head(QH) and associated queue transfer descriptors(qTD). The code for this is in function ehci_submit_async() (drivers/usb/host/ehci-hcd.c). I am not getting the purpose of calling this function and what the usb core is achieving by calling it. If anyone can throw some light on it. Regards -- Puneet Sharma The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] USB ehci driver query
Hello, I am new to u-boot code. I am reading the usb host controller code for root hub configuration. I have some queries regarding some code. If anyone has got understanding about it pls explain it to me. In usb.c the core calls the usb controller driver (ehci-hcd.c) by issuing command GET_DESCRIPTOR to know the maximum packet size the endpoint supports. It than once again calls the driver by issuing command SET_ADDRESS to give address 1 to root hub. Than it issues command GET_DESCRIPTOR second time and this time creates a queue head and associated queue transfer descriptors. The code for this is in function ehci_submit_async() (drivers/usb/host/ehci-hcd.c). I am not getting the purpose of calling this function and what the usb core is achieving by calling it. If anyone can throw some light on it. Regards -- Puneet Sharma The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
