public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org,
	Archit Taneja <archit@ti.com>
Subject: Re: [PATCH 00/26] DSS device model change
Date: Wed, 27 Mar 2013 08:13:51 +0200	[thread overview]
Message-ID: <51528E1F.9080608@ti.com> (raw)
In-Reply-To: <20130326171006.GG25575@atomide.com>

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

On 2013-03-26 19:10, Tony Lindgren wrote:
> * Tomi Valkeinen <tomi.valkeinen@ti.com> [130326 06:38]:
>> Hi,
>>
>> To make it possible to add DT support to DSS, and later use the Common Display
>> Framework, we need to change the DSS device model. We currently have a custom
>> dss bus, and omap_dss_devices on that bus, and the aim is to get rid of that
>> bus.
>>
>> The panel devices will be converted occording to the control bus of the panel.
>> For many panels this means that the panel device will become a platform_device.
>> For some, it means the panel devices become i2c or spi devices.
>>
>> This series takes the first step toward that goal. This series:
>>
>> * Converts DPI, HDMI and DSI outputs to work with new style panels
>> * Converts TFP410, Taal and generic-dpi panels to new model
>> * Converts Panda, 4430SDP and Overo boards to use the new panels
>>
>> The non-converted outputs and panels still work, so they can be converted in
>> stages.
> 
> This is nice, it removes a merge dependency between ARM code and the driver :)

Yes. It does give me a few more gray hairs, though =). It'd be so much
easier to have all related changes in one clean patch series.

>> Note about board files: I only convert a few board files here for example. I
>> have a branch with board file changes for all the affected board files. I did
>> not include them as they are more or less identical. If this series looks good,
>> I will create an independent branch for the arch/arm stuff, so it can be pulled
>> separately.
> 
> Great looks good to me thanks.

To make the DSS work properly after this device model change, we also
need to solve the problem related to multiple display devices on the
same video bus.

Did the approach I suggested in

http://permalink.gmane.org/gmane.linux.ports.arm.omap/96039

look ok? Overo is the most complex one, I think the rest of the boards
that require changes have just LCD and DVI that conflict. But it still
means we'll have that kind of choice Kconfig option for all those boards.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]

  reply	other threads:[~2013-03-27  6:13 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 13:33 [PATCH 00/26] DSS device model change Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 01/26] OMAPDSS: only probe pdata if there's one Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 02/26] OMAPDSS: add omap_dss_find_output() Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 03/26] OMAPDSS: add omap_dss_find_output_by_node() Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 04/26] OMAPDSS: fix dss_get_ctx_loss_count for DT Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 05/26] OMAPDSS: DPI: fix regulators Tomi Valkeinen
2013-03-27  9:57   ` Archit Taneja
2013-03-26 13:33 ` [PATCH 06/26] OMAPDSS: SDI: " Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 07/26] OMAPDSS: add panel list Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 08/26] OMAPDSS: use the panel list in omap_dss_get_next_device Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 09/26] OMAPDSS: don't use dss bus in suspend/resume Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 10/26] OMAPDSS: implement display sysfs without dss bus Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 11/26] OMAPDSS: Add panel_dev pointer to dssdev Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 12/26] OMAPDSS: DPI: new panel registration Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 13/26] OMAPDSS: DSI: " Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 14/26] OMAPDSS: HDMI: " Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 15/26] OMAPDSS: TFP410 platform_data changes Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 16/26] OMAPDSS: TFP410: convert to platform device Tomi Valkeinen
2013-03-27 11:11   ` Archit Taneja
2013-03-27 11:14     ` Tomi Valkeinen
2013-03-27 11:17       ` Archit Taneja
2013-03-26 13:33 ` [PATCH 17/26] OMAPDSS: generic-dpi-panel platform_data changes Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 18/26] OMAPDSS: panel-generic-dpi: convert to platform device Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 19/26] OMAPDSS: HDMI: " Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 20/26] OMAPDSS: Taal platform_data changes Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 21/26] OMAPDSS: Taal: convert to platform device Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 22/26] ARM: OMAP: Panda: use new TFP410 platform driver Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 23/26] ARM: OMAP: Panda & SDP: use new HDMI driver Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 24/26] ARM: OMAP: 4430SDP: use new Taal driver Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 25/26] ARM: OMAP: Overo: use new TFP410 platform driver Tomi Valkeinen
2013-03-26 13:33 ` [PATCH 26/26] ARM: OMAP: Overo: use new generic-dpi-panel " Tomi Valkeinen
2013-03-26 17:10 ` [PATCH 00/26] DSS device model change Tony Lindgren
2013-03-27  6:13   ` Tomi Valkeinen [this message]
2013-03-27 20:25     ` Tony Lindgren

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=51528E1F.9080608@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=archit@ti.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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