<html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi Rob, <div class="moz-cite-prefix">On 11/12/2015 07:10 AM, Rob Herring wrote: </div> <blockquote cite="mid:20151111231042.GA29893@rob-hp-laptop" type="cite"> <pre wrap="">On Fri, Oct 30, 2015 at 09:09:15AM +0800, Yakir Yang wrote: </pre> <blockquote type="cite"> <pre wrap="">Some edp screen do not have hpd signal, so we can't just return failed when hpd plug in detect failed. This is an hardware property, so we need add a devicetree property "analogix,need-force-hpd" to indicate this sutiation. Tested-by: Heiko Stuebner <a class="moz-txt-link-rfc2396E" href="mailto:heiko@sntech.de"><heiko@sntech.de></a> Tested-by: Javier Martinez Canillas <a class="moz-txt-link-rfc2396E" href="mailto:javier@osg.samsung.com"><javier@osg.samsung.com></a> Signed-off-by: Yakir Yang <a class="moz-txt-link-rfc2396E" href="mailto:ykk@rock-chips.com"><ykk@rock-chips.com></a> --- </pre> </blockquote> <pre wrap=""> I didn't find this one in v10. Did it get dropped?</pre> </blockquote> <meta http-equiv="content-type" content="text/html; charset=windows-1252"> You are in my 'to' list, but I haven't send the whole v10 out, most of them don't need update :) This series should be: ---- [v8 0/17 ...] |---- [v8 1/17 ...] |---- [v8 2/17 ...] |---- [v8 3/17 ...] |---- [...] |---- [v8 15/17 ...] |---- [v8 16/17 ...] |---- [v8 17/17 ...] | |---- [v9 10/17 ...] |---- [v9 15/17 ...] |---- We are here |---- [v9 09/17 ...] |---- [v10 09/17 ...] |---- Received an acked from you <blockquote cite="mid:20151111231042.GA29893@rob-hp-laptop" type="cite"> <blockquote type="cite"> <pre wrap="">Changes in v9: None Changes in v8: None Changes in v7: None Changes in v6: None Changes in v5: None Changes in v4: None Changes in v3: - Add "analogix,need-force-hpd" to indicate whether driver need foce hpd when hpd detect failed. Changes in v2: None .../bindings/display/bridge/analogix_dp.txt | 4 ++- .../bindings/display/exynos/exynos_dp.txt | 1 + .../display/rockchip/analogix_dp-rockchip.txt | 1 + drivers/gpu/drm/bridge/analogix/analogix_dp_core.c | 36 +++++++++++++++++++--- drivers/gpu/drm/bridge/analogix/analogix_dp_core.h | 2 ++ drivers/gpu/drm/bridge/analogix/analogix_dp_reg.c | 9 ++++++ 6 files changed, 47 insertions(+), 6 deletions(-) diff --git a/Documentation/devicetree/bindings/display/bridge/analogix_dp.txt b/Documentation/devicetree/bindings/display/bridge/analogix_dp.txt index 7659a7a..74f0e80 100644 --- a/Documentation/devicetree/bindings/display/bridge/analogix_dp.txt +++ b/Documentation/devicetree/bindings/display/bridge/analogix_dp.txt @@ -22,6 +22,9 @@ Required properties for dp-controller: from general PHY binding: Should be "dp". Optional properties for dp-controller: + -analogix,need-force-hpd: + Indicate driver need force hpd when hpd detect failed, this + is used for some eDP screen which don't have hpd signal. </pre> </blockquote> <pre wrap=""> This should be a generic property.</pre> </blockquote> This property would only need in some no-hpd case, it would be dropped if panel keep the hotplug signal, that's why I thought it should be optional. I thought if we put this a property to generic property, then we must need to define it in normal device node, not sure whether it is right :) Thanks, - Yakir <blockquote cite="mid:20151111231042.GA29893@rob-hp-laptop" type="cite"> <pre wrap=""> Rob </pre> </blockquote> </body> </html>