On Thu, Jun 27, 2019 at 12:19:27AM +0200, Heiko Stuebner wrote: > Hi Matthias, > > Am Mittwoch, 26. Juni 2019, 00:26:28 CEST schrieb Matthias Kaehlcke: > > The chromebook .dtsi file contains common settings for veyron > > Chromebooks with eDP displays. Some veyron devices with a display > > aren't Chromebooks (e.g. 'tiger' aka 'AOpen Chromebase Mini'), move > > display related bits from the chromebook .dtsi into a separate file > > to avoid redundant DT settings. > > > > The new file is included from the chromebook .dtsi and can be > > included by non-Chromebook devices with a display. > > > > Signed-off-by: Matthias Kaehlcke <mka@xxxxxxxxxxxx> > > --- > > This series is based on v5.3-armsoc/dts32 (f497ab6b4bb8 "ARM: > > dts: rockchip: Configure BT_HOST_WAKE as wake-up signal on > > veyron") plus the display timing patches from Doug: > > the display-timing patches are still stuck on panel-review. > > But while we wait for that to get resolved, you could also check if > the veyron panels could use Enric's fanzy new automatic calculation > of brightness-leves in the pwm-backlight driver, so that we possibly > could get rid of the long table of levels. We could get rid of the tables after "backlight: pwm_bl: Fix heuristic to determine number of brightness levels" (https://lore.kernel.org/patchwork/patch/1087809/) lands. Ideally we would also have something like this series https://lore.kernel.org/patchwork/project/lkml/list/?series=399607 , to provide userspace information about the brightness scale. Currently Chrome OS would interpret Enric's table as being linear and adjust the brightness slider incorrectly. _______________________________________________ Linux-rockchip mailing list Linux-rockchip@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/linux-rockchip
