* am335x: linux 3.16-rc3: USB DMA issue
@ 2014-07-01 13:03 Yegor Yefremov
2014-07-01 15:07 ` Yegor Yefremov
0 siblings, 1 reply; 7+ messages in thread
From: Yegor Yefremov @ 2014-07-01 13:03 UTC (permalink / raw)
To: linux-omap; +Cc: linux-usb, Felipe Balbi, Ezequiel Garcia, Roger Quadros
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@47400000/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@47400000/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-00006-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-00006-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: 00000000000504
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@47400000/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-00006-g16874b2 musb-hcd
usb usb1: SerialNumber: musb-hdrc.0.auto
of_get_named_gpiod_flags: can't parse gpios property of node
'/ocp/usb@47400000/usb-phy@47401b00[0]'
47401b00.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.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-00006-g16874b2 musb-hcd
usb usb2: SerialNumber: musb-hdrc.1.auto
usb0: HOST MAC 02:97:91:6a:a9:c6
usb0: MAC 06:cf:9d:85:16:7f
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usb 1-1: new high-speed USB device number 2 using musb-hdrc
usb 1-1: new high-speed USB device number 3 using musb-hdrc
usb 1-1: new high-speed USB device number 4 using musb-hdrc
usb 1-1: new high-speed USB device number 5 using musb-hdrc
usb 2-1: new high-speed USB device number 2 using musb-hdrc
usb 2-1: New USB device found, idVendor=1b8f, idProduct=0305
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1: Product: EXPRESS DUO
usb 2-1: Manufacturer: STT
usb 2-1: SerialNumber: 09021000000110490000000154
usb-storage 2-1:1.0: USB Mass Storage device detected
scsi0 : usb-storage 2-1:1.0
In 3.15 both interfaces were working. The only problem was, that my
GPS card didn't work with USB0 in DMA mode.
Regards,
Yegor
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: am335x: linux 3.16-rc3: USB DMA issue
2014-07-01 13:03 am335x: linux 3.16-rc3: USB DMA issue Yegor Yefremov
@ 2014-07-01 15:07 ` Yegor Yefremov
2014-07-01 15:37 ` Ezequiel García
0 siblings, 1 reply; 7+ messages in thread
From: Yegor Yefremov @ 2014-07-01 15:07 UTC (permalink / raw)
To: linux-omap
Cc: linux-usb, Felipe Balbi, Ezequiel Garcia, Roger Quadros, George Cherian
On Tue, Jul 1, 2014 at 3:03 PM, Yegor Yefremov
<yegorslists@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@47400000/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@47400000/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-00006-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-00006-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: 00000000000504
> 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@47400000/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-00006-g16874b2 musb-hcd
> usb usb1: SerialNumber: musb-hdrc.0.auto
> of_get_named_gpiod_flags: can't parse gpios property of node
> '/ocp/usb@47400000/usb-phy@47401b00[0]'
> 47401b00.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.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-00006-g16874b2 musb-hcd
> usb usb2: SerialNumber: musb-hdrc.1.auto
> usb0: HOST MAC 02:97:91:6a:a9:c6
> usb0: MAC 06:cf:9d:85:16:7f
> usbcore: registered new interface driver usbhid
> usbhid: USB HID core driver
> usb 1-1: new high-speed USB device number 2 using musb-hdrc
> usb 1-1: new high-speed USB device number 3 using musb-hdrc
> usb 1-1: new high-speed USB device number 4 using musb-hdrc
> usb 1-1: new high-speed USB device number 5 using musb-hdrc
> usb 2-1: new high-speed USB device number 2 using musb-hdrc
> usb 2-1: New USB device found, idVendor=1b8f, idProduct=0305
> usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 2-1: Product: EXPRESS DUO
> usb 2-1: Manufacturer: STT
> usb 2-1: SerialNumber: 09021000000110490000000154
> usb-storage 2-1:1.0: USB Mass Storage device detected
> scsi0 : usb-storage 2-1:1.0
>
> In 3.15 both interfaces were working. The only problem was, that my
> GPS card didn't work with USB0 in DMA mode.
What can be done with these error messages:
of_get_named_gpiod_flags: can't parse gpios property of node
'/ocp/usb@47400000/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@47400000/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
# uname -r
3.16.0-rc3-00006-g16874b2
Yegor
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: am335x: linux 3.16-rc3: USB DMA issue
2014-07-01 15:07 ` Yegor Yefremov
@ 2014-07-01 15:37 ` Ezequiel García
2014-07-01 15:43 ` Bin Liu
[not found] ` <CAAEAJfDaEt0PGhFOs0-Q6W8ogu1aEGMGarnbuBVzZHnuHm4zZQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
0 siblings, 2 replies; 7+ messages in thread
From: Ezequiel García @ 2014-07-01 15:37 UTC (permalink / raw)
To: Yegor Yefremov
Cc: linux-omap, linux-usb, Felipe Balbi, Roger Quadros, George Cherian
On 1 July 2014 12:07, Yegor Yefremov <yegorslists@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@47400000/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@47400000/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 majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: am335x: linux 3.16-rc3: USB DMA issue
2014-07-01 15:37 ` Ezequiel García
@ 2014-07-01 15:43 ` Bin Liu
[not found] ` <CADYTM3YkfzjUNrDaPrY_RwtRcstjSJ+o-ST31Z7z70f44-CuUA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[not found] ` <CAAEAJfDaEt0PGhFOs0-Q6W8ogu1aEGMGarnbuBVzZHnuHm4zZQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
1 sibling, 1 reply; 7+ messages in thread
From: Bin Liu @ 2014-07-01 15:43 UTC (permalink / raw)
To: Ezequiel García
Cc: Yegor Yefremov, linux-omap, linux-usb, Felipe Balbi,
Roger Quadros, George Cherian
On Tue, Jul 1, 2014 at 10:37 AM, Ezequiel García
<ezequiel@vanguardiasur.com.ar> wrote:
> On 1 July 2014 12:07, Yegor Yefremov <yegorslists@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@47400000/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@47400000/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 majordomo@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 majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: am335x: linux 3.16-rc3: USB DMA issue
[not found] ` <CAAEAJfDaEt0PGhFOs0-Q6W8ogu1aEGMGarnbuBVzZHnuHm4zZQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
@ 2014-07-02 13:28 ` Yegor Yefremov
2014-07-08 9:42 ` Yegor Yefremov
0 siblings, 1 reply; 7+ messages in thread
From: Yegor Yefremov @ 2014-07-02 13:28 UTC (permalink / raw)
To: Ezequiel García
Cc: linux-omap-u79uwXL29TY76Z2rM5mHXA, linux-usb, Felipe Balbi,
Roger Quadros, George Cherian
On Tue, Jul 1, 2014 at 5:37 PM, Ezequiel García
<ezequiel-30ULvvUtt6G51wMPkGsGjgyUoB5FGQPZ@public.gmane.org> wrote:
> On 1 July 2014 12:07, Yegor Yefremov <yegorslists-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> wrote:
> [..]
>>
>> What can be done with these error messages:
>>
>> of_get_named_gpiod_flags: can't parse gpios property of node
>> '/ocp/usb@47400000/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@47400000/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-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: am335x: linux 3.16-rc3: USB DMA issue
[not found] ` <CADYTM3YkfzjUNrDaPrY_RwtRcstjSJ+o-ST31Z7z70f44-CuUA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
@ 2014-07-02 13:29 ` Yegor Yefremov
0 siblings, 0 replies; 7+ messages in thread
From: Yegor Yefremov @ 2014-07-02 13:29 UTC (permalink / raw)
To: Bin Liu
Cc: Ezequiel García, linux-omap-u79uwXL29TY76Z2rM5mHXA,
linux-usb, Felipe Balbi, Roger Quadros, George Cherian
On Tue, Jul 1, 2014 at 5:43 PM, Bin Liu <binmlist-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> On Tue, Jul 1, 2014 at 10:37 AM, Ezequiel García
> <ezequiel-30ULvvUtt6G51wMPkGsGjgyUoB5FGQPZ@public.gmane.org> wrote:
>> On 1 July 2014 12:07, Yegor Yefremov <yegorslists-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> wrote:
>> [..]
>>>
>>> What can be done with these error messages:
>>>
>>> of_get_named_gpiod_flags: can't parse gpios property of node
>>> '/ocp/usb@47400000/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@47400000/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-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: am335x: linux 3.16-rc3: USB DMA issue
2014-07-02 13:28 ` Yegor Yefremov
@ 2014-07-08 9:42 ` Yegor Yefremov
0 siblings, 0 replies; 7+ messages in thread
From: Yegor Yefremov @ 2014-07-08 9:42 UTC (permalink / raw)
To: Ezequiel García
Cc: linux-omap, linux-usb, Felipe Balbi, Roger Quadros, George Cherian
On Wed, Jul 2, 2014 at 3:28 PM, Yegor Yefremov
<yegorslists@googlemail.com> wrote:
> On Tue, Jul 1, 2014 at 5:37 PM, Ezequiel García
> <ezequiel@vanguardiasur.com.ar> wrote:
>> On 1 July 2014 12:07, Yegor Yefremov <yegorslists@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@47400000/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@47400000/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 majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2014-07-08 9:42 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-07-01 13:03 am335x: linux 3.16-rc3: USB DMA issue Yegor Yefremov
2014-07-01 15:07 ` Yegor Yefremov
2014-07-01 15:37 ` Ezequiel García
2014-07-01 15:43 ` Bin Liu
[not found] ` <CADYTM3YkfzjUNrDaPrY_RwtRcstjSJ+o-ST31Z7z70f44-CuUA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-02 13:29 ` Yegor Yefremov
[not found] ` <CAAEAJfDaEt0PGhFOs0-Q6W8ogu1aEGMGarnbuBVzZHnuHm4zZQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-02 13:28 ` Yegor Yefremov
2014-07-08 9:42 ` Yegor Yefremov
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.