Am Sonntag, den 13.04.2014, 15:58 +0100 schrieb Russell King - ARM
Linux:
On Fri, Apr 11, 2014 at 04:13:33PM +0200, Lucas Stach wrote:
Make sure that we probe for a display on detect regardless
of previous hotplug events. Don't handle connector
hotplug state ourselves, but let DRM do the
On Mon, Apr 14, 2014 at 10:42:32AM +0200, Lucas Stach wrote:
Am Sonntag, den 13.04.2014, 15:58 +0100 schrieb Russell King - ARM
Linux:
On Fri, Apr 11, 2014 at 04:13:33PM +0200, Lucas Stach wrote:
Make sure that we probe for a display on detect regardless
of previous hotplug events. Don't
Am Montag, den 14.04.2014, 10:10 +0100 schrieb Russell King - ARM Linux:
On Mon, Apr 14, 2014 at 10:42:32AM +0200, Lucas Stach wrote:
Am Sonntag, den 13.04.2014, 15:58 +0100 schrieb Russell King - ARM
Linux:
On Fri, Apr 11, 2014 at 04:13:33PM +0200, Lucas Stach wrote:
Make sure that we
On Mon, Apr 14, 2014 at 11:38:43AM +0200, Lucas Stach wrote:
Am Montag, den 14.04.2014, 10:10 +0100 schrieb Russell King - ARM Linux:
On Mon, Apr 14, 2014 at 10:42:32AM +0200, Lucas Stach wrote:
Am Sonntag, den 13.04.2014, 15:58 +0100 schrieb Russell King - ARM
Linux:
On Fri, Apr 11,
On Mon, Apr 14, 2014 at 12:24:45PM +0200, Lucas Stach wrote:
Am Montag, den 14.04.2014, 11:09 +0100 schrieb Russell King - ARM Linux:
Now *you* please go back and read what you said about kms/userspace being
able to poll the connector, thereby causing an EDID read attempt while
HPD may not
On Fri, Apr 11, 2014 at 04:13:33PM +0200, Lucas Stach wrote:
Make sure that we probe for a display on detect regardless
of previous hotplug events. Don't handle connector
hotplug state ourselves, but let DRM do the right thing
for us. This brings our hotplug handling in line with
what other
Make sure that we probe for a display on detect regardless
of previous hotplug events. Don't handle connector
hotplug state ourselves, but let DRM do the right thing
for us. This brings our hotplug handling in line with
what other DRM drivers do.
Signed-off-by: Lucas Stach l.st...@pengutronix.de
