mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: Felipe Balbi <balbi@ti.com>,
	Russell King <linux@arm.linux.org.uk>,
	Stephen Boyd <sboyd@codeaurora.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Mike Turquette <mturquette@ti.com>
Subject: Re: [RFC PATCH] clk: add extension API
Date: Thu, 31 May 2012 13:00:58 +0100	[thread overview]
Message-ID: <20120531120057.GA15786@sirena.org.uk> (raw)
In-Reply-To: <20120531083131.GQ8026@tbergstrom-lnx.Nvidia.com>

On Thu, May 31, 2012 at 11:31:31AM +0300, Peter De Schrijver wrote:

> > What I wonder most is if this should be done at the clock level or at
> > the device level. In the end you reset the IP block, not the clock,
> > right ?

> Yes. but, every block has at least 1 clock and thus the mapping is identical
> down to the register level. Ie. we could do this outside the clockframework,
> but then we would have the keep a list of IDs (1 per module) which the drivers
> can use to call some tegra reset function which would in the end use registers
> in the same memory area to cause a reset. (the registers controlling
> modulereset are interleaved with those controlling the enable/disable of the
> main moduleclock and bitpositions are identical)

One option which doesn't really need anything from the clock API is for
the module resets to restore these registers so the clock API never
notices anything changed.

  parent reply	other threads:[~2012-05-31 12:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-29  9:58 Peter De Schrijver
2012-05-30  8:52 ` Stephen Boyd
2012-05-30 19:40   ` Mike Turquette
2012-05-30 20:28     ` Stephen Boyd
2012-05-31 19:09       ` Mike Turquette
2012-05-31  3:29     ` Saravana Kannan
2012-05-31  8:23       ` Peter De Schrijver
2012-05-31 21:12         ` Saravana Kannan
2012-05-31  7:51   ` Peter De Schrijver
2012-05-31  8:18     ` Felipe Balbi
2012-05-31  8:31       ` Peter De Schrijver
2012-05-31  8:54         ` Felipe Balbi
2012-05-31  9:05           ` Peter De Schrijver
2012-05-31  9:26             ` Felipe Balbi
2012-05-31  9:43               ` Peter De Schrijver
2012-05-31  9:46                 ` Felipe Balbi
2012-05-31  9:57                   ` Peter De Schrijver
2012-05-31 10:01                     ` Felipe Balbi
2012-05-31 12:50             ` Cousson, Benoit
2012-05-31 13:04               ` Mark Brown
2012-05-31 13:07                 ` Cousson, Benoit
2012-05-31 13:11                   ` Mark Brown
2012-05-31 12:00         ` Mark Brown [this message]
2012-05-31  9:04     ` Stephen Boyd
2012-05-31  9:10       ` Peter De Schrijver
2012-05-30  9:28 ` Rajendra Nayak
2012-05-31 19:19   ` Mike Turquette
2012-06-06 12:07     ` Peter De Schrijver
2012-05-31 16:42 ` Stephen Warren

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=20120531120057.GA15786@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=balbi@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mturquette@ti.com \
    --cc=pdeschrijver@nvidia.com \
    --cc=sboyd@codeaurora.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

all inboxes | Powered by JetHome®