Hi Krzysztof, Hi all,
On 02.05.23 12:59, Krzysztof Kozlowski wrote:
...
Apologies for this, just very busy times. :)
Thanks for letting me know. Take the time you need.
Writing towards the list:
I think there is a misunderstanding here.
The connector node provides information about the installed USB
hardware. E.g. property "usb-role-switch" means "Indicates that the
device is capable of assigning the USB data role (USB host or USB
device) for a given USB connector [...]" [5]. To my understanding, in
relation with a port node this actually says that this port has this
capability. This is not relevant to the rt5033-charger driver.
The rt5033-charger driver needs to pair with the extcon chip because it
needs the information about *external* connectors being attached [6].
Extcon devices like SM5502 or SM5504 are real hardware. I'm not adding
new properties. The way of getting an excton device from the devicetree
by phandle is part of the extcon subsystem:
- function to get the excton device by phandle: [7]
- line that's looking for the property "extcon": [8]
The connector node is the wrong approach, as far as I can tell on my
current state of knowledge. It doesn't provide the information needed by
the rt5033-charger driver.
[5]
https://github.com/torvalds/linux/blob/v6.3/Documentation/devicetree/bindings/usb/usb-drd.yaml#L51-L55
[6]
https://github.com/torvalds/linux/blob/v6.3/include/linux/extcon.h#L32-L60
[7]
https://github.com/torvalds/linux/blob/v6.3/drivers/extcon/extcon.c#L1361-L1392
[8]
https://github.com/torvalds/linux/blob/v6.3/drivers/extcon/extcon.c#L1381
Kind regards,
Jakob
