linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: bilhuang@nvidia.com (Bill Huang)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 1/1] clk: Add notifier support in clk_prepare_enable/clk_disable_unprepare
Date: Fri, 15 Mar 2013 19:23:19 -0700	[thread overview]
Message-ID: <1363400599.2879.18.camel@bilhuang-vm1> (raw)
In-Reply-To: <CAPDyKFpHz6KCNbVe2AsDuzZw-oN7NyRzCA=RatWA+9iMaQ7C+Q@mail.gmail.com>

On Fri, 2013-03-15 at 20:33 +0800, Ulf Hansson wrote:
> I guess you did not fully got what I meant with "dvfs clock type". It
> will not affect the clock API. But instead the dvfs is handled by
> implementing a specific clk hw type. So the same thing is accomplished
> as with clk notifiers, no changes should be needed to device drivers.
> 
> The difference is only that no notifiers will be needed, and all the
> dvfs stuff will be handled in the clk hw instead. It will mean that we
> will bundle dvfs stuff into the clock drivers, instead of separating
> the code outside the clock drivers. But, on the other hand no
> notifiers will be needed.
> 
Oh yes I misunderstand your origin point, but my thought is using
existing devfreq framework as frequency/voltage policy driver instead of
creating another one in clock driver and that's why I think we need the
notifier work. 

By the way, some centralized DVFS implementation like Tegra's VDD_CORE
rail has association with tens of clocks which will need to be taken
care specially if we're doing those in clock driver I think.

> Kind regards
> Ulf Hansson

  parent reply	other threads:[~2013-03-16  2:23 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 12:37 [RFC 1/1] clk: Add notifier support in clk_prepare_enable/clk_disable_unprepare Bill Huang
2013-03-12 13:40 ` Russell King - ARM Linux
2013-03-13  1:47   ` Bill Huang
2013-03-13  4:42     ` Stephen Warren
2013-03-13  5:08       ` Bill Huang
2013-03-13  5:24         ` Stephen Warren
2013-03-13  5:40           ` Bill Huang
2013-03-13 18:10             ` Stephen Warren
2013-03-14  2:15               ` Bill Huang
2013-03-14  9:21                 ` Peter De Schrijver
2013-03-14  9:28                   ` Bill Huang
2013-03-14 17:54                     ` Stephen Warren
2013-03-15  1:20                       ` Bill Huang
2013-03-15  5:22                         ` Stephen Warren
2013-03-15  5:48                           ` Bill Huang
2013-03-15  9:39                           ` Peter De Schrijver
2013-03-15 10:08                             ` Ulf Hansson
2013-03-15 12:06                               ` Bill Huang
2013-03-15 12:33                                 ` Ulf Hansson
2013-03-15 19:38                                   ` Stephen Warren
2013-03-16  1:54                                     ` Bill Huang
2013-03-18 10:36                                     ` Ulf Hansson
2013-03-21 22:28                                       ` Mike Turquette
2013-03-16  2:23                                   ` Bill Huang [this message]
2013-03-15 17:12                           ` Russell King - ARM Linux
2013-03-15 17:09             ` Russell King - ARM Linux
2013-03-16  2:25               ` Bill Huang
2013-03-15 16:59       ` Russell King - ARM Linux
2013-03-15 16:57     ` Russell King - ARM Linux
2013-03-15 18:44       ` Nicolas Pitre

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=1363400599.2879.18.camel@bilhuang-vm1 \
    --to=bilhuang@nvidia.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 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).