Part Number: SN65DSI86-Q1
Other Parts Discussed in Thread: SN65DSI86
We are currently debugging the SN65DSI86 eDP bridge on our platform using the SN65DSI86IPAPRQ1 device.
We observed that the EN pin of the SN65DSI86 goes LOW after the system completes booting and we see the following messages in the kernel log:
auxiliary ti_sn65dsi86.bridge.0: deferred probe pending
ti_sn65dsi86.bridge.0 ti_sn65dsi86.bridge: failed to attach dsi host
We are using the following Device Tree configuration:
edp_bridge: bridge@2d {
compatible = "ti,sn65dsi86";
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_edp_bridge>;
reg = <0x2d>;
clocks = <&audioclk>;
clock-names = "refclk";
enable-gpios = <&gpio5 11 GPIO_ACTIVE_HIGH>;
interrupt-parent = <&gpio5>;
interrupts = <9 IRQ_TYPE_LEVEL_LOW>;
vccio-supply = <®_1p8v>;
vpll-supply = <®_1p8v>;
vcca-supply = <®_main_1v2>;
vcc-supply = <®_main_1v2>;
status = "okay";
ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
edp_bridge_in: endpoint {
remote-endpoint = <&mipi_dsi_out>;
};
};
port@1 {
reg = <1>;
edp_bridge_out: endpoint {
remote-endpoint = <&panel_in>;
};
};
};
aux-bus {
panel: panel {
compatible = "edp-panel";
power-supply = <®_3p3v>;
backlight = <&edp_backlight0>;
status = "okay";
port {
panel_in: endpoint {
remote-endpoint = <&edp_bridge_out>;
};
};
};
};
};
We are using the following Linux driver as reference:
https://github.com/nxp-imx/linux-imx/blob/lf-6.6.y/drivers/gpu/drm/bridge/ti-sn65dsi86.c
Could you please clarify the following points?
Under what conditions does the SN65DSI86 driver drive the EN GPIO LOW after boot?
Is the EN GPIO expected to be toggled LOW/HIGH during the driver's probe, runtime PM, or DSI host attachment sequence?
Could the "failed to attach dsi host" error cause the driver to disable the EN GPIO?
Is there any dependency between the REFCLK configuration, power supplies, EN GPIO, and DSI host attachment that could result in this behavior?
Please advise which driver functions/registers we should specifically check to determine why the EN pin is being driven LOW after boot.
We would appreciate your guidance on the expected EN pin behavior and the recommended debugging procedure.
Regards,
Ashwini A
