public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Igor Stoppa <igor.stoppa@nokia.com>
To: ext Paul Walmsley <paul@pwsan.com>
Cc: Tomi Valkeinen <tomi.valkeinen@nokia.com>,
	linux-omap@vger.kernel.org, khilman@deeprootsystems.com
Subject: Re: Bug in linux omap clock framework?
Date: Wed, 10 Dec 2008 05:04:41 +0200	[thread overview]
Message-ID: <1228878281.3405.7.camel@localhost> (raw)
In-Reply-To: <alpine.DEB.2.00.0812091612240.5902@utopia.booyaka.com>

Hi Paul,
On Tue, 2008-12-09 at 16:14 -0700, ext Paul Walmsley wrote:
> Hi Tomi,
> 
> On Tue, 9 Dec 2008, Tomi Valkeinen wrote:
> 
> > I don't know much about power and clock domains, but I believe I found
> > the reason and fix for this. At least this should point to the right
> > direction.
> > 
> > It looks to me that when I do clk_enable() to a clock which is inside a
> > turned off powerdomain, clk_enable() function will return before the
> > powerdomain is fully turned on. Reading PM_PWSTST_DSS shows that the
> > powerdomain is still in transition state.
> > 
> > The following change waits until the powerdomain has finished the
> > transition. At least it fixed the problem for me, and other things seem
> > to be still working =).
> 
> Nice work - this makes sense.  Tested your patch here also. 

Just a thought:
wouldn't this feature be required in basically every similar case?

And if yes, wouldn't it be better to embed it into clk_enable() so that
the driver code doesn't have to address it explicitly and can be more
easily shared across different OMAP architectures?

-- 

Cheers, Igor

---

Igor Stoppa
Maemo Software - Nokia Devices R&D - Helsinki

  reply	other threads:[~2008-12-10  3:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05 14:49 Bug in linux omap clock framework? Tomi.Valkeinen
2008-12-05 18:23 ` Kevin Hilman
2008-12-08  7:59   ` Tomi Valkeinen
2008-12-06 23:51 ` Paul Walmsley
2008-12-08  8:59   ` Tomi Valkeinen
2008-12-08  9:24     ` Paul Walmsley
2008-12-08  9:36       ` Tomi Valkeinen
2008-12-09 13:58       ` Tomi Valkeinen
2008-12-09 23:14         ` Paul Walmsley
2008-12-10  3:04           ` Igor Stoppa [this message]
2008-12-10  7:02             ` Paul Walmsley
2008-12-10  7:37         ` Högander Jouni
2008-12-10  7:59           ` Tomi Valkeinen
2008-12-10  8:44             ` Högander Jouni
2008-12-10  8:57               ` Tomi Valkeinen
2008-12-10 10:44                 ` Högander Jouni
2008-12-10 11:53                   ` Tomi Valkeinen
2008-12-11  9:19         ` Högander Jouni
2008-12-11 16:17           ` Paul Walmsley
2008-12-12  7:48             ` Tomi Valkeinen
2008-12-09  9:15   ` Tomi Valkeinen

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=1228878281.3405.7.camel@localhost \
    --to=igor.stoppa@nokia.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=tomi.valkeinen@nokia.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