From: Rob Herring <robh@kernel.org>
To: Douglas Anderson <dianders@chromium.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>,
robdclark@chromium.org, Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org, David Airlie <airlied@linux.ie>,
devicetree@vger.kernel.org, swboyd@chromium.org,
linux-arm-msm@vger.kernel.org,
Steev Klimaszewski <steev@kali.org>,
eballetbo@gmail.com, Andy Gross <agross@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
drinkcat@chromium.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/3] dt-bindings: display: simple: Add the panel on sc7180-trogdor-pompom
Date: Thu, 25 Mar 2021 18:09:07 -0600 [thread overview]
Message-ID: <20210326000907.GA1965415@robh.at.kernel.org> (raw)
In-Reply-To: <20210316140707.RFC.1.I3a21995726282f1e9fcb70da5eb96f19ed96634f@changeid>
On Tue, Mar 16, 2021 at 02:08:19PM -0700, Douglas Anderson wrote:
> The sc7180-trogdor-pompom board might be attached to any number of a
> pile of eDP panels. At the moment I'm told that the list might include:
> - KD KD116N21-30NV-A010
> - KD KD116N09-30NH-A016
> - Starry 2081116HHD028001-51D
> - Sharp LQ116M1JW10
>
> It should be noted that while the EDID programmed in the first 3
> panels indicates that they should run with exactly the same timing (to
> keep things simple), the 4th panel not only needs different timing but
> has a different resolution.
>
> As is true in general with eDP panels, we can figure out which panel
> we have and all the info needed to drive its pixel clock by reading
> the EDID. However, we can do this only after we've powered the panel
> on. Powering on the panels requires following the timing diagram in
> each panel's datasheet which specifies delays between certain
> actions. This means that, while we can be quite dynamic about handling
> things we can't just totally skip out on describing the panel like we
> could do if it was connected to an external-facing DP port.
Is this a 'standard' eDP connector? AFAICT, there does seem to be
such a thing. I've said in the past I'd be okay with a edp-connector
node. If that needs just the "HPD absent delay" property, I think that
would be okay. It's just a never ending stream of new properties with
each new panel that I don't want to see.
Rob
next prev parent reply other threads:[~2021-03-26 0:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 21:08 [RFC PATCH 1/3] dt-bindings: display: simple: Add the panel on sc7180-trogdor-pompom Douglas Anderson
2021-03-16 21:08 ` [RFC PATCH 2/3] drm/panel: panel-simple: " Douglas Anderson
2021-03-16 21:08 ` [RFC PATCH 3/3] arm64: dts: qcom: Don't specify exactly what panel is on pompom Douglas Anderson
2021-03-17 23:27 ` [RFC PATCH 1/3] dt-bindings: display: simple: Add the panel on sc7180-trogdor-pompom Matthias Kaehlcke
2021-03-18 1:53 ` Rob Clark
2021-03-26 12:39 ` Thierry Reding
2021-03-26 15:18 ` Rob Clark
2021-03-26 15:24 ` Rob Clark
2021-03-26 17:00 ` Bjorn Andersson
2021-03-26 19:48 ` Rob Herring
2021-03-26 22:16 ` Rob Clark
2021-03-26 23:48 ` Rob Herring
2021-03-27 0:33 ` Rob Clark
2021-03-27 0:49 ` Rob Clark
2021-03-29 15:51 ` Doug Anderson
2021-03-29 16:07 ` Doug Anderson
2021-03-26 0:09 ` Rob Herring [this message]
2021-03-29 16:25 ` Doug Anderson
2021-04-22 22:08 ` Doug Anderson
2021-04-23 11:14 ` Thierry Reding
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=20210326000907.GA1965415@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=airlied@linux.ie \
--cc=bjorn.andersson@linaro.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=drinkcat@chromium.org \
--cc=eballetbo@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@chromium.org \
--cc=sam@ravnborg.org \
--cc=steev@kali.org \
--cc=swboyd@chromium.org \
--cc=thierry.reding@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).