From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: "Noralf Trønnes" <noralf@tronnes.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Thierry Reding <thierry.reding@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/2] drm/panel: Add support for the Sitronix ST7789V
Date: Tue, 7 Feb 2017 16:34:44 +0100 [thread overview]
Message-ID: <20170207153444.yc7znfkje7hm4em6@lukather> (raw)
In-Reply-To: <a4634b34-ee70-449e-74c3-2ede4ea8c569@tronnes.org>
[-- Attachment #1: Type: text/plain, Size: 1769 bytes --]
On Mon, Feb 06, 2017 at 12:29:31PM +0100, Noralf Trønnes wrote:
>
> Den 06.02.2017 11.39, skrev Maxime Ripard:
> > Hi Noralf,
> >
> > On Fri, Feb 03, 2017 at 07:48:51PM +0100, Noralf Trønnes wrote:
> > > Den 03.02.2017 10.59, skrev Maxime Ripard:
> > > > Hi,
> > > >
> > > > Here is an attempt at supporting the ST7789V LCD controller from Sitronix.
> > > What happens if there's another panel driven by ST7789V that needs
> > > a different controller initialization?
> > You know those panels / controllers much better than I do, but why
> > would that be the case?
> >
> > > Maybe it's better to name it after the panel, not the controller.
> > I guess you could also use that panel directly without the controller?
>
> A controller can drive many different panels that can require different
> initializations. I faced that with staging/fbtft, when I wrote
> controller drivers having initialization code, and then came across
> displays with the same controller but with a different initialization.
>
> Trying to write controller drivers for these controllers is very
> difficult with all the possible permutations. On top of that we have
> those undocumented commands/registers.
>
> Some panels come with embedded controllers, in which case it makes
> sense to write a driver for the panel.
>
> But if the panel and controller are separate, then I don't know. Maybe
> the chance of coming across two uncompatible ST7789V and panel
> combinations in drm/panel is extremly low.
Hmm, I see. If we ever come across that case, I guess we could just
add new optional properties to override the current sequence.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-02-07 15:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 9:59 [PATCH 0/2] drm/panel: Add support for the Sitronix ST7789V Maxime Ripard
2017-02-03 9:59 ` [PATCH 1/2] dt-bindings: display: panel: Add bindings for the Sitronix ST7789V panel Maxime Ripard
2017-02-06 13:05 ` Thierry Reding
2017-02-07 15:44 ` Maxime Ripard
2017-02-07 16:42 ` Thierry Reding
2017-02-03 9:59 ` [PATCH 2/2] drm/panel: Add driver for sitronix " Maxime Ripard
2017-02-03 18:53 ` Noralf Trønnes
2017-02-06 10:50 ` Maxime Ripard
2017-02-06 12:13 ` Noralf Trønnes
2017-02-06 12:25 ` Thierry Reding
2017-02-06 13:26 ` Thierry Reding
2017-02-07 15:53 ` Maxime Ripard
2017-02-03 9:59 ` [PATCH v3 1/2] dt-bindings: gpu: Add Mali Utgard bindings Maxime Ripard
2017-02-03 9:59 ` [PATCH v3 2/2] ARM: sun8i: dt: Add mali node Maxime Ripard
2017-02-03 18:48 ` [PATCH 0/2] drm/panel: Add support for the Sitronix ST7789V Noralf Trønnes
2017-02-06 10:39 ` Maxime Ripard
2017-02-06 11:29 ` Noralf Trønnes
2017-02-07 15:34 ` Maxime Ripard [this message]
2017-02-07 16:46 ` Thierry Reding
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=20170207153444.yc7znfkje7hm4em6@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=noralf@tronnes.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).