6c59c5bb51
When doing a atomic commit affecting multiple crtc's, multiple events are generated. The user_data member does not allow you to distinguish, because they all have the same pointer. I've chosen to use crtc_id, because using pipe would create ambiguity when pipe = 0. A test for != 0 is easier to implement, and crtc_id will never be 0. Change-Id: Ie2daba50f711f298872f15498b8d46dedb38c0ff Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Cc: David Airlie <airlied@linux.ie> Cc: Daniel Stone <daniels@collabora.com> Signed-off-by: Mark Yao <mark.yao@rock-chips.com> (am from https://patchwork.kernel.org/patch/9272895/) |
||
|---|---|---|
| .. | ||
| acpi | ||
| asm-generic | ||
| clocksource | ||
| crypto | ||
| drm | ||
| dt-bindings | ||
| keys | ||
| kvm | ||
| linux | ||
| math-emu | ||
| media | ||
| memory | ||
| misc | ||
| net | ||
| pcmcia | ||
| ras | ||
| rdma | ||
| rxrpc | ||
| scsi | ||
| soc | ||
| sound | ||
| target | ||
| trace | ||
| uapi | ||
| video | ||
| xen | ||
| Kbuild | ||