Quoting aravindh@xxxxxxxxxxxxxx (2021-04-21 11:55:21) > On 2021-04-21 10:26, khsieh@xxxxxxxxxxxxxx wrote: > >> > >>> + > >>> mutex_unlock(&dp->event_mutex); > >>> > >>> return 0; > >>> @@ -1496,6 +1502,9 @@ int msm_dp_display_disable(struct msm_dp *dp, > >>> struct drm_encoder *encoder) > >>> /* stop sentinel checking */ > >>> dp_del_event(dp_display, EV_DISCONNECT_PENDING_TIMEOUT); > >>> > >>> + /* link is down, delete pending irq_hdps */ > >>> + dp_del_event(dp_display, EV_IRQ_HPD_INT); > >>> + > >> > >> I'm becoming convinced that the whole kthread design and event queue > >> is > >> broken. These sorts of patches are working around the larger problem > >> that the kthread is running independently of the driver and irqs can > >> come in at any time but the event queue is not checked from the irq > >> handler to debounce the irq event. Is the event queue necessary at > >> all? > >> I wonder if it would be simpler to just use an irq thread and process > >> the hpd signal from there. Then we're guaranteed to not get an irq > >> again > >> until the irq thread is done processing the event. This would > >> naturally > >> debounce the irq hpd event that way. > > event q just like bottom half of irq handler. it turns irq into event > > and handle them sequentially. > > irq_hpd is asynchronous event from panel to bring up attention of hsot > > during run time of operation. > > Here, the dongle is unplugged and main link had teared down so that no > > need to service pending irq_hpd if any. > > > > As Kuogee mentioned, IRQ_HPD is a message received from the panel and is > not like your typical HW generated IRQ. There is no guarantee that we > will not receive an IRQ_HPD until we are finished with processing of an > earlier HPD message or an IRQ_HPD message. For example - when you run > the protocol compliance, when we get a HPD from the sink, we are > expected to start reading DPCD, EDID and proceed with link training. As > soon as link training is finished (which is marked by a specific DPCD > register write), the sink is going to issue an IRQ_HPD. At this point, > we may not done with processing the HPD high as after link training we > would typically notify the user mode of the newly connected display, > etc. Given that the irq comes in and is then forked off to processing at a later time implies that IRQ_HPD can come in at practically anytime. Case in point, this patch, which is trying to selectively search through the "event queue" and then remove the event that is no longer relevant because the display is being turned off either by userspace or because HPD has gone away. If we got rid of the queue and kthread and processed irqs in a threaded irq handler I suspect the code would be simpler and not have to search through an event queue when we disable the display. Instead while disabling the display we would make sure that the irq thread isn't running anymore with synchronize_irq() or even disable the irq entirely, but really it would be better to just disable the irq in the hardware with a register write to some irq mask register. This pushes more of the logic for HPD and connect/disconnect into the hardware and avoids reimplementing that in software: searching through the queue, checking for duplicate events, etc. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
