Hi On 4/21/2020 1:13 PM, Heikki Krogerus wrote: > Adding linux-usb mailing list. > > On Mon, Apr 20, 2020 at 07:09:17PM +0530, Shah, Nehal-bakulchandra wrote: >> Hi Heikki , >> >> I need some pointer from you, so in a system where I have UCSI driver for DRD >> Controller, then how call stack will be? >> >> I am unable to comprehend the flow from UCSI infrastructure to DRD controller >> code base. > Do you need to tell the negotiated data role to your USB controller > driver from the UCSI driver? For that we would need to know which USB > controller, or more precisely, which USB port is connected to the > USB Type-C connector in question. > > That would require ACPI tables to be able to describe the connection > between the USB Type-C connector and the USB port (and the connection > between DisplayPort and the USB Type-C connector etc.). Unfortunately > there is currently no documented way of doing that, however, there is > a proposal for a document the defines how the USB Type-C connectors > should be described in ACPI in general. The proposal does consider > this problem as well. For this the solution is to use _DSD device > properties "usb2-port" and "usb3-port" that have references to the > correct USB port nodes as values. > > Which USB controller are you using btw? > > thanks, Thanks for the mail. Here is the configuration 1. DRD Controller (DWC3 controller) 2. TI PD Controller 3. TI PD Controller and Host has I2C as transport layer. So ACPI mechanism wont work here. Hence i was wondering, is there any way from UCSI Driver we inform to DWC3 driver stack about Role change. I can understand one point that, DWC3 controller can work without UCSI Implementation i.e Only PD firmware. But i want to understand if there is a role change, PD interrupt will be generated and UCSI Driver will come to know about this role change. But from this onwards , i am unable to comprehend how it can be propagated upto DWC3 stack. Thanks Nehal Shah
