From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757930AbbICV4W (ORCPT ); Thu, 3 Sep 2015 17:56:22 -0400 Received: from mail-yk0-f176.google.com ([209.85.160.176]:36383 "EHLO mail-yk0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751505AbbICV4T (ORCPT ); Thu, 3 Sep 2015 17:56:19 -0400 MIME-Version: 1.0 In-Reply-To: <20150903084735.GB3784@ulmo.nvidia.com> References: <1441086371-24838-1-git-send-email-ykk@rock-chips.com> <1441088079-25809-1-git-send-email-ykk@rock-chips.com> <20150903084735.GB3784@ulmo.nvidia.com> From: Rob Herring Date: Thu, 3 Sep 2015 16:55:59 -0500 Message-ID: Subject: Re: [PATCH v4 14/16] drm: bridge: analogix/dp: try force hpd after plug in lookup failed To: Thierry Reding Cc: Yakir Yang , Heiko Stuebner , Jingoo Han , Inki Dae , Joe Perches , Kukjin Kim , Krzysztof Kozlowski , Mark Yao , Russell King , djkurtz@chromium.com, dianders@chromium.com, seanpaul@chromium.com, Ajay kumar , Andrzej Hajda , Kyungmin Park , David Airlie , Gustavo Padovan , Andy Yan , Kumar Gala , Ian Campbell , Rob Herring , Pawel Moll , Kishon Vijay Abraham I , architt@codeaurora.org, dri-devel , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-samsung-soc@vger.kernel.org" , linux-rockchip@lists.infradead.org, "linux-arm-kernel@lists.infradead.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 3, 2015 at 3:47 AM, Thierry Reding wrote: > On Wed, Sep 02, 2015 at 03:17:57PM -0500, Rob Herring wrote: > [...] >> Are there any eDP panels which don't have EDID and need panel details in DT? > > Most panels need information other than EDID. They typically have some > requirements regarding the power up sequence that aren't to be found > anywhere in EDID or detectable by some other mechanism. A decision was > therefore made a long time ago to require panels to be listed in DT with > a specific compatible string. That way all of these details can be > stashed away in drivers that know how to deal with these kinds of > details. I guess I was being hopeful that eDP was improving that situation. Rob From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Herring Subject: Re: [PATCH v4 14/16] drm: bridge: analogix/dp: try force hpd after plug in lookup failed Date: Thu, 3 Sep 2015 16:55:59 -0500 Message-ID: References: <1441086371-24838-1-git-send-email-ykk@rock-chips.com> <1441088079-25809-1-git-send-email-ykk@rock-chips.com> <20150903084735.GB3784@ulmo.nvidia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <20150903084735.GB3784@ulmo.nvidia.com> Sender: linux-samsung-soc-owner@vger.kernel.org To: Thierry Reding Cc: Yakir Yang , Heiko Stuebner , Jingoo Han , Inki Dae , Joe Perches , Kukjin Kim , Krzysztof Kozlowski , Mark Yao , Russell King , djkurtz@chromium.com, dianders@chromium.com, seanpaul@chromium.com, Ajay kumar , Andrzej Hajda , Kyungmin Park , David Airlie , Gustavo Padovan , Andy Yan , Kumar Gala , Ian Campbell , Rob Herring , Pawel Moll , Kishon Vijay Abraham I , architt@codeaurora.org, dri-devel List-Id: devicetree@vger.kernel.org On Thu, Sep 3, 2015 at 3:47 AM, Thierry Reding wrote: > On Wed, Sep 02, 2015 at 03:17:57PM -0500, Rob Herring wrote: > [...] >> Are there any eDP panels which don't have EDID and need panel details in DT? > > Most panels need information other than EDID. They typically have some > requirements regarding the power up sequence that aren't to be found > anywhere in EDID or detectable by some other mechanism. A decision was > therefore made a long time ago to require panels to be listed in DT with > a specific compatible string. That way all of these details can be > stashed away in drivers that know how to deal with these kinds of > details. I guess I was being hopeful that eDP was improving that situation. Rob From mboxrd@z Thu Jan 1 00:00:00 1970 From: robherring2@gmail.com (Rob Herring) Date: Thu, 3 Sep 2015 16:55:59 -0500 Subject: [PATCH v4 14/16] drm: bridge: analogix/dp: try force hpd after plug in lookup failed In-Reply-To: <20150903084735.GB3784@ulmo.nvidia.com> References: <1441086371-24838-1-git-send-email-ykk@rock-chips.com> <1441088079-25809-1-git-send-email-ykk@rock-chips.com> <20150903084735.GB3784@ulmo.nvidia.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, Sep 3, 2015 at 3:47 AM, Thierry Reding wrote: > On Wed, Sep 02, 2015 at 03:17:57PM -0500, Rob Herring wrote: > [...] >> Are there any eDP panels which don't have EDID and need panel details in DT? > > Most panels need information other than EDID. They typically have some > requirements regarding the power up sequence that aren't to be found > anywhere in EDID or detectable by some other mechanism. A decision was > therefore made a long time ago to require panels to be listed in DT with > a specific compatible string. That way all of these details can be > stashed away in drivers that know how to deal with these kinds of > details. I guess I was being hopeful that eDP was improving that situation. Rob