From: Keith Packard <keithp@keithp.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, linaro-dev@lists.linaro.org,
"Clark\, Rob" <rob@ti.com>, Archit Taneja <archit@ti.com>
Subject: Re: Proposal for a low-level Linux display framework
Date: Sun, 18 Sep 2011 23:53:27 -0700 [thread overview]
Message-ID: <yunfwjtauqg.fsf@aiko.keithp.com> (raw)
In-Reply-To: <1316414014.1978.12.camel@deskari>
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
On Mon, 19 Sep 2011 09:33:34 +0300, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
> I think it's a bit more complex than that. True, there are MIPI
> standards, for the video there are DPI, DBI, DSI, and for the commands
> there is DCS. And, as you mentioned, many panels need custom
> initialization, or support only parts of the DCS, or have other
> quirks.
So DSI is more like i2c than the DisplayPort aux channel or DDC. That
seems fine; you can create a DSI infrastructure like the i2c
infrastructure and then just have your display drivers use it to talk to
the panel. We might eventually end up with some shared DRM code to deal
with common DSI functions for display devices, like the EDID code
today, but that doesn't need to happen before you can write your first
DSI-using display driver.
--
keith.packard@intel.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2011-09-19 6:53 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 12:07 Proposal for a low-level Linux display framework Tomi Valkeinen
2011-09-15 14:59 ` Keith Packard
2011-09-15 15:29 ` Tomi Valkeinen
2011-09-15 15:50 ` Keith Packard
2011-09-15 17:05 ` Alan Cox
2011-09-17 21:36 ` Laurent Pinchart
2011-09-15 17:12 ` Florian Tobias Schandinat
2011-09-15 17:18 ` Alan Cox
2011-09-15 17:47 ` Florian Tobias Schandinat
2011-09-15 19:05 ` Alan Cox
2011-09-15 19:46 ` Florian Tobias Schandinat
2011-09-15 21:31 ` Alan Cox
2011-09-15 17:52 ` Alex Deucher
2011-09-15 17:56 ` Geert Uytterhoeven
2011-09-15 18:04 ` Alex Deucher
2011-09-15 18:39 ` Florian Tobias Schandinat
2011-09-15 18:58 ` Alan Cox
2011-09-15 19:18 ` Florian Tobias Schandinat
2011-09-15 19:28 ` Alan Cox
2011-09-15 19:45 ` Alex Deucher
2011-09-17 14:44 ` Felipe Contreras
2011-09-17 15:16 ` Rob Clark
2011-09-17 16:11 ` Florian Tobias Schandinat
2011-09-17 16:47 ` Dave Airlie
2011-09-17 18:15 ` Florian Tobias Schandinat
2011-09-17 18:23 ` Dave Airlie
2011-09-17 19:06 ` Florian Tobias Schandinat
2011-09-17 19:25 ` Corbin Simpson
2011-09-17 21:25 ` Alex Deucher
2011-09-17 20:25 ` Alan Cox
2011-10-31 20:24 ` Jesse Barnes
2011-09-17 16:50 ` Rob Clark
2011-09-16 4:53 ` Keith Packard
2011-09-17 23:12 ` Laurent Pinchart
2011-09-18 16:14 ` Rob Clark
2011-09-18 21:55 ` Laurent Pinchart
2011-09-18 22:23 ` Alan Cox
2011-09-19 0:09 ` Rob Clark
2011-09-20 23:32 ` Laurent Pinchart
2011-09-15 18:12 ` Keith Packard
2011-10-01 17:30 ` Enrico Weigelt
2011-09-15 17:21 ` Tomi Valkeinen
2011-09-15 18:32 ` Rob Clark
2011-09-16 0:55 ` Keith Packard
2011-09-16 6:38 ` Tomi Valkeinen
2011-09-16 14:17 ` Daniel Vetter
2011-09-16 16:53 ` Alan Cox
2011-09-19 6:33 ` Tomi Valkeinen
2011-09-19 6:53 ` Keith Packard [this message]
2011-09-19 7:29 ` Tomi Valkeinen
2011-09-20 8:29 ` Patrik Jakobsson
2011-09-20 15:55 ` Keith Packard
2011-09-20 21:20 ` Patrik Jakobsson
2011-09-21 6:01 ` Tomi Valkeinen
2011-09-21 18:07 ` Patrik Jakobsson
2011-10-01 17:34 ` Enrico Weigelt
2011-09-15 15:03 ` Kyungmin Park
2011-09-21 13:26 ` Heiko Stübner
2011-10-01 16:52 ` Enrico Weigelt
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=yunfwjtauqg.fsf@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=archit@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@ti.com \
--cc=tomi.valkeinen@ti.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