From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Archit Taneja <archit@ti.com>
Cc: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 06/15] OMAPDSS: remove all old panel drivers
Date: Thu, 29 Aug 2013 14:06:20 +0000 [thread overview]
Message-ID: <521F555C.8090802@ti.com> (raw)
In-Reply-To: <521F53F0.4030203@ti.com>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
Hi,
On 29/08/13 17:00, Archit Taneja wrote:
> On Thursday 29 August 2013 07:01 PM, Tomi Valkeinen wrote:
>> The board files now use the new panel drivers, making the old panel
>> drivers obsolete.
>>
>> Remove the old panel drivers, Kconfig and Makefile entries, and the
>> panels' platform data structs.
>
> Can we convert the picodlp driver to the new panel driver model, and
> report it as broken for now?
(please cut your quotes a bit, you just included some thousands of lines
of code there =).
We could, but I'm not sure what would be the point. The new picodlp
would be (more or less) totally new driver, so we would still end up
removing the old driver. We can as well add it later if we manage to get
it working.
The RFBI case is a bit different, as there we just changed the current
driver a bit and we didn't create a totally new one.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2013-08-29 14:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 13:31 [PATCH 00/15] OMAPDSS: remove old panel model code Tomi Valkeinen
2013-08-29 13:31 ` [PATCH 01/15] OMAPDSS: RFBI: Mark RFBI as broken Tomi Valkeinen
2013-08-29 13:31 ` [PATCH 02/15] OMAPDSS: remove omap_dss_device->channel field Tomi Valkeinen
2013-08-29 13:31 ` [PATCH 03/15] OMAPDSS: fix DPI and SDI device ids Tomi Valkeinen
2013-09-17 16:20 ` Tony Lindgren
2013-08-29 13:31 ` [PATCH 04/15] OMAPDSS: SDI: change regulator handling Tomi Valkeinen
2013-08-29 13:31 ` [PATCH 05/15] OMAPDSS: DPI: " Tomi Valkeinen
2013-08-29 13:31 ` [PATCH 07/15] OMAPDSS: DPI: remove code related to old panel model Tomi Valkeinen
2013-08-29 13:31 ` [PATCH 08/15] OMAPDSS: HDMI: " Tomi Valkeinen
2013-08-29 13:31 ` [PATCH 09/15] OMAPDSS: DSI: " Tomi Valkeinen
2013-08-29 13:31 ` [PATCH 10/15] OMAPDSS: SDI: " Tomi Valkeinen
2013-08-29 13:31 ` [PATCH 11/15] OMAPDSS: VENC: " Tomi Valkeinen
2013-08-29 13:31 ` [PATCH 12/15] OMAPDSS: RFBI: " Tomi Valkeinen
2013-08-29 13:31 ` [PATCH 13/15] OMAPDSS: DSS: remove legacy dss bus support Tomi Valkeinen
2013-08-29 14:44 ` Archit Taneja
2013-08-30 5:52 ` Tomi Valkeinen
2013-08-29 13:31 ` [PATCH 14/15] OMAPDSS: rename omap_dss_device's 'output' to 'src' Tomi Valkeinen
2013-08-29 13:32 ` [PATCH 15/15] OMAPDSS: rename omap_dss_device's 'device' field to 'dst' Tomi Valkeinen
[not found] ` <1377783120-14001-7-git-send-email-tomi.valkeinen@ti.com>
[not found] ` <521F53F0.4030203@ti.com>
2013-08-29 14:06 ` Tomi Valkeinen [this message]
2013-08-29 14:20 ` [PATCH 06/15] OMAPDSS: remove all old panel drivers Archit Taneja
2013-08-29 14:47 ` [PATCH 00/15] OMAPDSS: remove old panel model code Archit Taneja
2013-08-30 6:00 ` Tomi Valkeinen
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=521F555C.8090802@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=archit@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.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 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).