Hi Dmitry, what are your thoughts on Abhishek's comment? I think we should attempt to register the alternate mode when CONFIG_TYPEC_DP_ALTMODE is not enabled. It would give us a more accurate representation of the partner in user space. I understand your point about ignoring a potential EOPNOTSUPP response from the non-stub function. What if we leave ucsi.c alone, and replace the stub function's null return with a call to typec_port_register_altmode(). That would register DP altmode as an unsupported mode when CONFIG_TYPEC_DP_ALTMODE is not enabled, and fix the null pointer dereference. But, it won't change behavior when CONFIG_TYPEC_DP_ALTMODE is enabled. Hi Markus, thanks for your feedback. I'll update the commit message to say "null pointer dereference" when I upload a v3 series. Thanks, Jameson
