From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "Cousson, Benoit" <b-cousson@ti.com>
Cc: Archit Taneja <a0393947@ti.com>,
linux-omap@vger.kernel.org, linux@arm.linux.org.uk,
linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v2] OMAPDSS: HACK: Ensure DSS clock domain gets out of idle when HDMI is enabled
Date: Wed, 15 Feb 2012 12:51:57 +0000 [thread overview]
Message-ID: <1329310317.1892.60.camel@deskari> (raw)
In-Reply-To: <4F3BA6A2.60604@ti.com>
[-- Attachment #1: Type: text/plain, Size: 759 bytes --]
On Wed, 2012-02-15 at 13:35 +0100, Cousson, Benoit wrote:
> I think that changing the device creation to change the dev->parent
> should be pretty straightforward.
That's not possible with the current kernel, right?
We are now using omap_device_build() (in arch/arm/mach-omap2/display.c)
to build the dss devices. Looking at the omap_device.c, the parent will
always forcibly set to omap_device_parent. It'd be nice to be able to
construct the device child-parent relationship the same way with both DT
and non-DT cases.
Or can I create only the dss_core with omap_device_build(), and create
the rest normally with platform device functions, and make dss_core the
parent of the rest? But are the hwmods then handled correctly?
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-15 12:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 6:27 [PATCH v2] OMAPDSS: HACK: Ensure DSS clock domain gets out of idle when HDMI is enabled Archit Taneja
2012-02-14 11:57 ` Tomi Valkeinen
2012-02-14 12:58 ` Cousson, Benoit
2012-02-14 13:15 ` Tomi Valkeinen
2012-02-14 13:42 ` Archit Taneja
2012-02-14 13:33 ` Tomi Valkeinen
2012-02-14 13:57 ` Archit Taneja
2012-02-14 16:02 ` Cousson, Benoit
2012-02-14 16:59 ` Shilimkar, Santosh
2012-02-14 19:54 ` Archit Taneja
2012-02-14 15:41 ` Cousson, Benoit
2012-02-15 12:13 ` Archit Taneja
2012-02-15 12:35 ` Cousson, Benoit
2012-02-15 12:51 ` Tomi Valkeinen [this message]
2012-02-15 13:04 ` Cousson, Benoit
2012-02-15 19:59 ` Kevin Hilman
2012-02-16 8:22 ` Tomi Valkeinen
2012-02-16 10:16 ` Cousson, Benoit
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=1329310317.1892.60.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=a0393947@ti.com \
--cc=b-cousson@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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).