LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Doug Anderson <email@example.com>
To: Rob Herring <firstname.lastname@example.org>
Cc: Daniel Vetter <email@example.com>,
Thierry Reding <firstname.lastname@example.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<email@example.com>, Sam Ravnborg <firstname.lastname@example.org>,
David Airlie <email@example.com>,
Linus W <firstname.lastname@example.org>,
Maxime Ripard <email@example.com>,
Steev Klimaszewski <firstname.lastname@example.org>,
Thomas Zimmermann <email@example.com>,
Rob Herring <firstname.lastname@example.org>,
Maarten Lankhorst <email@example.com>,
Bjorn Andersson <firstname.lastname@example.org>
Subject: Re: [PATCH v2 1/6] dt-bindings: drm/panel-simple: Introduce generic eDP panels
Date: Mon, 9 Aug 2021 15:20:43 -0700 [thread overview]
Message-ID: <CAD=FV=U63qGf+RTOe=X+BYK06OuJM5N5Vy6zcA8+7ka1CFLwcg@mail.gmail.com> (raw)
On Mon, Aug 2, 2021 at 6:39 AM Rob Herring <email@example.com> wrote:
> On Fri, 30 Jul 2021 14:26:20 -0700, Douglas Anderson wrote:
> > eDP panels generally contain almost everything needed to control them
> > in their EDID. This comes from their DP heritage were a computer needs
> > to be able to properly control pretty much any DP display that's
> > plugged into it.
> > The one big issue with eDP panels and the reason that we need a panel
> > driver for them is that the power sequencing can be different per
> > panel.
> > While it is true that eDP panel sequencing can be arbitrarily complex,
> > in practice it turns out that many eDP panels are compatible with just
> > some slightly different delays. See the contents of the bindings file
> > introduced in this patch for some details.
> > The fact that eDP panels are 99% probable and that the power
> > sequencing (especially power up) can be compatible between many panels
> > means that there's a constant desire to plug multiple different panels
> > into the same board. This could be for second sourcing purposes or to
> > support multiple SKUs (maybe a 11" and a 13", for instance).
> > As discussed , it should be OK to support this by adding two
> > properties to the device tree to specify the delays needed for
> > powering up the panel the first time. We'll create a new "edp-panel"
> > bindings file and define the two delays that might need to be
> > specified. NOTE: in the vast majority of the cases (HPD is hooked up
> > and isn't glitchy or is debounced) even these delays aren't needed.
> >  https://lore.kernel.org/r/CAD=FV=VZYOMPwQZzWdhJGh5cjJWw_EcM-wQVEivZ-bdGXjPrEQ@mail.gmail.com
> > Signed-off-by: Douglas Anderson <firstname.lastname@example.org>
> > ---
> > Changes in v2:
> > - No longer allow fallback to panel-simple.
> > - Add "-ms" suffix to delays.
> > .../bindings/display/panel/panel-edp.yaml | 188 ++++++++++++++++++
> > 1 file changed, 188 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/display/panel/panel-edp.yaml
> My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
> on your patch (DT_CHECKER_FLAGS is new in v5.13):
> yamllint warnings/errors:
> dtschema/dtc warnings/errors:
> /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/display/panel/panel-edp.example.dt.yaml: bridge@2d: 'aux-bus' does not match any of the regexes: 'pinctrl-[0-9]+'
> From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml
> \ndoc reference errors (make refcheckdocs):
> See https://patchwork.ozlabs.org/patch/1511822
> This check can fail if there are any dependencies. The base for a patch
> series is generally the most recent rc1.
I think it's a dependency problem. No hits here:
git grep aux-bus v5.14-rc5 -- Documentation/devicetree/bindings/
...but I get hits against "linuxnext". Rob: I'm hoping that this can
still be in your queue for review even with the bot warning. Thanks!
next prev parent reply other threads:[~2021-08-09 22:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 21:26 [PATCH v2 0/6] eDP: Support probing eDP panels dynamically instead of hardcoding Douglas Anderson
2021-07-30 21:26 ` [PATCH v2 1/6] dt-bindings: drm/panel-simple: Introduce generic eDP panels Douglas Anderson
2021-08-02 13:39 ` Rob Herring
2021-08-09 22:20 ` Doug Anderson [this message]
2021-08-09 22:56 ` Rob Herring
2021-07-30 21:26 ` [PATCH v2 2/6] drm/edid: Break out reading block 0 of the EDID Douglas Anderson
2021-07-30 21:26 ` [PATCH v2 3/6] drm/edid: Allow the querying/working with the panel ID from " Douglas Anderson
2021-07-30 21:26 ` [PATCH v2 4/6] drm/panel-simple: Don't re-read the EDID every time we power off the panel Douglas Anderson
2021-07-30 21:26 ` [PATCH v2 5/6] drm/panel-simple: Split the delay structure out of the panel description Douglas Anderson
2021-07-30 21:26 ` [PATCH v2 6/6] drm/panel-simple: Implement generic "edp-panel"s probed by EDID Douglas Anderson
[not found] ` <YQmp3mGpLW+ELxAC@ravnborg.org>
2021-08-09 22:18 ` [PATCH v2 0/6] eDP: Support probing eDP panels dynamically instead of hardcoding Doug Anderson
[not found] ` <YRTsFNTn/T8fLxyB@ravnborg.org>
2021-08-12 16:00 ` Doug Anderson
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--subject='Re: [PATCH v2 1/6] dt-bindings: drm/panel-simple: Introduce generic eDP panels' \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).