From: David Brownell <david-b@pacbell.net>
To: Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/1] Group and resource assignments for TWL4030
Date: Fri, 13 Feb 2009 12:55:21 -0800 [thread overview]
Message-ID: <200902131255.21379.david-b@pacbell.net> (raw)
In-Reply-To: <1234271495-11705-1-git-send-email-peter.de-schrijver@nokia.com>
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)?
I'd sort of like to stick to simplifying assumptions,
notably "only P1 matters", until we have a clear need
to switch to another one.
This sort of thing ties into some patches I have
floating around, to disable regulators turned on
inappropriately by the boot loader. I was doing
that in a late_initcall in the regulator driver ...
but it's a bit messy, as the regulator framework
has deficiencies in that area (too).
- dave
next prev parent reply other threads:[~2009-02-13 20:55 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 ` David Brownell [this message]
2009-02-15 16:48 ` [PATCH 0/1] " 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
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=200902131255.21379.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
--cc=peter.de-schrijver@nokia.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