diff options
| author | Douglas Anderson <dianders@chromium.org> | 2018-10-25 15:21:29 -0700 |
|---|---|---|
| committer | Sean Paul <seanpaul@chromium.org> | 2018-10-29 11:53:27 -0400 |
| commit | cb028e49129f352d2f2645727ceeeacdd64761f4 (patch) | |
| tree | a9c5ed70e6b72edca8505510f544fe6faab5643c /drivers/gpu/drm/panel | |
| parent | 922dceff8dc1fb4dafc9af78139ba65671408103 (diff) | |
| download | linux-stable-cb028e49129f352d2f2645727ceeeacdd64761f4.tar.gz linux-stable-cb028e49129f352d2f2645727ceeeacdd64761f4.tar.bz2 linux-stable-cb028e49129f352d2f2645727ceeeacdd64761f4.zip | |
dt-bindings: drm/panel: simple: Add no-hpd property
Some eDP panels that are designed to be always connected to a board
use their HPD signal to signal that they've finished powering on and
they're ready to be talked to.
However, for various reasons it's possible that the HPD signal from
the panel isn't actually hooked up. In the case where the HPD isn't
hooked up you can look at the timing diagram on the panel datasheet
and insert a delay for the maximum amount of time that the HPD might
take to come up.
Let's add a property in the device tree for this concept.
Reviewed-by: Sean Paul <sean@poorly.run>
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Signed-off-by: Sean Paul <seanpaul@chromium.org>
Link: https://patchwork.freedesktop.org/patch/msgid/20181025222134.174583-1-dianders@chromium.org
Diffstat (limited to 'drivers/gpu/drm/panel')
0 files changed, 0 insertions, 0 deletions