From: "Nayak, Rajendra" <rnayak@ti.com>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Cc: "Nayak, Rajendra" <rnayak@ti.com>
Subject: [PATCH 00/03] OMAP3 clock: Remove virtual clock nodes
Date: Fri, 20 Mar 2009 19:20:02 +0530 [thread overview]
Message-ID: <5A47E75E594F054BAF48C5E4FC4B92AB02FAF6EF37@dbde02.ent.ti.com> (raw)
Hi,
This patch set removes the virtual clock node implementation for
VDD1/2 on omap3 which was causing issues with recursive locking of spinlocks.
All references to virtual clock nodes from resource framework and cpufreq
driver are removed. Resource framework now uses individual dpll clock
nodes to do frequency scaling.
Most of the functionality implemented as part of the virtual clock nodes
is now implemented internally in the resource framework.
Thanks to Tero Kristo <tero.kristo@nokia.com> who has implemented
most of these changes.
Patches generated and apply on pm-2.6.28 branch + [PATCH 00/09] OMAP3 clock: Clock rate change notifiers
regards,
Rajendra
next reply other threads:[~2009-03-20 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 13:50 Nayak, Rajendra [this message]
2009-03-26 18:13 ` [PATCH 00/03] OMAP3 clock: Remove virtual clock nodes 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=5A47E75E594F054BAF48C5E4FC4B92AB02FAF6EF37@dbde02.ent.ti.com \
--to=rnayak@ti.com \
--cc=linux-omap@vger.kernel.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 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).