From: Grant Likely <grant.likely@secretlab.ca>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv9 1/3] Runtime Interpreted Power Sequences
Date: Mon, 26 Nov 2012 15:34:53 +0000 [thread overview]
Message-ID: <20121126153453.2AA023E1AAA@localhost> (raw)
In-Reply-To: <20121122214021.GA14771@avionic-0098.adnet.avionic-design.de>
On Thu, 22 Nov 2012 22:40:21 +0100, Thierry Reding <thierry.reding@avionic-design.de> wrote:
> On Thu, Nov 22, 2012 at 01:39:41PM +0000, Grant Likely wrote:
> [...]
> > I do think that each sequence should be contained within a single
> > property, but I'm open to other suggestions.
>
> IIRC a very early prototype did implement something like that. However
> because of the resource issues this had to be string based, so that the
> sequences looked somewhat like (Alex, correct me if I'm wrong):
>
> power-on = <"REGULATOR", "power", 1, "GPIO", "enable", 1>;
>
> Instead we could possibly have something like:
>
> power-on = <0 ® 1,
> 1 &gpio 42 0 1>;
Yes, that would work, although I still think it would be a good idea to
split the used resources off into the gpios/pwms/regs/etc properties.
> Where the first cell in each entry defines the type (0 = regulator, 1 > GPIO) and the rest would be a regular OF specifier for the given type of
> resource along with some defined parameter such as enable/disable,
> voltage, delay in ms, ... I don't know if that sounds any better. It
> looks sort of cryptic but it is more "in the spirit of" DT, right Grant?
It is still kind of a ham-handed approach, but it does fit better with
existing conventions than the hierarchy of nodes does.
g.
WARNING: multiple messages have this Message-ID (diff)
From: Grant Likely <grant.likely@secretlab.ca>
To: Thierry Reding <thierry.reding@avionic-design.de>
Cc: Alexandre Courbot <gnurou@gmail.com>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
Stephen Warren <swarren@nvidia.com>,
Arnd Bergmann <arnd@arndb.de>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Mark Zhang <markz@nvidia.com>,
Rob Herring <rob.herring@calxeda.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alex Courbot <acourbot@nvidia.com>,
Anton Vorontsov <cbouatmailru@gmail.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCHv9 1/3] Runtime Interpreted Power Sequences
Date: Mon, 26 Nov 2012 15:34:53 +0000 [thread overview]
Message-ID: <20121126153453.2AA023E1AAA@localhost> (raw)
In-Reply-To: <20121122214021.GA14771@avionic-0098.adnet.avionic-design.de>
On Thu, 22 Nov 2012 22:40:21 +0100, Thierry Reding <thierry.reding@avionic-design.de> wrote:
> On Thu, Nov 22, 2012 at 01:39:41PM +0000, Grant Likely wrote:
> [...]
> > I do think that each sequence should be contained within a single
> > property, but I'm open to other suggestions.
>
> IIRC a very early prototype did implement something like that. However
> because of the resource issues this had to be string based, so that the
> sequences looked somewhat like (Alex, correct me if I'm wrong):
>
> power-on = <"REGULATOR", "power", 1, "GPIO", "enable", 1>;
>
> Instead we could possibly have something like:
>
> power-on = <0 ® 1,
> 1 &gpio 42 0 1>;
Yes, that would work, although I still think it would be a good idea to
split the used resources off into the gpios/pwms/regs/etc properties.
> Where the first cell in each entry defines the type (0 = regulator, 1 =
> GPIO) and the rest would be a regular OF specifier for the given type of
> resource along with some defined parameter such as enable/disable,
> voltage, delay in ms, ... I don't know if that sounds any better. It
> looks sort of cryptic but it is more "in the spirit of" DT, right Grant?
It is still kind of a ham-handed approach, but it does fit better with
existing conventions than the hierarchy of nodes does.
g.
WARNING: multiple messages have this Message-ID (diff)
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv9 1/3] Runtime Interpreted Power Sequences
Date: Mon, 26 Nov 2012 15:34:53 +0000 [thread overview]
Message-ID: <20121126153453.2AA023E1AAA@localhost> (raw)
In-Reply-To: <20121122214021.GA14771@avionic-0098.adnet.avionic-design.de>
On Thu, 22 Nov 2012 22:40:21 +0100, Thierry Reding <thierry.reding@avionic-design.de> wrote:
> On Thu, Nov 22, 2012 at 01:39:41PM +0000, Grant Likely wrote:
> [...]
> > I do think that each sequence should be contained within a single
> > property, but I'm open to other suggestions.
>
> IIRC a very early prototype did implement something like that. However
> because of the resource issues this had to be string based, so that the
> sequences looked somewhat like (Alex, correct me if I'm wrong):
>
> power-on = <"REGULATOR", "power", 1, "GPIO", "enable", 1>;
>
> Instead we could possibly have something like:
>
> power-on = <0 ® 1,
> 1 &gpio 42 0 1>;
Yes, that would work, although I still think it would be a good idea to
split the used resources off into the gpios/pwms/regs/etc properties.
> Where the first cell in each entry defines the type (0 = regulator, 1 =
> GPIO) and the rest would be a regular OF specifier for the given type of
> resource along with some defined parameter such as enable/disable,
> voltage, delay in ms, ... I don't know if that sounds any better. It
> looks sort of cryptic but it is more "in the spirit of" DT, right Grant?
It is still kind of a ham-handed approach, but it does fit better with
existing conventions than the hierarchy of nodes does.
g.
WARNING: multiple messages have this Message-ID (diff)
From: Grant Likely <grant.likely@secretlab.ca>
To: Thierry Reding <thierry.reding@avionic-design.de>
Cc: Alex Courbot <acourbot@nvidia.com>,
Alexandre Courbot <gnurou@gmail.com>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
Stephen Warren <swarren@nvidia.com>,
Arnd Bergmann <arnd@arndb.de>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Mark Zhang <markz@nvidia.com>,
Rob Herring <rob.herring@calxeda.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Anton Vorontsov <cbouatmailru@gmail.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCHv9 1/3] Runtime Interpreted Power Sequences
Date: Mon, 26 Nov 2012 15:34:53 +0000 [thread overview]
Message-ID: <20121126153453.2AA023E1AAA@localhost> (raw)
In-Reply-To: <20121122214021.GA14771@avionic-0098.adnet.avionic-design.de>
On Thu, 22 Nov 2012 22:40:21 +0100, Thierry Reding <thierry.reding@avionic-design.de> wrote:
> On Thu, Nov 22, 2012 at 01:39:41PM +0000, Grant Likely wrote:
> [...]
> > I do think that each sequence should be contained within a single
> > property, but I'm open to other suggestions.
>
> IIRC a very early prototype did implement something like that. However
> because of the resource issues this had to be string based, so that the
> sequences looked somewhat like (Alex, correct me if I'm wrong):
>
> power-on = <"REGULATOR", "power", 1, "GPIO", "enable", 1>;
>
> Instead we could possibly have something like:
>
> power-on = <0 ® 1,
> 1 &gpio 42 0 1>;
Yes, that would work, although I still think it would be a good idea to
split the used resources off into the gpios/pwms/regs/etc properties.
> Where the first cell in each entry defines the type (0 = regulator, 1 =
> GPIO) and the rest would be a regular OF specifier for the given type of
> resource along with some defined parameter such as enable/disable,
> voltage, delay in ms, ... I don't know if that sounds any better. It
> looks sort of cryptic but it is more "in the spirit of" DT, right Grant?
It is still kind of a ham-handed approach, but it does fit better with
existing conventions than the hierarchy of nodes does.
g.
next prev parent reply other threads:[~2012-11-26 15:34 UTC|newest]
Thread overview: 158+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-17 10:55 [PATCHv9 0/3] Runtime Interpreted Power Sequences Alexandre Courbot
2012-11-17 10:55 ` Alexandre Courbot
2012-11-17 10:55 ` Alexandre Courbot
2012-11-17 10:55 ` [PATCHv9 1/3] " Alexandre Courbot
2012-11-17 10:55 ` Alexandre Courbot
2012-11-17 10:55 ` Alexandre Courbot
2012-11-17 10:55 ` Alexandre Courbot
2012-11-17 11:38 ` Anton Vorontsov
2012-11-17 11:38 ` Anton Vorontsov
2012-11-17 11:38 ` Anton Vorontsov
2012-11-19 2:29 ` Alex Courbot
2012-11-19 2:29 ` Alex Courbot
2012-11-19 2:29 ` Alex Courbot
2012-11-19 2:29 ` Alex Courbot
2012-11-19 2:32 ` Anton Vorontsov
2012-11-19 2:32 ` Anton Vorontsov
2012-11-19 2:32 ` Anton Vorontsov
2012-11-20 14:48 ` Tomi Valkeinen
2012-11-20 14:48 ` Tomi Valkeinen
2012-11-20 14:48 ` Tomi Valkeinen
2012-11-20 14:48 ` Tomi Valkeinen
2012-11-21 1:56 ` Alex Courbot
2012-11-21 1:56 ` Alex Courbot
2012-11-21 1:56 ` Alex Courbot
2012-11-21 1:56 ` Alex Courbot
2012-11-21 8:13 ` Tomi Valkeinen
2012-11-21 8:13 ` Tomi Valkeinen
2012-11-21 8:13 ` Tomi Valkeinen
2012-11-21 8:13 ` Tomi Valkeinen
2012-11-21 8:32 ` Alex Courbot
2012-11-21 8:32 ` Alex Courbot
2012-11-21 8:32 ` Alex Courbot
2012-11-21 8:32 ` Alex Courbot
2012-11-21 8:48 ` Tomi Valkeinen
2012-11-21 8:48 ` Tomi Valkeinen
2012-11-21 8:48 ` Tomi Valkeinen
2012-11-21 8:48 ` Tomi Valkeinen
2012-11-21 10:00 ` Alex Courbot
2012-11-21 10:00 ` Alex Courbot
2012-11-21 10:00 ` Alex Courbot
2012-11-22 13:01 ` Grant Likely
2012-11-22 13:01 ` Grant Likely
2012-11-22 13:01 ` Grant Likely
2012-11-22 13:01 ` Grant Likely
2012-11-20 21:54 ` Grant Likely
2012-11-20 21:54 ` Grant Likely
2012-11-20 21:54 ` Grant Likely
2012-11-20 21:54 ` Grant Likely
2012-11-21 1:31 ` Mark Brown
2012-11-21 1:31 ` Mark Brown
2012-11-21 1:31 ` Mark Brown
2012-11-21 16:44 ` Grant Likely
2012-11-21 16:44 ` Grant Likely
2012-11-21 16:44 ` Grant Likely
2012-11-22 8:57 ` Linus Walleij
2012-11-22 8:57 ` Linus Walleij
2012-11-22 8:57 ` Linus Walleij
2012-11-22 8:57 ` Linus Walleij
2012-11-22 9:55 ` Alexandre Courbot
2012-11-22 9:55 ` Alexandre Courbot
2012-11-22 9:55 ` Alexandre Courbot
2012-11-22 9:55 ` Alexandre Courbot
2012-11-23 1:44 ` Mark Brown
2012-11-23 1:44 ` Mark Brown
2012-11-23 1:44 ` Mark Brown
2012-11-21 4:23 ` Alex Courbot
2012-11-21 4:23 ` Alex Courbot
2012-11-21 4:23 ` Alex Courbot
2012-11-21 11:06 ` Tomi Valkeinen
2012-11-21 11:06 ` Tomi Valkeinen
2012-11-21 11:06 ` Tomi Valkeinen
2012-11-21 11:06 ` Tomi Valkeinen
2012-11-21 11:40 ` Thierry Reding
2012-11-21 11:40 ` Thierry Reding
2012-11-21 11:40 ` Thierry Reding
2012-11-21 11:40 ` Thierry Reding
2012-11-21 12:04 ` Tomi Valkeinen
2012-11-21 12:04 ` Tomi Valkeinen
2012-11-21 12:04 ` Tomi Valkeinen
2012-11-21 13:00 ` Thierry Reding
2012-11-21 13:00 ` Thierry Reding
2012-11-21 13:00 ` Thierry Reding
2012-11-21 13:32 ` Tomi Valkeinen
2012-11-21 13:32 ` Tomi Valkeinen
2012-11-21 13:32 ` Tomi Valkeinen
2012-11-21 13:32 ` Tomi Valkeinen
2012-11-21 15:02 ` Alexandre Courbot
2012-11-21 15:02 ` Alexandre Courbot
2012-11-21 15:02 ` Alexandre Courbot
2012-11-21 15:02 ` Alexandre Courbot
2012-11-21 15:12 ` Thierry Reding
2012-11-21 15:12 ` Thierry Reding
2012-11-21 15:12 ` Thierry Reding
2012-11-22 2:01 ` Alexandre Courbot
2012-11-22 2:01 ` Alexandre Courbot
2012-11-22 2:01 ` Alexandre Courbot
2012-11-22 2:01 ` Alexandre Courbot
2012-11-22 2:06 ` Mark Brown
2012-11-22 2:06 ` Mark Brown
2012-11-22 2:06 ` Mark Brown
2012-11-22 2:06 ` Mark Brown
2012-11-22 3:09 ` Alexandre Courbot
2012-11-22 3:09 ` Alexandre Courbot
2012-11-22 3:09 ` Alexandre Courbot
2012-11-22 3:09 ` Alexandre Courbot
2012-11-22 13:39 ` Grant Likely
2012-11-22 13:39 ` Grant Likely
2012-11-22 13:39 ` Grant Likely
2012-11-22 13:39 ` Grant Likely
2012-11-27 15:19 ` Laurent Pinchart
2012-11-27 15:19 ` Laurent Pinchart
2012-11-27 15:19 ` Laurent Pinchart
2012-11-27 15:08 ` Laurent Pinchart
2012-11-27 15:08 ` Laurent Pinchart
2012-11-27 15:08 ` Laurent Pinchart
2012-11-27 15:08 ` Laurent Pinchart
2012-11-27 15:08 ` Laurent Pinchart
2012-11-27 15:19 ` Tomi Valkeinen
2012-11-27 15:19 ` Tomi Valkeinen
2012-11-27 15:19 ` Tomi Valkeinen
2012-11-27 15:19 ` Tomi Valkeinen
2012-11-27 15:37 ` Laurent Pinchart
2012-11-27 15:37 ` Laurent Pinchart
2012-11-27 15:37 ` Laurent Pinchart
2012-11-27 16:46 ` Mark Brown
2012-11-27 16:46 ` Mark Brown
2012-11-27 16:46 ` Mark Brown
2012-11-27 14:47 ` Laurent Pinchart
2012-11-27 14:47 ` Laurent Pinchart
2012-11-27 14:47 ` Laurent Pinchart
2012-11-27 14:47 ` Laurent Pinchart
2012-11-22 13:39 ` Grant Likely
2012-11-22 13:39 ` Grant Likely
2012-11-22 13:39 ` Grant Likely
2012-11-22 13:39 ` Grant Likely
2012-11-22 21:40 ` Thierry Reding
2012-11-22 21:40 ` Thierry Reding
2012-11-22 21:40 ` Thierry Reding
2012-11-22 21:40 ` Thierry Reding
2012-11-26 11:49 ` Alex Courbot
2012-11-26 11:49 ` Alex Courbot
2012-11-26 11:49 ` Alex Courbot
2012-11-26 11:49 ` Alex Courbot
2012-11-26 15:34 ` Grant Likely [this message]
2012-11-26 15:34 ` Grant Likely
2012-11-26 15:34 ` Grant Likely
2012-11-26 15:34 ` Grant Likely
2012-11-17 10:55 ` [PATCHv9 2/3] pwm_backlight: use power sequences Alexandre Courbot
2012-11-17 10:55 ` Alexandre Courbot
2012-11-17 10:55 ` Alexandre Courbot
2012-11-17 10:55 ` Alexandre Courbot
2012-11-17 10:55 ` [PATCHv9 3/3] Take maintainership of " Alexandre Courbot
2012-11-17 10:55 ` Alexandre Courbot
2012-11-17 10:55 ` Alexandre Courbot
2012-11-20 21:58 ` [PATCHv9 0/3] Runtime Interpreted Power Sequences Grant Likely
2012-11-20 21:58 ` Grant Likely
2012-11-20 21:58 ` Grant Likely
2012-11-20 21:58 ` Grant Likely
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=20121126153453.2AA023E1AAA@localhost \
--to=grant.likely@secretlab.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.