@@ -2205,6 +2205,15 @@ static const struct panel_desc hitachi_tx23d38vm0caa = {
},
};
+static const struct panel_desc google_pompom_panel = {
+ .delay = {
+ .hpd_absent_delay = 200,
+ .enable = 200,
+ .unprepare = 500,
+ },
+ .connector_type = DRM_MODE_CONNECTOR_eDP,
+};
+
static const struct drm_display_mode innolux_at043tn24_mode = {
.clock = 9000,
.hdisplay = 480,
@@ -4265,6 +4274,9 @@ static const struct of_device_id platform_of_match[] = {
}, {
.compatible = "hit,tx23d38vm0caa",
.data = &hitachi_tx23d38vm0caa
+ }, {
+ .compatible = "google,pompom-panel",
+ .data = &google_pompom_panel,
}, {
.compatible = "innolux,at043tn24",
.data = &innolux_at043tn24,
This adds an entry to simple panel for the timings of a panel that might be attached to the board sc7180-trogdor-pompom. As talked about in the previous patch ("dt-bindings: display: simple: Add the panel on sc7180-trogdor-pompom") any number of panels might be attached. These panels might have different timings or even different resolutions. When we see a pompom panel we'll use some conservative power sequence timings that can work with any of the panels that will be attached. All the rest of the details about the panel can be found by read its EDID. NOTE: if we wanted to optimize things a bit we could figure out which of the panels was actually attached and perhaps reduce some of the timings by a tiny bit if it was a panel that we recognized. I won't attempt this right now but it could be a nice future optimization, epsecially getting rid of the 200 ms "enable delay" imposed by the Starry panel. Signed-off-by: Douglas Anderson <dianders@chromium.org> --- For overall discussion about the idea of defining a generic panel at the board level, please respond in the bindings patch so we can keep all discussion in one place. drivers/gpu/drm/panel/panel-simple.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)