Hi,
I double checked by changing the pinmux of I2C5_CLK/DATA (pin A53/C53) to DP_AUX_CH3_P/N function, and changing them back to I2C5_CLK/DATA function. And I can 100% confirm that the generated dtsi files are the same. And the converted pinmux .cfg files are the same as well.
From pinmux perspective, how come I2C and DP_AUX function gives the same dtsi and pinmux .cfg file?
How can I use devmem2 command to verify the pinmux settings for I2C5_CLK/DATA are really set to i2c?
I did some investigation on device-tree. It looks like I2C5 pinmux setting are set by “nvidia,tegra194-dpaux3-padctl” driver!
Here is the section that I am missing in my device-tree file:
host1x {
dpaux@155F0000 {
status = "okay";
compatible = "nvidia,tegra194-dpaux3-padctl";
/delete-property/ power-domains;
dpaux_default: pinmux@0 {
dpaux3_pins {
pins = "dpaux3-3";
function = "i2c";
};
};
};
};
And then in the I2C5 node, it has to set pinctrl to reference it:
i2c@31e0000 {
pinctrl-names = "default";
pinctrl-0 = <&dpaux_default>;
I think adding these in device-tree will make it to work.
In my carrier, I don’t have any display nor hdmi etc. So, I disabled all below in my device-tree:
nvdisplay@*
./sor*/hdmi-display
./sor*/dp-display
./dpaux@*
I am not 100% sure that enabling nvidia,tegra194-dpaux3-padctl on dpaux@155F0000 will cause any issue or not. I will test it tomorrow at work.
Can we add this pinmux setting in pinmux .cfg so that we can set it in i2c mode in pinmux MB1 CFG?
Regards.