[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3703486.dL69t9P4Cl@diego>
Date: Thu, 11 Jul 2019 23:52:58 +0200
From: Heiko Stübner <heiko@...ech.de>
To: Douglas Anderson <dianders@...omium.org>
Cc: Thierry Reding <thierry.reding@...il.com>,
Sean Paul <seanpaul@...omium.org>,
linux-rockchip@...ts.infradead.org,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
dri-devel@...ts.freedesktop.org,
Boris Brezillon <boris.brezillon@...labora.com>,
Ezequiel Garcia <ezequiel@...labora.com>,
Enric Balletbò <enric.balletbo@...labora.com>,
Rob Herring <robh+dt@...nel.org>, mka@...omium.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Mark Rutland <mark.rutland@....com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v5 6/7] ARM: dts: rockchip: Specify rk3288-veyron-chromebook's display timings
Am Donnerstag, 11. Juli 2019, 23:27:44 CEST schrieb Heiko Stübner:
> Am Montag, 1. April 2019, 19:17:23 CEST schrieb Douglas Anderson:
> > Let's document the display timings that most veyron chromebooks (like
> > jaq, jerry, mighty, speedy) have been using out in the field. This
> > uses the standard blankings but a slightly slower clock rate, thus
> > getting a refresh rate 58.3 Hz.
> >
> > NOTE: this won't really do anything except cause DRM to properly
> > report the refresh rate since vop_crtc_mode_fixup() was rounding the
> > pixel clock to 74.25 MHz anyway. Apparently the adjusted rate isn't
> > exposed to userspace so it's important that the rate we're trying to
> > achieve is mostly right.
> >
> > For the downstream kernel change related to this see See
> > https://crrev.com/c/324558.
> >
> > NOTE: minnie uses a different panel will be fixed up in a future
> > patch, so for now we'll just delete the panel timings there.
> >
> > Signed-off-by: Douglas Anderson <dianders@...omium.org>
>
> applied for 5.3
5.4 obviously
[just to not confuse people reading that later]
Powered by blists - more mailing lists