From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Tony Lindgren <tony@atomide.com>,
Liam Girdwood <lrg@slimlogic.co.uk>,
Archit Taneja <archit@ti.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/9] OMAP: DSS2: Change DSI platform device name from "omapdss_dsi1" to "omapdss_dsi"
Date: Tue, 10 May 2011 15:30:52 +0300 [thread overview]
Message-ID: <1305030652.2045.49.camel@deskari> (raw)
In-Reply-To: <20110509191912.GA6546@opensource.wolfsonmicro.com>
On Mon, 2011-05-09 at 21:19 +0200, Mark Brown wrote:
> On Mon, May 09, 2011 at 06:34:34PM +0300, Tomi Valkeinen wrote:
> > The second thing is that even if the power source for vdds_dsi may be
> > configured differently on different boards, the same vdds_dsi goes to
> > multiple DSS HW blocks inside OMAP, each represented by a separate
> > omap_device. So it'd be much nicer to configure just the vdds_dsi power
> > in the board file, but let the omap display code configure the
> > regulators properly for all the DSS HW blocks in that particular OMAP.
>
> For this I'd suggest setting up an arrangement with supplies where you
> have one thing on the OMAP is supplied by board configuration and then
> it has child supplies within the device but right now that's not so easy
> to do. I was just writing some stuff for that this afternoon but it'll
> be next week before I can test it properly.
This sounds just the thing we need here. Do you think there's a chance
the code could get merged in the next window? And I'm also happy to test
the code with omapdss, whenever you have something ready.
I think we'll go forward with this patch set in a modified form: we'll
leave the board files untouched and add the DSS driver parts (which is
99% of the patch set) with a small hack which makes things work with the
current device setup.
This means we won't be able to use the second DSI LCD yet, but getting
the biggest bulk of code in is more important.
Tomi
next prev parent reply other threads:[~2011-05-10 12:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 7:38 [PATCH 0/9] MAP: DSS2: DSI2 for secondary lcd panel on OMAP4 Archit Taneja
2011-05-04 7:38 ` [PATCH 1/9] OMAP: DSS2: Change DSI platform device name from "omapdss_dsi1" to "omapdss_dsi" Archit Taneja
2011-05-04 9:40 ` Tony Lindgren
2011-05-04 10:53 ` Tomi Valkeinen
2011-05-04 11:21 ` Tomi Valkeinen
2011-05-04 12:11 ` Archit Taneja
2011-05-04 12:17 ` Tony Lindgren
2011-05-05 11:36 ` Tomi Valkeinen
2011-05-05 11:50 ` Tony Lindgren
2011-05-05 11:58 ` Tomi Valkeinen
2011-05-05 13:03 ` Tomi Valkeinen
2011-05-05 13:02 ` Mark Brown
2011-05-09 15:34 ` Tomi Valkeinen
2011-05-09 19:19 ` Mark Brown
2011-05-10 12:30 ` Tomi Valkeinen [this message]
2011-05-10 13:47 ` Mark Brown
2011-05-11 9:23 ` Tomi Valkeinen
2011-05-11 12:12 ` Mark Brown
2011-06-07 11:44 ` Tomi Valkeinen
2011-06-07 12:08 ` Mark Brown
2011-06-07 13:11 ` Tomi Valkeinen
2011-06-13 9:54 ` Tomi Valkeinen
2011-06-13 13:27 ` Tony Lindgren
2011-05-04 7:38 ` [PATCH 2/9] OMAP: DSS2: DSI: Add extra omap_dss_device argument in functions exported by dsi Archit Taneja
2011-05-04 7:38 ` [PATCH 3/9] OMAP: DSS2: Remove omap_dss_device argument from dsi_pll_init() Archit Taneja
2011-05-04 7:38 ` [PATCH 4/9] OMAP: DSS2: Pass platform_device as an argument in dsi functions Archit Taneja
2011-05-04 7:38 ` [PATCH 5/9] OMAP: DSS2: DSI: Use platform_device pointer to get dsi data Archit Taneja
2011-05-04 7:38 ` [PATCH 6/9] OMAP: DSS2: DSI: Pass pointer to struct to packet_sent_handler isrs Archit Taneja
2011-05-04 7:38 ` [PATCH 7/9] OMAP4: DSS2: DSI: Changes for DSI2 on OMAP4 Archit Taneja
2011-05-04 7:38 ` [PATCH 8/9] OMAP: DSS2: DSI: Build a platform device instance for DSI2 Archit Taneja
2011-05-04 7:38 ` [PATCH 9/9] OMAP: DSS2: Taal: Use device name in backlight_device_register Archit Taneja
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=1305030652.2045.49.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=archit@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--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