public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter 'p2' De Schrijver" <peter.de-schrijver@nokia.com>
To: ext David Brownell <david-b@pacbell.net>
Cc: Tony Lindgren <tony@atomide.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 0/1] Group and resource assignments for TWL4030
Date: Wed, 4 Mar 2009 16:41:21 +0200	[thread overview]
Message-ID: <20090304144121.GA2944@codecarver.research.nokia.com> (raw)
In-Reply-To: <200903031538.16757.david-b@pacbell.net>

On Wed, Mar 04, 2009 at 12:38:16AM +0100, ext David Brownell wrote:
> On Friday 27 February 2009, Tony Lindgren wrote:
> > * Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com> [090215 08:49]:
> > > On Fri, Feb 13, 2009 at 09:55:21PM +0100, ext David Brownell wrote:
> > > > On Tuesday 10 February 2009, Peter 'p2' De Schrijver wrote:
> > > > >
> > > > > This patch introduces support for board specific group assignments of TWL4030
> > > > > resources. The resource type and type2 fields can also be specified.
> > > > 
> > > > Do we have any real examples yet of needing to assign
> > > > resources to anything other than P1 (processor)?
> > > 
> > > Yes. On our custom hardware we use it to assign CLKEN to P3.
> 
> P3 roughly translating to "system running", with
> no regard to whether ARM(s) or DSP are active, yes?
> 

Depends on the board. We use P3 to control the system oscillator. The
SYSCLK_REQ output of OMAP3 is wired to the CLKREQ input on the TWL4030.
OMAP3 will disable SYSCLK_REQ when the system clock is no longer
necessary. (Eg, when going to chip retention).  This obviously only works if
CLKEN is only in P3.  (Otherwise it won't be turned off as P1 is still
active). A similar setup is used on the TI SDP3430 board.

Cheers,

Peter.

-- 
goa is a state of mind

  reply	other threads:[~2009-03-04 14:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10 13:11 [PATCH 0/1] Group and resource assignments for TWL4030 Peter 'p2' De Schrijver
2009-02-10 13:11 ` [PATCH 1/1] " Peter 'p2' De Schrijver
2009-02-10 13:28   ` Felipe Balbi
2009-03-03 23:28   ` David Brownell
2009-02-13 20:55 ` [PATCH 0/1] " David Brownell
2009-02-15 16:48   ` Peter 'p2' De Schrijver
2009-02-27 16:59     ` Tony Lindgren
2009-03-03 23:38       ` David Brownell
2009-03-04 14:41         ` Peter 'p2' De Schrijver [this message]
2009-03-06  0:16         ` Tony Lindgren
2009-03-13 15:33           ` Peter 'p2' De Schrijver
2009-03-13 15:33             ` [PATCH 1/1] " Peter 'p2' De Schrijver
2009-03-13 23:11               ` David Brownell
2009-03-14  1:16               ` [PATCH 1/1] Group and resource assignments for TWL4030 (v3) David Brownell

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=20090304144121.GA2944@codecarver.research.nokia.com \
    --to=peter.de-schrijver@nokia.com \
    --cc=david-b@pacbell.net \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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