[PATCH 3/4] drm: bridge/dw-hdmi: detect initial connector state

2016-03-02 Thread Thierry Reding
On Fri, Jan 08, 2016 at 10:02:06AM +0100, Philipp Zabel wrote: > Allow userspace to read the initial connector state via sysfs without > having to issue a detect manually. There is no reason to keep the state > unknown during initialization. > > Signed-off-by: Philipp Zabel > --- > drivers/gpu/d

[PATCH 3/4] drm: bridge/dw-hdmi: detect initial connector state

2016-01-08 Thread Philipp Zabel
Am Freitag, den 08.01.2016, 11:24 + schrieb Russell King - ARM Linux: > On Fri, Jan 08, 2016 at 10:02:06AM +0100, Philipp Zabel wrote: > > Allow userspace to read the initial connector state via sysfs without > > having to issue a detect manually. There is no reason to keep the state > > unknow

[PATCH 3/4] drm: bridge/dw-hdmi: detect initial connector state

2016-01-08 Thread Russell King - ARM Linux
On Fri, Jan 08, 2016 at 10:02:06AM +0100, Philipp Zabel wrote: > Allow userspace to read the initial connector state via sysfs without > having to issue a detect manually. There is no reason to keep the state > unknown during initialization. Can you describe how it can be unknown? I've always see

[PATCH 3/4] drm: bridge/dw-hdmi: detect initial connector state

2016-01-08 Thread Philipp Zabel
Allow userspace to read the initial connector state via sysfs without having to issue a detect manually. There is no reason to keep the state unknown during initialization. Signed-off-by: Philipp Zabel --- drivers/gpu/drm/bridge/dw-hdmi.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/dri