From: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
To: Maxime Ripard <maxime@cerno.tech>
Cc: Jagan Teki <jagan@amarulasolutions.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Thierry Reding <thierry.reding@gmail.com>,
Rob Clark <robdclark@gmail.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Linus Walleij <linus.walleij@linaro.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Robert Foss <robert.foss@linaro.org>
Subject: Re: [PATCH 2/2] Revert "drm: of: Lookup if child node has panel or bridge"
Date: Tue, 26 Apr 2022 09:54:36 +0200 [thread overview]
Message-ID: <YmelPCcWCCjALtRU@aptenodytes> (raw)
In-Reply-To: <YmEdAVwZuA7Wo1Ch@aptenodytes>
[-- Attachment #1: Type: text/plain, Size: 2255 bytes --]
Hi,
On Thu 21 Apr 22, 10:59, Paul Kocialkowski wrote:
> Hi Maxime,
>
> On Thu 21 Apr 22, 10:23, Maxime Ripard wrote:
> > On Thu, Apr 21, 2022 at 01:15:54PM +0530, Jagan Teki wrote:
> > > + Linus
> > > + Marek
> > > + Laurent
> > > + Robert
> > >
> > > On Thu, Apr 21, 2022 at 4:40 AM Bjorn Andersson
> > > <bjorn.andersson@linaro.org> wrote:
> > > >
> > > > Commit '80253168dbfd ("drm: of: Lookup if child node has panel or
> > > > bridge")' attempted to simplify the case of expressing a simple panel
> > > > under a DSI controller, by assuming that the first non-graph child node
> > > > was a panel or bridge.
> > > >
> > > > Unfortunately for non-trivial cases the first child node might not be a
> > > > panel or bridge. Examples of this can be a aux-bus in the case of
> > > > DisplayPort, or an opp-table represented before the panel node.
> > > >
> > > > In these cases the reverted commit prevents the caller from ever finding
> > > > a reference to the panel.
> > > >
> > > > This reverts commit '80253168dbfd ("drm: of: Lookup if child node has
> > > > panel or bridge")', in favor of using an explicit graph reference to the
> > > > panel in the trivial case as well.
> > >
> > > This eventually breaks many child-based devm_drm_of_get_bridge
> > > switched drivers. Do you have any suggestions on how to proceed to
> > > succeed in those use cases as well?
> >
> > I guess we could create a new helper for those, like
> > devm_drm_of_get_bridge_with_panel, or something.
>
> Oh wow I feel stupid for not thinking about that.
>
> Yeah I agree that it seems like the best option.
Should I prepare a patch with such a new helper?
The idea would be to keep drm_of_find_panel_or_bridge only for the of graph
case and add one for the child node case, maybe:
drm_of_find_child_panel_or_bridge.
I really don't have a clear idea of which driver would need to be switched
over though. Could someone (Jagan?) let me know where it would be needed?
Are there cases where we could both expect of graph and child node?
(i.e. does the new helper also need to try via of graph?)
Thanks,
Paul
--
Paul Kocialkowski, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-04-26 7:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 23:12 [PATCH 1/2] Revert "drm: of: Properly try all possible cases for bridge/panel detection" Bjorn Andersson
2022-04-20 23:12 ` [PATCH 2/2] Revert "drm: of: Lookup if child node has panel or bridge" Bjorn Andersson
2022-04-21 7:20 ` (subset) " Maxime Ripard
2022-04-21 7:45 ` Jagan Teki
2022-04-21 8:23 ` Maxime Ripard
2022-04-21 8:59 ` Paul Kocialkowski
2022-04-26 7:54 ` Paul Kocialkowski [this message]
2022-04-26 8:10 ` Jagan Teki
2022-04-27 14:34 ` Maxime Ripard
2022-04-28 6:17 ` Marek Szyprowski
2022-04-28 8:25 ` Jagan Teki
2022-04-28 8:39 ` Jagan Teki
2022-04-28 22:17 ` Laurent Pinchart
2022-04-29 8:24 ` Jagan Teki
2022-04-29 15:46 ` Maxime Ripard
2022-04-29 16:05 ` Laurent Pinchart
2022-05-04 15:08 ` Maxime Ripard
2022-04-26 11:33 ` Laurent Pinchart
2022-04-26 12:41 ` Paul Kocialkowski
2022-04-26 12:54 ` Maxime Ripard
2022-04-26 12:55 ` Maxime Ripard
2022-04-26 13:04 ` Paul Kocialkowski
2022-04-26 13:19 ` Maxime Ripard
2022-04-26 13:50 ` Paul Kocialkowski
2022-04-26 21:10 ` Bjorn Andersson
2022-04-27 7:34 ` Paul Kocialkowski
2022-05-03 0:03 ` Bjorn Andersson
2022-04-26 12:58 ` Paul Kocialkowski
2022-04-27 13:10 ` Laurent Pinchart
2022-04-26 12:51 ` Maxime Ripard
2022-04-27 6:59 ` Jagan Teki
2022-04-27 11:52 ` Jagan Teki
2022-04-27 12:19 ` Paul Kocialkowski
2022-04-27 12:59 ` Jagan Teki
2022-04-27 13:10 ` Laurent Pinchart
2022-04-20 23:19 ` [PATCH 1/2] Revert "drm: of: Properly try all possible cases for bridge/panel detection" Bjorn Andersson
2022-04-21 7:13 ` Paul Kocialkowski
2022-04-21 7:26 ` Maxime Ripard
2022-04-22 7:58 ` Raphael Gallais-Pou
2022-04-21 7:11 ` Paul Kocialkowski
2022-04-21 7:20 ` (subset) " Maxime Ripard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YmelPCcWCCjALtRU@aptenodytes \
--to=paul.kocialkowski@bootlin.com \
--cc=airlied@linux.ie \
--cc=bjorn.andersson@linaro.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jagan@amarulasolutions.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maxime@cerno.tech \
--cc=robdclark@gmail.com \
--cc=robert.foss@linaro.org \
--cc=thierry.reding@gmail.com \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox