On 12/9/20 6:04 PM, Patrick DELAUNAY wrote:
Hi,
[...]
I add a new property to be backward compatible (even it the
combinaison is less clear) I protect regulator function call to
avoid compilation
issue for other platform.
PS: after reading the refmanual, I also split VALOEN and VALOVAL bit
update
as it is required.
So yes I think it is needed but I can split the patch to simplify
the review.
I presume you don't feel like implementing proper OTG support, right ?
Yes, I am afraid of this task.
Can you take a look ?
I will pick this patch into next for now.
I check this topic, I think I don't need to support OTG in dwc2
but I need to support USB port and connector as it is done in linux kernel.
and I think that I can propose a plan (6 month-1 year)
- Add a new u-class for USB connector based on
linux/drivers/usb/typec/class.c
=> Allow to detect cable connection and USB mode (device / host)
- Add a new driver for USB type C connector (compatible "usb-c-connector")
- Migrate stusb1600 driver to use this new driver
- Update driver (dwc2 or usbphyc or directly in uclass ?) to use
connector when present in device tree
(devicetree/bindings/connector/usb-connector.yaml)
With these modifcations, I hope to have the same hooks than Linux.
And for future
- Add a USB typeC connector driver based on UCSI
(linux/drivers/usb/typec/ucsi)
https://www.intel.com/content/dam/www/public/us/en/documents/technical-specifications/usb-type-c-ucsi-spec.pdf
- Adapt other driver to use USB connector..... (as DWC3 for example to
manage dual role with type-c)
Sounds good, thanks :)
