Re: am335x: linux 3.16-rc3: USB DMA issue
On Wed, Jul 2, 2014 at 3:28 PM, Yegor Yefremov yegorsli...@googlemail.com wrote: On Tue, Jul 1, 2014 at 5:37 PM, Ezequiel García ezequ...@vanguardiasur.com.ar wrote: On 1 July 2014 12:07, Yegor Yefremov yegorsli...@googlemail.com wrote: [..] What can be done with these error messages: of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/usb@4740/usb-phy@47401300[0]' 47401300.usb-phy supply vcc not found, using dummy regulator musb-hdrc musb-hdrc.0.auto: Failed to request rx1. musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 platform musb-hdrc.0.auto: Driver musb-hdrc requests probe deferral of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/usb@4740/usb-phy@47401b00[0]' 47401b00.usb-phy supply vcc not found, using dummy regulator musb-hdrc musb-hdrc.1.auto: Failed to request rx1. musb-hdrc musb-hdrc.1.auto: musb_init_controller failed with status -517 platform musb-hdrc.1.auto: Driver musb-hdrc requests probe deferral couldn't find an available UDC The above are typical deferal messages. Have you tried building everything as a module or moving the DMA devicetree node so it's probed earlier? But I'm not sure it's related to the problem you are seeing. Compiling as a module helped. Thanks. I experience another issue, that happens either in monolithic kernel or as modules. In 2-4% of power cycles the hub chip connected to USB0 won't be detected. So far I couldn't find any error messages. Any idea? Yegor -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: am335x: linux 3.16-rc3: USB DMA issue
On Tue, Jul 1, 2014 at 5:37 PM, Ezequiel García ezequ...@vanguardiasur.com.ar wrote: On 1 July 2014 12:07, Yegor Yefremov yegorsli...@googlemail.com wrote: [..] What can be done with these error messages: of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/usb@4740/usb-phy@47401300[0]' 47401300.usb-phy supply vcc not found, using dummy regulator musb-hdrc musb-hdrc.0.auto: Failed to request rx1. musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 platform musb-hdrc.0.auto: Driver musb-hdrc requests probe deferral of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/usb@4740/usb-phy@47401b00[0]' 47401b00.usb-phy supply vcc not found, using dummy regulator musb-hdrc musb-hdrc.1.auto: Failed to request rx1. musb-hdrc musb-hdrc.1.auto: musb_init_controller failed with status -517 platform musb-hdrc.1.auto: Driver musb-hdrc requests probe deferral couldn't find an available UDC The above are typical deferal messages. Have you tried building everything as a module or moving the DMA devicetree node so it's probed earlier? But I'm not sure it's related to the problem you are seeing. Compiling as a module helped. Thanks. Yegor -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: am335x: linux 3.16-rc3: USB DMA issue
On Tue, Jul 1, 2014 at 5:43 PM, Bin Liu binml...@gmail.com wrote: On Tue, Jul 1, 2014 at 10:37 AM, Ezequiel García ezequ...@vanguardiasur.com.ar wrote: On 1 July 2014 12:07, Yegor Yefremov yegorsli...@googlemail.com wrote: [..] What can be done with these error messages: of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/usb@4740/usb-phy@47401300[0]' 47401300.usb-phy supply vcc not found, using dummy regulator musb-hdrc musb-hdrc.0.auto: Failed to request rx1. musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 platform musb-hdrc.0.auto: Driver musb-hdrc requests probe deferral of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/usb@4740/usb-phy@47401b00[0]' 47401b00.usb-phy supply vcc not found, using dummy regulator musb-hdrc musb-hdrc.1.auto: Failed to request rx1. musb-hdrc musb-hdrc.1.auto: musb_init_controller failed with status -517 platform musb-hdrc.1.auto: Driver musb-hdrc requests probe deferral couldn't find an available UDC The above are typical deferal messages. Have you tried building everything as a module or moving the DMA devicetree node so it's probed earlier? But I'm not sure it's related to the problem you are seeing. It might be ZLP related. Daniel's patch dma: cppi41: handle 0-length packets might solve it. Have applied the patch, but it didn't help. Compiling the drivers as a module help for now. Yegor -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
am335x: linux 3.16-rc3: USB DMA issue
I have following system: USB0: host mode (USB hub is soldered internally) USB1: OTG mode with OTG connector My DTS: http://pastebin.com/KB3iTehQ If I enable DMA in the kernel, I get USB0 working, i.e. USB hub is detected and USB devices, that are connected to this hub are also detected and working. The USB thumb drive connected to USB1 won't be detected. # lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=musb-hdrc/1p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=musb-hdrc/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 480M |__ Port 3: Dev 3, If 0, Class=Communications, Driver=cdc_acm, 12M |__ Port 3: Dev 3, If 1, Class=CDC Data, Driver=cdc_acm, 12M of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/usb@4740/usb-phy@47401300[0]' 47401300.usb-phy supply vcc not found, using dummy regulator musb-hdrc musb-hdrc.0.auto: Failed to request rx1. musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 platform musb-hdrc.0.auto: Driver musb-hdrc requests probe deferral of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/usb@4740/usb-phy@47401b00[0]' 47401b00.usb-phy supply vcc not found, using dummy regulator musb-hdrc musb-hdrc.1.auto: Failed to request rx1. musb-hdrc musb-hdrc.1.auto: musb_init_controller failed with status -517 platform musb-hdrc.1.auto: Driver musb-hdrc requests probe deferral usbcore: registered new interface driver usbhid usbhid: USB HID core driver musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory musb-hdrc musb-hdrc.0.auto: MUSB HDRC host driver musb-hdrc musb-hdrc.0.auto: new USB bus registered, assigned bus number 1 usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: MUSB HDRC host driver usb usb1: Manufacturer: Linux 3.16.0-rc3-6-g16874b2 musb-hcd usb usb1: SerialNumber: musb-hdrc.0.auto musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 2 usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb2: Product: MUSB HDRC host driver usb usb2: Manufacturer: Linux 3.16.0-rc3-6-g16874b2 musb-hcd usb usb2: SerialNumber: musb-hdrc.1.auto usb 1-1: new high-speed USB device number 2 using musb-hdrc usb 1-1: New USB device found, idVendor=05e3, idProduct=0608 usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 usb 1-1: Product: USB2.0 Hub usb 1-1.3: new full-speed USB device number 3 using musb-hdrc usb 1-1.3: New USB device found, idVendor=1546, idProduct=01a7 usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-1.3: Product: u-blox 7 - GPS/GNSS Receiver usb 1-1.3: Manufacturer: u-blox AG - www.u-blox.com usb 1-1.2: new high-speed USB device number 4 using musb-hdrc usb 1-1.2: New USB device found, idVendor=1307, idProduct=0165 usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-1.2: Product: USB Mass Storage Device usb 1-1.2: Manufacturer: USBest Technology usb 1-1.2: SerialNumber: 000504 usb-storage 1-1.2:1.0: USB Mass Storage device detected scsi0 : usb-storage 1-1.2:1.0 If I disable DMA in the kernel, I have reverse behavior: USB1 is working, USB0 doesn't see the hub. # lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=musb-hdrc/1p, 480M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=musb-hdrc/1p, 480M of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/usb@4740/usb-phy@47401300[0]' 47401300.usb-phy supply vcc not found, using dummy regulator musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory musb-hdrc musb-hdrc.0.auto: MUSB HDRC host driver musb-hdrc musb-hdrc.0.auto: new USB bus registered, assigned bus number 1 usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: MUSB HDRC host driver usb usb1: Manufacturer: Linux 3.16.0-rc3-6-g16874b2 musb-hcd usb usb1: SerialNumber: musb-hdrc.0.auto of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/usb@4740/usb-phy@47401b00[0]' 47401b00.usb-phy supply vcc not found, using dummy regulator musb-hdrc: ConfigData=0xde
Re: am335x: linux 3.16-rc3: USB DMA issue
On Tue, Jul 1, 2014 at 3:03 PM, Yegor Yefremov yegorsli...@googlemail.com wrote: I have following system: USB0: host mode (USB hub is soldered internally) USB1: OTG mode with OTG connector My DTS: http://pastebin.com/KB3iTehQ If I enable DMA in the kernel, I get USB0 working, i.e. USB hub is detected and USB devices, that are connected to this hub are also detected and working. The USB thumb drive connected to USB1 won't be detected. # lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=musb-hdrc/1p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=musb-hdrc/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 480M |__ Port 3: Dev 3, If 0, Class=Communications, Driver=cdc_acm, 12M |__ Port 3: Dev 3, If 1, Class=CDC Data, Driver=cdc_acm, 12M of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/usb@4740/usb-phy@47401300[0]' 47401300.usb-phy supply vcc not found, using dummy regulator musb-hdrc musb-hdrc.0.auto: Failed to request rx1. musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 platform musb-hdrc.0.auto: Driver musb-hdrc requests probe deferral of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/usb@4740/usb-phy@47401b00[0]' 47401b00.usb-phy supply vcc not found, using dummy regulator musb-hdrc musb-hdrc.1.auto: Failed to request rx1. musb-hdrc musb-hdrc.1.auto: musb_init_controller failed with status -517 platform musb-hdrc.1.auto: Driver musb-hdrc requests probe deferral usbcore: registered new interface driver usbhid usbhid: USB HID core driver musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory musb-hdrc musb-hdrc.0.auto: MUSB HDRC host driver musb-hdrc musb-hdrc.0.auto: new USB bus registered, assigned bus number 1 usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: MUSB HDRC host driver usb usb1: Manufacturer: Linux 3.16.0-rc3-6-g16874b2 musb-hcd usb usb1: SerialNumber: musb-hdrc.0.auto musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 2 usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb2: Product: MUSB HDRC host driver usb usb2: Manufacturer: Linux 3.16.0-rc3-6-g16874b2 musb-hcd usb usb2: SerialNumber: musb-hdrc.1.auto usb 1-1: new high-speed USB device number 2 using musb-hdrc usb 1-1: New USB device found, idVendor=05e3, idProduct=0608 usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 usb 1-1: Product: USB2.0 Hub usb 1-1.3: new full-speed USB device number 3 using musb-hdrc usb 1-1.3: New USB device found, idVendor=1546, idProduct=01a7 usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-1.3: Product: u-blox 7 - GPS/GNSS Receiver usb 1-1.3: Manufacturer: u-blox AG - www.u-blox.com usb 1-1.2: new high-speed USB device number 4 using musb-hdrc usb 1-1.2: New USB device found, idVendor=1307, idProduct=0165 usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-1.2: Product: USB Mass Storage Device usb 1-1.2: Manufacturer: USBest Technology usb 1-1.2: SerialNumber: 000504 usb-storage 1-1.2:1.0: USB Mass Storage device detected scsi0 : usb-storage 1-1.2:1.0 If I disable DMA in the kernel, I have reverse behavior: USB1 is working, USB0 doesn't see the hub. # lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=musb-hdrc/1p, 480M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=musb-hdrc/1p, 480M of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/usb@4740/usb-phy@47401300[0]' 47401300.usb-phy supply vcc not found, using dummy regulator musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory musb-hdrc musb-hdrc.0.auto: MUSB HDRC host driver musb-hdrc musb-hdrc.0.auto: new USB bus registered, assigned bus number 1 usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: MUSB HDRC host driver usb usb1: Manufacturer: Linux 3.16.0-rc3-6-g16874b2 musb-hcd usb usb1: SerialNumber: musb-hdrc.0.auto
Re: am335x: linux 3.16-rc3: USB DMA issue
On 1 July 2014 12:07, Yegor Yefremov yegorsli...@googlemail.com wrote: [..] What can be done with these error messages: of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/usb@4740/usb-phy@47401300[0]' 47401300.usb-phy supply vcc not found, using dummy regulator musb-hdrc musb-hdrc.0.auto: Failed to request rx1. musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 platform musb-hdrc.0.auto: Driver musb-hdrc requests probe deferral of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/usb@4740/usb-phy@47401b00[0]' 47401b00.usb-phy supply vcc not found, using dummy regulator musb-hdrc musb-hdrc.1.auto: Failed to request rx1. musb-hdrc musb-hdrc.1.auto: musb_init_controller failed with status -517 platform musb-hdrc.1.auto: Driver musb-hdrc requests probe deferral couldn't find an available UDC The above are typical deferal messages. Have you tried building everything as a module or moving the DMA devicetree node so it's probed earlier? But I'm not sure it's related to the problem you are seeing. -- Ezequiel García, VanguardiaSur www.vanguardiasur.com.ar -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: am335x: linux 3.16-rc3: USB DMA issue
On Tue, Jul 1, 2014 at 10:37 AM, Ezequiel García ezequ...@vanguardiasur.com.ar wrote: On 1 July 2014 12:07, Yegor Yefremov yegorsli...@googlemail.com wrote: [..] What can be done with these error messages: of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/usb@4740/usb-phy@47401300[0]' 47401300.usb-phy supply vcc not found, using dummy regulator musb-hdrc musb-hdrc.0.auto: Failed to request rx1. musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 platform musb-hdrc.0.auto: Driver musb-hdrc requests probe deferral of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/usb@4740/usb-phy@47401b00[0]' 47401b00.usb-phy supply vcc not found, using dummy regulator musb-hdrc musb-hdrc.1.auto: Failed to request rx1. musb-hdrc musb-hdrc.1.auto: musb_init_controller failed with status -517 platform musb-hdrc.1.auto: Driver musb-hdrc requests probe deferral couldn't find an available UDC The above are typical deferal messages. Have you tried building everything as a module or moving the DMA devicetree node so it's probed earlier? But I'm not sure it's related to the problem you are seeing. It might be ZLP related. Daniel's patch dma: cppi41: handle 0-length packets might solve it. -Bin. -- Ezequiel García, VanguardiaSur www.vanguardiasur.com.ar -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
