From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tony Lindgren <tony@atomide.com>,
Igor Grinberg <grinberg@compulab.co.il>
Cc: linux-omap@vger.kernel.org, Archit Taneja <archit@ti.com>
Subject: Re: [PATCH 00/28] OMAP: DSS related board file changes
Date: Wed, 3 Apr 2013 12:36:58 +0300 [thread overview]
Message-ID: <515BF83A.7000108@ti.com> (raw)
In-Reply-To: <1364474962-20439-1-git-send-email-tomi.valkeinen@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1714 bytes --]
Hi,
On 2013-03-28 14:48, Tomi Valkeinen wrote:
> So here are the DSS related board file changes for 3.10.
>
> First there are a bunch of patches adding the Kconfig options so that only one
> display device is created for a single video bus. Only Overo had more than two
> displays on the same bus, but unfortunately there were multiple boards with a
> setup that puts an LCD and DVI output on the same video bus.
>
> So the ifdeffery is not very nice. But, as discussed, this is the best way
> forward, and should be seen as a temporary solution until we get full DT
> support.
>
> Then the rest are converting the old omap_dss_device style displays to platform
> devices. Only TFP410, generic-dpi-panel, HDMI and Taal drivers have been
> converted yet, but those seem to form the bulk of the display options used.
>
> This series can be found from:
> git://gitorious.org/linux-omap-dss2/linux.git 3.10-lo/1-arch-dss
>
> These patches depend on a few dss header file changes. These header file
> changes can be found from:
> git://gitorious.org/linux-omap-dss2/linux.git 3.10/0-dss-headers
>
> If this series is applied without the relevant omapdss changes, everything
> compiles and the boards boot, but the converted displays do not work. The same
> happens if only the omapdss changes are applied, but not this series.
>
> The related omapdss changes can be found from:
> git://gitorious.org/linux-omap-dss2/linux.git 3.10/3-dss-dev-model
I'll drop these patches and the branches mentioned above, as I don't
have a solution to the multiple-displays-per-output problem. I'll
continue looking at this, but it surely won't make into the next merge
window.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
prev parent reply other threads:[~2013-04-03 9:37 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 12:48 [PATCH 00/28] OMAP: DSS related board file changes Tomi Valkeinen
2013-03-28 12:48 ` [PATCH 01/28] ARM: OMAP: Remove unnecessary platform callbacks for VENC devices Tomi Valkeinen
2013-03-28 15:18 ` Igor Grinberg
2013-03-28 12:48 ` [PATCH 02/28] ARM: OMAP: don't use reset_gpio from omap4_panda_dvi_device Tomi Valkeinen
2013-03-28 12:48 ` [PATCH 03/28] ARM: OMAP: Overo: Kconfig option for the display options Tomi Valkeinen
2013-03-28 12:48 ` [PATCH 04/28] ARM: OMAP: 3430SDP: " Tomi Valkeinen
2013-03-28 12:48 ` [PATCH 05/28] ARM: OMAP: 4430SDP: " Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 06/28] ARM: OMAP: DEVKIT8000: " Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 07/28] ARM: OMAP: OMAP3EVM: " Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 08/28] ARM: OMAP: CM-T35: " Tomi Valkeinen
2013-03-28 16:09 ` Igor Grinberg
2013-03-28 16:53 ` Tony Lindgren
2013-03-28 17:12 ` Tomi Valkeinen
2013-03-28 21:28 ` Tony Lindgren
2013-03-29 4:27 ` Tomi Valkeinen
2013-03-29 15:47 ` Tony Lindgren
2013-03-28 17:02 ` Tomi Valkeinen
2013-03-31 9:17 ` Igor Grinberg
2013-04-02 8:07 ` Tomi Valkeinen
2013-04-02 11:20 ` Igor Grinberg
2013-03-28 12:49 ` [PATCH 09/28] ARM: OMAP: AM3517EVM: " Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 10/28] ARM: OMAP: Panda: use new TFP410 platform driver Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 11/28] ARM: OMAP: Panda & SDP: use new HDMI driver Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 12/28] ARM: OMAP: 4430SDP: use new Taal driver Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 13/28] ARM: OMAP: Beagle: use new TFP410 platform driver Tomi Valkeinen
2013-03-28 12:52 ` Peter Meerwald
2013-03-28 12:49 ` [PATCH 14/28] ARM: OMAP: Stalker: " Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 15/28] ARM: OMAP: OMAP3EVM: " Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 16/28] ARM: OMAP: IGEP0020: " Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 17/28] ARM: OMAP: Devkit8000: " Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 18/28] ARM: OMAP: CM-T35: " Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 19/28] ARM: OMAP: AM3517EVM: " Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 20/28] ARM: OMAP: 3430SDP: " Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 21/28] ARM: OMAP: Overo: " Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 22/28] ARM: OMAP: Overo: use new generic-dpi-panel " Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 23/28] ARM: OMAP: LDP: " Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 24/28] ARM: OMAP: H4: " Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 25/28] ARM: OMAP: Devkit8000: " Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 26/28] ARM: OMAP: CM-T35: " Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 27/28] ARM: OMAP: AM3517EVM: " Tomi Valkeinen
2013-03-28 12:49 ` [PATCH 28/28] ARM: OMAP: 2430SDP: " Tomi Valkeinen
2013-03-28 15:31 ` [PATCH 00/28] OMAP: DSS related board file changes Igor Grinberg
2013-03-28 16:48 ` Tomi Valkeinen
2013-03-28 16:57 ` Tony Lindgren
2013-03-31 8:41 ` Igor Grinberg
2013-03-31 8:39 ` Igor Grinberg
2013-03-31 15:03 ` Greg Kroah-Hartman
2013-04-02 8:01 ` Tomi Valkeinen
2013-04-02 8:40 ` Igor Grinberg
2013-04-03 9:36 ` Tomi Valkeinen [this message]
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=515BF83A.7000108@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=archit@ti.com \
--cc=grinberg@compulab.co.il \
--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