On Tue, May 15, 2018 at 9:26 AM, Felipe Balbi <balbi@xxxxxxxxxx> wrote: > Andrzej Hajda <a.hajda@xxxxxxxxxxx> writes: > >> extcon device is used to detect host/device connection. Since extcon >> OF property is deprecated, alternative method should be added. >> This method uses OF graph bindings to locate extcon. >> >> Signed-off-by: Andrzej Hajda <a.hajda@xxxxxxxxxxx> >> --- >> Hi all, >> >> This patch implements alternative method to get extcon from DWC3. >> The code works but is hacky, as DWC3 must traverse different DT nodes >> to get extcon, in case of TM2 it is USB-PHY and MUIC, but other >> platforms can have different paths. >> I would be glad if it can be merged as is for now, but additional work >> must be done to make it generic. >> I guess on DT binding side it is OK. So the problem should be addressed >> in the code. >> My rough idea is to implement kind of extcon aliases/forwarder mechanism, >> ie. USB-PHY will expect on its output remote port extcon, and it should register >> extcon-forwarder pointing to this extcon. This way DWC3 can look for the extcon >> on its PHY phandle, and it will receive via forwarding mechanism extcon >> exposed by MUIC. >> As I said this is rough idea for discussion, other propositions are welcome. >> >> Regards >> Andrzej > > I need someone from devicetree to review and ack patch2 before I can > apply them. Either way, this doesn't apply: The DTS patch will go through arm-soc tree, I'll take it. The DTS patches are independent from drivers and shall not usually go through regular trees. Best regards, Krzysztof -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html