All of lore.kernel.org
 help / color / mirror / Atom feed
From: Archit Taneja <a0393947@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Benoit Cousson <b-cousson@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Rajendra Nayak <rnayak@ti.com>
Subject: Re: query about _setup() in omap_hwmod.c
Date: Fri, 13 Apr 2012 14:22:48 +0530	[thread overview]
Message-ID: <4F87E960.408@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1204130234220.25832@utopia.booyaka.com>

Hi,

On Friday 13 April 2012 02:09 PM, Paul Walmsley wrote:
> Hi Archit,
>
> On Fri, 13 Apr 2012, Archit Taneja wrote:
>
>> There were still some issues related to this, particularly on OMAP4, I have
>> posted a patch set to fix this just a while back.
>
> Was looking at those.  The first one, removing the OCPIF_SWSUP_IDLE flags,
> makes sense to me.  But as far as the second one goes, it would be nice if
> we could use interface clocks again for interfaces, rather than functional
> clocks.  That's the root cause of the problem... Looks like this was added
> in commit da7cdfac1b0c58d6863532dd3b432c3fbc034978.  Maybe this is needed
> because we don't properly enable parent hwmods before the dependent child
> hwmods?
>

Yes, you are right. As you and Benoit in the other thread explained, if 
we get the parent-child dependency right, we could switch back to using 
l3_div interface clock.

Thanks,
Archit

>
> - Paul
>


      reply	other threads:[~2012-04-13  8:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11  9:37 query about _setup() in omap_hwmod.c Archit Taneja
2012-04-13  8:09 ` Paul Walmsley
2012-04-13  8:21   ` Archit Taneja
2012-04-13  8:35     ` Cousson, Benoit
2012-04-13  8:39     ` Paul Walmsley
2012-04-13  8:52       ` Archit Taneja [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=4F87E960.408@ti.com \
    --to=a0393947@ti.com \
    --cc=b-cousson@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=rnayak@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.