the OTG ID PIN is no longer needed?
But i.MX8MP even has no CC pin, how this chip can support typeC without peripheral circuits?
Without typeC peripheral circuits, how i.MX8MP can do role switch as you said "the OTG ID PIN is no longer needed"?
It is changed to using gpio usb id from a dedicated usb id pin from the infomation in schematic.
As I know linux can deal with the DRD message from typeC and gpio usb id pin both.
The default usb id in linux is using gpio as usb id.
Could you please explain the following?
It mainly depends on whether the physical interface is type-c or OTG's AB interface. If it is Type-c, then you need to refer to the development board and add a ptn5110. If it is the AB interface of OTG, then the ID pin needs to be connected to a GPIO, software Here you need to use a GPIO-based exton driver.
&usb_dwc3_0 {
dr_mode = "otg";
hnp-disable;
srp-disable;
adp-disable;
extcon = <&extcon_usb0>;
status = "okay";
};
extcon_usb0: extcon-usb0 {
compatible = "linux,extcon-usb-gpio";
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_usb0_extcon>;
id-gpios = <&gpio1 3 GPIO_ACTIVE_HIGH>;
};
arch\arm64\boot\dts\freescale\imx8mp-msc-sm2s.dtsi Example of third-party boards, it requires the OTG ID pin to generate an interrupt. USB_DNUx cannot be used as GPIO and cannot generate interrupts, so the OTG Driver cannot run.
Regards
Harvey
I don't need you to explain anything. I know that than you can do.
I asked you to explain is to ask NXP to improve support quality.
OTG's AB interface?
Have you read Cable and Connector Specification?
AB interface could be a OTG?
Even USB 3.0 A SS and USB 3.0 B SS have no id pin defined. How it can be " OTG's AB interface"?