All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>, linux-omap <linux-omap@vger.kernel.org>
Subject: Re: DSS pwrdm usecount, disabling autodeps for DSS
Date: Mon, 12 Mar 2012 09:24:16 -0700	[thread overview]
Message-ID: <87aa3l23f3.fsf@ti.com> (raw)
In-Reply-To: <1331542847.2097.4.camel@deskari> (Tomi Valkeinen's message of "Mon, 12 Mar 2012 11:00:47 +0200")

Tomi Valkeinen <tomi.valkeinen@ti.com> writes:

> On Fri, 2012-03-09 at 10:57 -0700, Paul Walmsley wrote:
>> On Fri, 9 Mar 2012, Tomi Valkeinen wrote:
>> 
>> > I didn't get very far with the patch =(. Tested on omap3 overo, with
>> > -rc6 based dss tree.
>> 
>> Thanks for testing and the .config.  Probably the best thing to do in the 
>> medium term is to fix the hwmod iclk handling; I think that will also fix 
>> the DSS autodeps problem.
>
> Btw, I don't know if it affects omap2/3, but I'm making a change with
> the dss hwmod devices so that the dss_core will be a parent device to
> all the other dss hwmod devices. This solves the mess on omap4, the
> modulemode bit, and the sequence in which the dss clocks need to be
> enabled, as dss_core will always be enabled first.
>
> This requires two patches for omap_device, "ARM: OMAP: remove
> omap_device_parent", "ARM: OMAP: omap_device: Expose omap_device_{alloc,
> delete, register}" which I hope are going in in the next merge window.

Yes, both are queued for 3.4.

Kevin

>
> So, it may not affect omap2/3 in any way, but just thought to mention.
>
>  Tomi

  reply	other threads:[~2012-03-12 16:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09  0:42 DSS pwrdm usecount, disabling autodeps for DSS Kevin Hilman
2012-03-09 11:08 ` Grazvydas Ignotas
2012-03-09 11:14 ` Tomi Valkeinen
2012-03-09 17:57   ` Paul Walmsley
2012-03-12  9:00     ` Tomi Valkeinen
2012-03-12 16:24       ` Kevin Hilman [this message]
2012-03-09 18:17   ` Kevin Hilman

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=87aa3l23f3.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=tomi.valkeinen@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.