From: Sam Ravnborg <sam@ravnborg.org>
To: Josef Lusticky <josef@lusticky.cz>, Daniel Vetter <daniel@ffwll.ch>
Cc: devicetree@vger.kernel.org, airlied@linux.ie,
dri-devel@lists.freedesktop.org, thierry.reding@gmail.com
Subject: Controllers with several interface options - one or more drivers?
Date: Fri, 26 Jul 2019 14:25:10 +0200 [thread overview]
Message-ID: <20190726122510.GA14341@ravnborg.org> (raw)
In-Reply-To: <20190708145618.26031-1-josef@lusticky.cz>
Hi Josef, Daniel et al.
The driver that triggered this reply is a driver that adds parallel
support to ili9341 in a dedicated panel driver.
The issue here is that we already have a tiny driver that supports the
ili9341 controller - but with a slightly different configuration.
The ili9341 supports several interfaces - from the datasheet:
"ILI9341 supports parallel 8-/9-/16-/18-bit data bus
MCU interface, 6-/16-/18-bit data bus RGB interface and
3-/4-line serial peripheral interface (SPI)"
Noralf - in another mail explained:
"
The MIPI Alliance has lots of standards some wrt. display controller
interfaces:
- MIPI DBI - Display Bus Interface (used for commands and optionally pixels)
- MIPI DPI - Display Pixel Interface (also called RGB interface or
DOTCLK interface)
- MIPI DSI - Display Serial Interface (commands and pixels)
The ili9341 supports both MIPI DBI and DPI.
"
MIPI DPI - is a good fit for a drm_panel driver.
MIPI DBI - requires a full display controller driver.
There are many other examples of driver SoC that in the same way
can be seen only as a panel or as a full display controller driver.
The open question here is if we should try to support both cases in the
same driver / file. Or shall we implment two different drivers.
One for the panel use-case. And one for the display controller usecase?
Not sure - so asking for feedback.
Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-07-26 12:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 12:50 [RFC PATCH 0/2] Add DRM panel driver for Ilitek ILI9341 based panels in parallel RGB mode Josef Lusticky
2019-03-04 12:50 ` [RFC PATCH 1/2] drm/panel: Add Ilitek ILI9341 parallel RGB panel driver Josef Lusticky
2019-03-27 21:00 ` Rob Herring
2019-03-04 12:50 ` [RFC PATCH 2/2] dt-bindings: panel: Add Ilitek ILI9341 panel documentation Josef Lusticky
2019-03-27 20:55 ` Rob Herring
2019-07-08 14:56 ` [PATCH v2 0/2] Add DRM ILI9341 parallel RGB panel driver Josef Lusticky
2019-07-08 14:56 ` [PATCH v2 1/2] dt-bindings: panel: Add parallel RGB mode for Ilitek ILI9341 panels Josef Lusticky
2019-07-10 13:39 ` Sam Ravnborg
2019-07-24 19:57 ` Rob Herring
2019-07-26 5:56 ` Josef Luštický
2019-07-08 14:56 ` [PATCH v2 2/2] drm/panel: Add Ilitek ILI9341 parallel RGB panel driver Josef Lusticky
2019-07-10 13:47 ` Sam Ravnborg
2019-07-12 9:53 ` Josef Luštický
2019-07-10 13:51 ` [PATCH v2 0/2] Add DRM " Sam Ravnborg
2019-07-26 12:25 ` Sam Ravnborg [this message]
2019-07-26 14:55 ` Controllers with several interface options - one or more drivers? Daniel Vetter
2019-07-26 15:06 ` Daniel Vetter
2019-07-26 16:14 ` Sam Ravnborg
2019-07-29 7:19 ` Josef Luštický
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=20190726122510.GA14341@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=josef@lusticky.cz \
--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).