From: mturquette@ti.com (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: common clock framework
Date: Sun, 6 May 2012 16:49:58 -0700 [thread overview]
Message-ID: <20120506234958.GA14559@gmail.com> (raw)
In-Reply-To: <CAG9bXv=T7v_MBUOmCsp4n0SNmYY_DOEkhQXAp0rTGpdi6KkXNA@mail.gmail.com>
On 20120505-13:33, Raul Xiong wrote:
> 2012/5/5 Turquette, Mike <mturquette@ti.com>
> > Bad news: lockdep gets cranky about possible deadlocks due to holding
> > prepare_lock and then trying to hold it again in a rate-change
> > notifier handler (from OMAP's regulator code). Specifically
> >
>
> Glad to see common clock framework will support DVFS. Can we use different
> spinlock for different clocks with different lockdep lock classes to avoid
> the dead lock and lockdep warnings?
I understand that different lockdep classes could allow for nested
locking, but I don't have a good idea of how that would actually be
implemented. Could you elaborate a bit more?
In the mean time I'm looking at some different locking semantics that
don't involve lockdep class mangling, just a more fine-grained approach
to locking exactly what we want.
Regards,
Mike
next prev parent reply other threads:[~2012-05-06 23:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 2:02 common clock framework Chao Xie
2012-05-04 8:21 ` Sascha Hauer
2012-05-04 8:45 ` Chao Xie
2012-05-04 9:15 ` Russell King - ARM Linux
2012-05-04 10:20 ` Sascha Hauer
2012-05-04 23:08 ` Turquette, Mike
2012-05-05 8:28 ` Sascha Hauer
2012-05-05 17:44 ` Turquette, Mike
2012-05-08 9:01 ` Mark Brown
2012-05-08 17:29 ` Turquette, Mike
[not found] ` <CAG9bXv=T7v_MBUOmCsp4n0SNmYY_DOEkhQXAp0rTGpdi6KkXNA@mail.gmail.com>
2012-05-06 23:49 ` Mike Turquette [this message]
2012-05-07 3:49 ` Raul Xiong
[not found] ` <AAD1C6EB06EE3649B35B7E026785068D1A74B2C256@SC-VEXCH2.marvell.com>
[not found] ` <A63A0DC671D719488CD1A6CD8BDC16CF1A0F044EB4@SC-VEXCH4.marvell.com>
[not found] ` <53612FE6B944314AAADB181E45A45B6413D3FF9F37@sc-vexch3.marvell.com>
2012-05-18 8:41 ` Chao Xie
2012-05-22 18:57 ` Mike Turquette
2012-05-22 19:11 ` Mike Turquette
2012-06-14 13:09 ` Lei Wen
[not found] <AAD1C6EB06EE3649B35B7E026785068D1A749F0DB6@SC-VEXCH2.marvell.com>
[not found] ` <CAJOA=zPAy3AV6Dg9sE+fro1ZCmbxeCH8aeR5-YqffZphRkUQMQ@mail.gmail.com>
[not found] ` <AAD1C6EB06EE3649B35B7E026785068D1A749F10CC@SC-VEXCH2.marvell.com>
2012-04-25 4:40 ` Turquette, Mike
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=20120506234958.GA14559@gmail.com \
--to=mturquette@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.