[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <165052560307.696645.16914083635478662154.b4-ty@cerno.tech>
Date: Thu, 21 Apr 2022 09:20:07 +0200
From: Maxime Ripard <maxime@...no.tech>
To: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Daniel Vetter <daniel@...ll.ch>,
Thierry Reding <thierry.reding@...il.com>,
David Airlie <airlied@...ux.ie>,
Thomas Zimmermann <tzimmermann@...e.de>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Paul Kocialkowski <paul.kocialkowski@...tlin.com>,
Maxime Ripard <mripard@...nel.org>,
Rob Clark <robdclark@...il.com>
Cc: Maxime Ripard <maxime@...no.tech>, linux-kernel@...r.kernel.org,
dri-devel@...ts.freedesktop.org
Subject: Re: (subset) [PATCH 1/2] Revert "drm: of: Properly try all possible cases for bridge/panel detection"
On Wed, 20 Apr 2022 16:12:29 -0700, Bjorn Andersson wrote:
> Commit '80253168dbfd ("drm: of: Lookup if child node has panel or
> bridge")' introduced the ability to describe a panel under a display
> controller without having to use a graph to connect the controller to
> its single child panel (or bridge).
>
> The implementation of this would find the first non-graph node and
> attempt to acquire the related panel or bridge. This prevents cases
> where any other child node, such as a aux bus for a DisplayPort
> controller, or an opp-table to find the referenced panel.
>
> [...]
Applied to drm/drm-misc (drm-misc-fixes).
Thanks!
Maxime
Powered by blists - more mailing lists