[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190630205514.GA17046@ravnborg.org>
Date: Sun, 30 Jun 2019 22:55:14 +0200
From: Sam Ravnborg <sam@...nborg.org>
To: Douglas Anderson <dianders@...omium.org>
Cc: devicetree@...r.kernel.org, David Airlie <airlied@...ux.ie>,
Jeffy Chen <jeffy.chen@...k-chips.com>,
linux-kernel@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
linux-rockchip@...ts.infradead.org,
Thierry Reding <thierry.reding@...il.com>,
Sean Paul <seanpaul@...omium.org>,
dri-devel@...ts.freedesktop.org,
Boris Brezillon <boris.brezillon@...labora.com>,
Enric Balletbò <enric.balletbo@...labora.com>,
Stéphane Marchesin <marcheu@...omium.org>,
Ezequiel Garcia <ezequiel@...labora.com>, mka@...omium.org,
Laurent Pinchart <laurent.pinchart@...asonboard.com>
Subject: Re: [PATCH v5 2/7] drm/panel: simple: Add ability to override
typical timing
Hi Douglas.
> > +
> > + /* Only add timings if override was not there or failed to validate */
> > + if (num == 0 && panel->desc->num_timings)
> > + num = panel_simple_get_timings_modes(panel);
> > +
> > + /*
> > + * Only add fixed modes if timings/override added no mode.
>
> This part I fail to understand.
> If we have a panel where we in panel-simple have specified the timings,
> and done so using display_timing so with proper {min, typ, max} then it
> should be perfectly legal to specify a more precise variant in the DT
> file.
> Or what did I miss here?
Got it now.
If display_mode is used for timings this is what you call "fixed mode".
Hmm, if I got confused someone else may also be confused by this naming.
Sam
Powered by blists - more mailing lists