Kirill Dronov writes:
no changes whatsoever
>>> 2 changes:
>>> 1) added platform drivers in linux/drivers/platform/
>>> should not influence dwc3
>>> 2) the only dwc3 -related change is in dwc3_pci_quirks():
>>> I need different "baytrail" quirk - smsc 3310 does not have CS. So I
>>> request
On 04/19/2016 02:55 PM, Felipe Balbi wrote:
Hi,
Kirill Dronov writes:
> irq/19-dwc3-96[000] d..2 825.229265: dwc3_event: event 0301
Link change U3 [3] -> U0 [0]
Host reports: " new high-speed USB device number XX using ehci-pci"
Host Sends USB_REQ_GET_DESCRIPTOR 3 times, ge
Hi,
Kirill Dronov writes:
> irq/19-dwc3-96[000] d..2 825.229265: dwc3_event: event
0301
>>> Link change U3 [3] -> U0 [0]
>>> Host reports: " new high-speed USB device number XX using ehci-pci"
>>> Host Sends USB_REQ_GET_DESCRIPTOR 3 times, gets r=-71. No events
>>> de
On 04/19/2016 02:10 PM, Felipe Balbi wrote:
Hi,
Kirill Dronov writes:
Is something definitely wrong with initialization and enumeration traces?
I'll go read them
> irq/19-dwc3-96[000] d..2 824.785778: dwc3_event: event 00150301
Link State change -> RX.Detect
> irq/19-d
Hi,
Kirill Dronov writes:
Is something definitely wrong with initialization and enumeration traces?
>>> I'll go read them
>> > irq/19-dwc3-96[000] d..2 824.785778: dwc3_event: event 00150301
>>
>> Link State change -> RX.Detect
>>
>> > irq/19-dwc3-96[000] d..2 824.87
Hi,
On 04/19/2016 11:07 AM, Felipe Balbi wrote:
Hi,
Felipe Balbi writes:
Is something definitely wrong with initialization and enumeration traces?
I'll go read them
> irq/19-dwc3-96[000] d..2 824.785778: dwc3_event: event 00150301
Link State change -> RX.Detect
> irq/19-d
Hi,
Felipe Balbi writes:
>> Is something definitely wrong with initialization and enumeration traces?
>
> I'll go read them
> irq/19-dwc3-96[000] d..2 824.785778: dwc3_event: event 00150301
Link State change -> RX.Detect
> irq/19-dwc3-96[000] d..2 824.877339: dwc3_event:
Hi,
Kirill Dronov writes:
> I'm not sure if I hit “run/stop metastability” issue [“STAR#9000525659:
> Clock Domain Crossing on DCTL in USB 2.0 Mode”]. I don't have DWC3
we have a workaround for that, you shouldn't hit it unless you removed
the workaround.
>>> No, I didn't.
>> y
Hi,
On 04/12/2016 09:33 AM, Felipe Balbi wrote:
Hi,
Kirill Dronov writes:
Hi Felipe,
On 04/07/2016 08:10 AM, Felipe Balbi wrote:
Hi,
Kirill Dronov writes:
I'm working on USB device bringup on Intel E3800 – based board. DWC3
core configured as DRD in device mode. The only connected device p
Hi,
Kirill Dronov writes:
> Hi Felipe,
> On 04/07/2016 08:10 AM, Felipe Balbi wrote:
>> Hi,
>>
>> Kirill Dronov writes:
>>> I'm working on USB device bringup on Intel E3800 – based board. DWC3
>>> core configured as DRD in device mode. The only connected device phy
>>> is SMSC 3310 (USB2 ULPI).
Hi Felipe,
On 04/07/2016 08:10 AM, Felipe Balbi wrote:
Hi,
Kirill Dronov writes:
I'm working on USB device bringup on Intel E3800 – based board. DWC3
core configured as DRD in device mode. The only connected device phy
is SMSC 3310 (USB2 ULPI). DWC3 core version is 2.10A. Gadget zero
driver ca
Hi,
Kirill Dronov writes:
> I'm working on USB device bringup on Intel E3800 – based board. DWC3
> core configured as DRD in device mode. The only connected device phy
> is SMSC 3310 (USB2 ULPI). DWC3 core version is 2.10A. Gadget zero
> driver can be loaded, but device enumeration fails: device
Hi.
I'm working on USB device bringup on Intel E3800 – based board. DWC3
core configured as DRD in device mode. The only connected device phy is
SMSC 3310 (USB2 ULPI). DWC3 core version is 2.10A. Gadget zero driver
can be loaded, but device enumeration fails: device is detected by host,
speed
13 matches
Mail list logo
