All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Douglas Anderson <dianders@chromium.org>
Cc: "Heiko Stuebner" <heiko@sntech.de>,
	"Sean Paul" <seanpaul@chromium.org>,
	linux-rockchip@lists.infradead.org,
	"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
	dri-devel@lists.freedesktop.org,
	"Boris Brezillon" <boris.brezillon@collabora.com>,
	"Ezequiel Garcia" <ezequiel@collabora.com>,
	"Enric Balletbò" <enric.balletbo@collabora.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	mka@chromium.org, "David Airlie" <airlied@linux.ie>,
	linux-kernel@vger.kernel.org, "Daniel Vetter" <daniel@ffwll.ch>
Subject: Re: [PATCH v5 4/7] drm/panel: simple: Use display_timing for Innolux n116bge
Date: Sat, 29 Jun 2019 01:50:28 +0200	[thread overview]
Message-ID: <20190628235028.GC1189@mithrandir> (raw)
In-Reply-To: <20190401171724.215780-5-dianders@chromium.org>

[-- Attachment #1: Type: text/plain, Size: 1939 bytes --]

On Mon, Apr 01, 2019 at 10:17:21AM -0700, Douglas Anderson wrote:
> Convert the Innolux n116bge from using a fixed mode to specifying a
> display timing with min/typ/max values.
> 
> Note that the n116bge's datasheet doesn't fit too well into DRM's way
> of specifying things.  Specifically the panel's datasheet just
> specifies the vertical blanking period and horizontal blanking period
> and doesn't break things out.  For now we'll leave everything as a
> fixed value but just allow adjusting the pixel clock.  I've added a
> comment on what the datasheet claims so someone could later expand
> things to fit their needs if they wanted to test other blanking
> periods.
> 
> The goal here is to be able to specify the panel timings in the device
> tree for several rk3288 Chromebooks (like rk3288-veryon-jerry).  These
> Chromebooks have all been running in the downstream kernel with the
> standard porches and sync lengths but just with a slightly slower
> pixel clock because the 76.42 MHz clock is not achievable from the
> fixed PLL that was available.  These Chromebooks only achieve a
> refresh rate of ~58 Hz.  While it's probable that we could adjust the
> timings to achieve 60 Hz it's probably wisest to match what's been
> running on these devices all these years.
> 
> I'll note that though the upstream kernel has always tried to achieve
> 76.42 MHz, it has actually been running at 74.25 MHz also since the
> video processor is parented off the same fixed PLL.
> 
> Changes in v4:
>  - display_timing for Innolux n116bge new for v4.
> 
> Changes in v5:
>  - Added Heiko's Tested-by
> 
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> Tested-by: Heiko Stuebner <heiko@sntech.de>
> ---
> 
>  drivers/gpu/drm/panel/panel-simple.c | 37 +++++++++++++++++-----------
>  1 file changed, 23 insertions(+), 14 deletions(-)

Acked-by: Thierry Reding <thierry.reding@gmail.com>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-06-28 23:50 UTC|newest]

Thread overview: 102+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 17:17 [PATCH v5 0/7] drm/panel: simple: Add mode support to devicetree Douglas Anderson
2019-04-01 17:17 ` Douglas Anderson
2019-04-01 17:17 ` Douglas Anderson
2019-04-01 17:17 ` [PATCH v5 1/7] dt-bindings: Add panel-timing subnode to simple-panel Douglas Anderson
2019-04-01 17:17   ` Douglas Anderson
2019-04-06  6:06   ` Rob Herring
2019-04-06  6:06     ` Rob Herring
2019-04-08  9:10   ` Boris Brezillon
2019-04-08 10:32   ` Thierry Reding
2019-04-08 14:39     ` Doug Anderson
2019-04-08 14:39       ` Doug Anderson
2019-05-20 18:35       ` Doug Anderson
2019-06-28 23:47   ` Thierry Reding
2019-06-28 23:47     ` Thierry Reding
2019-06-30 20:02   ` Sam Ravnborg
2019-06-30 20:02     ` Sam Ravnborg
2019-07-01 16:59     ` Doug Anderson
2019-07-01 16:59       ` Doug Anderson
     [not found] ` <20190401171724.215780-1-dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2019-04-01 17:17   ` [PATCH v5 2/7] drm/panel: simple: Add ability to override typical timing Douglas Anderson
2019-04-01 17:17     ` Douglas Anderson
2019-04-08  9:10     ` Boris Brezillon
2019-04-08  9:10       ` Boris Brezillon
2019-06-28 23:49     ` Thierry Reding
2019-06-28 23:49       ` Thierry Reding
2019-06-30 20:22     ` Sam Ravnborg
2019-06-30 20:22       ` Sam Ravnborg
2019-06-30 20:55       ` Sam Ravnborg
2019-06-30 20:55         ` Sam Ravnborg
2019-07-01 16:39         ` Doug Anderson
2019-07-08 17:56           ` Sam Ravnborg
2019-07-10 22:56             ` Doug Anderson
2019-07-11 19:16               ` Sean Paul
2019-07-11 19:16                 ` Sean Paul
2019-07-01 16:39       ` Doug Anderson
2019-07-08 17:50         ` Sam Ravnborg
2019-07-08 17:50           ` Sam Ravnborg
2019-07-10 22:39           ` Doug Anderson
2019-07-10 22:39             ` Doug Anderson
2019-07-11 19:38             ` Sam Ravnborg
2019-04-01 17:17 ` [PATCH v5 3/7] arm64: dts: rockchip: Specify override mode for kevin panel Douglas Anderson
2019-04-01 17:17   ` Douglas Anderson
2019-04-01 17:17   ` Douglas Anderson
2019-07-11 21:30   ` Heiko Stübner
2019-07-11 21:30     ` Heiko Stübner
2019-07-11 21:30     ` Heiko Stübner
2019-04-01 17:17 ` [PATCH v5 4/7] drm/panel: simple: Use display_timing for Innolux n116bge Douglas Anderson
2019-04-01 17:17   ` Douglas Anderson
2019-06-28 23:50   ` Thierry Reding [this message]
2019-04-01 17:17 ` [PATCH v5 5/7] drm/panel: simple: Use display_timing for AUO b101ean01 Douglas Anderson
2019-04-01 17:17   ` Douglas Anderson
2019-06-28 23:50   ` Thierry Reding
2019-04-01 17:17 ` [PATCH v5 6/7] ARM: dts: rockchip: Specify rk3288-veyron-chromebook's display timings Douglas Anderson
2019-04-01 17:17   ` Douglas Anderson
2019-04-01 17:17   ` Douglas Anderson
2019-04-07  1:15   ` Urja Rannikko
2019-04-07  1:15     ` Urja Rannikko
2019-04-08 15:21     ` Doug Anderson
2019-04-08 15:21       ` Doug Anderson
2019-04-08 16:26       ` Urja Rannikko
2019-04-08 16:26         ` Urja Rannikko
2019-04-13  0:07         ` Doug Anderson
2019-04-13  0:07           ` Doug Anderson
2019-04-13  0:07           ` Doug Anderson
2019-07-11 21:27   ` Heiko Stübner
2019-07-11 21:27     ` Heiko Stübner
2019-07-11 21:27     ` Heiko Stübner
2019-07-11 21:52     ` Heiko Stübner
2019-07-11 21:52       ` Heiko Stübner
2019-07-11 21:52       ` Heiko Stübner
2019-04-01 17:17 ` [PATCH v5 7/7] ARM: dts: rockchip: Specify rk3288-veyron-minnie's " Douglas Anderson
2019-04-01 17:17   ` Douglas Anderson
2019-04-01 17:17   ` Douglas Anderson
2019-07-11 21:28   ` Heiko Stübner
2019-07-11 21:28     ` Heiko Stübner
2019-07-11 21:28     ` Heiko Stübner
2019-06-14 10:39 ` [PATCH v5 0/7] drm/panel: simple: Add mode support to devicetree Heiko Stuebner
2019-06-14 10:39   ` Heiko Stuebner
2019-06-14 10:39   ` Heiko Stuebner
2019-06-26 13:00 ` Sam Ravnborg
2019-06-26 13:00   ` Sam Ravnborg
2019-06-26 13:00   ` Sam Ravnborg
2019-06-26 14:41   ` Doug Anderson
2019-06-26 14:41     ` Doug Anderson
2019-06-26 14:41     ` Doug Anderson
2019-06-28 15:55     ` Doug Anderson
2019-06-28 15:55       ` Doug Anderson
2019-06-28 15:55       ` Doug Anderson
2019-06-28 16:10       ` Rob Herring
2019-06-28 16:10         ` Rob Herring
2019-06-28 16:10         ` Rob Herring
2019-06-28 17:13       ` Sam Ravnborg
2019-06-28 17:13         ` Sam Ravnborg
2019-06-28 17:13         ` Sam Ravnborg
2019-06-29 14:09         ` Heiko Stübner
2019-06-29 14:09           ` Heiko Stübner
2019-06-29 14:09           ` Heiko Stübner
2019-07-08 15:58           ` Doug Anderson
2019-07-08 15:58             ` Doug Anderson
2019-07-08 15:58             ` Doug Anderson
2019-07-11 19:35             ` Sam Ravnborg
2019-07-11 19:35               ` Sam Ravnborg
2019-07-11 19:35               ` Sam Ravnborg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190628235028.GC1189@mithrandir \
    --to=thierry.reding@gmail.com \
    --cc=airlied@linux.ie \
    --cc=boris.brezillon@collabora.com \
    --cc=daniel@ffwll.ch \
    --cc=dianders@chromium.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=enric.balletbo@collabora.com \
    --cc=ezequiel@collabora.com \
    --cc=heiko@sntech.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mka@chromium.org \
    --cc=robh+dt@kernel.org \
    --cc=seanpaul@chromium.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.