Re: [PATCH v4 2/5] drm: Add HPD state to drm_connector_oob_hotplug_event()

2022-05-17 Thread Heikki Krogerus
On Mon, May 02, 2022 at 09:53:13AM -0700, Bjorn Andersson wrote: > In some implementations, such as the Qualcomm platforms, the display > driver has no way to query the current HPD state and as such it's > impossible to distinguish between disconnect and attention events. > > Add a parameter to dr

Re: [PATCH v4 2/5] drm: Add HPD state to drm_connector_oob_hotplug_event()

2022-05-16 Thread Hans de Goede
Hi, On 5/16/22 13:25, Heikki Krogerus wrote: > +Hans > > Hans, do you have any comments? Thanks for the ping, this looks good to me: Reviewed-by: Hans de Goede Regards, Hans > > On Mon, May 02, 2022 at 09:53:13AM -0700, Bjorn Andersson wrote: >> In some implementations, such as the Qualco

Re: [PATCH v4 2/5] drm: Add HPD state to drm_connector_oob_hotplug_event()

2022-05-16 Thread Heikki Krogerus
+Hans Hans, do you have any comments? On Mon, May 02, 2022 at 09:53:13AM -0700, Bjorn Andersson wrote: > In some implementations, such as the Qualcomm platforms, the display > driver has no way to query the current HPD state and as such it's > impossible to distinguish between disconnect and atte

[PATCH v4 2/5] drm: Add HPD state to drm_connector_oob_hotplug_event()

2022-05-02 Thread Bjorn Andersson
In some implementations, such as the Qualcomm platforms, the display driver has no way to query the current HPD state and as such it's impossible to distinguish between disconnect and attention events. Add a parameter to drm_connector_oob_hotplug_event() to pass the HPD state. Also push the test