Re: link state problem with dwc3 in supper-speed device mode

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Bin Liu <b-liu@xxxxxx> writes:
>> >> >> > There is no VBUS detection on this device and board. Is the VBUS
>> >> >> > detection needed for dwc3 to work in device mode? 
>> >> >> 
>> >> >> In the case of DRA7x, you don't *really* need detection. All you need to
>> >> >> do is correctly update UTMI mailbox.
>> >> >
>> >> > But the UTMI mailbox is driven by extcon events, right? The board
>> >> > doesn't have external circuit or gpio to detect VBUS.
>> >> 
>> >> Then you should use ID event to *also* fiddle with VBUSVALID bit. That
>> >> used to work just fine, I guess commit below broke it:
>> >
>> > I don't understand how this dra7-evm worked before. dwc3 is in SS device
>> > mode, microB cable does not ground ID pin, so there is ID event when
>> > attach/detach dwc3 to the host. I am confused...
>> 
>> Please read about the mailbox in your SoC. Try to figure out how it
>> works and what it does. What happens, internally, when you write
>> VBUS_VALID and/or IDGND bits. What does that mean to dwc3? When can dwc3
>> connect its data pullups? What information does it need in order to do
>> that? Many of these questions will be answered ;-)
>
> Yes, got the issue figured out, it is missing hardware trigger to the
> mailbox.

you can verify that by writing to UTMI mailbox with devmem2 ;-)

-- 
balbi

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux