From: Daniel Lezcano <daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Lorenzo Pieralisi
<lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Dave Martin <dave.martin-5wv7dgnIgG8@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Sudeep KarkadaNagesha
<sudeep.karkadanagesha-5wv7dgnIgG8@public.gmane.org>,
Charles Garcia Tobin
<Charles.Garcia-Tobin-5wv7dgnIgG8@public.gmane.org>,
Nicolas Pitre <nico-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
Peter De Schrijver
<pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Grant Likely
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Santosh Shilimkar
<santosh.shilimkar-l0cyMroinI0@public.gmane.org>,
Mark Hambleton
<mark.hambleton-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
Hanjun Guo <hanjun.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Amit Kucheria
<amit.kucheria-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Vincent Guittot
<vincent.guittot-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH RFC 2/2] Documentation: arm: define DT C-states bindings
Date: Tue, 03 Dec 2013 12:52:36 +0100 [thread overview]
Message-ID: <529DC604.4050600@linaro.org> (raw)
In-Reply-To: <1386001205-11978-3-git-send-email-lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org>
On 12/02/2013 05:20 PM, Lorenzo Pieralisi wrote:
> ARM based platforms implement a variety of power management schemes that
> allow processors to enter at run-time low-power states, aka C-states
> in ACPI jargon. The parameters defining these C-states vary on a per-platform
> basis forcing the OS to hardcode the state parameters in platform
> specific static tables whose size grows as the number of platforms supported
> in the kernel increases and hampers device drivers standardization.
>
> Therefore, this patch aims at standardizing C-state device tree bindings for
> ARM platforms. Bindings define C-state parameters inclusive of entry methods
> and state latencies, to allow operating systems to retrieve the
> configuration entries from the device tree and initialize the related
> power management drivers, paving the way for common code in the kernel
> to deal with power states and removing the need for static data in current
> and previous kernel versions.
>
> Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org>
Hi Lorenzo,
thanks for the detailed description.
Just a couple of typos below.
[ ... ]
> +- cpu-power-states node
> +
> + Usage: Optional - On ARM systems, is a container of processor C-state
> + nodes. If the system does not provide CPU power
> + management capabilities or the processor just
> + supports WFI (C1 state) a cpu-power-states node is
> + not required.
> +
> + Description: cpu-power-states node is a container node, where its
> + subnodes describe the CPU low-power C-states.
> +
> + Node name must be "cpu-power-states".
> +
> + The cpu-power-states node's parent node must be cpus node.
> +
> + The cpu-power-states node's child nodes can be:
> +
> + - one or more state nodes
> +
> + The cpu-power-states node must contain the following properties:
> +
> + - compatible
> + Value type: <stringlist>
> + Usage: Required
Invert the field above to be consistent with the definitions below.
[ ... ]
> + - power-depth
> + Usage: Required
> + Value type: <u32>
> + Definition: Integer value, starting from 2 (value 0 meaning
> + running and value 1 representing power depth of
> + wfi (C1)), that defines the level of depth of a
> + power state.
> + The system denotes power states with different
> + depths, an increasing value meaning less power
> + consumption and might involve powering down more
> + components. Devices that are affected by
^^^ extra space
[ ... ]
Thanks
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 2/2] Documentation: arm: define DT C-states bindings
Date: Tue, 03 Dec 2013 12:52:36 +0100 [thread overview]
Message-ID: <529DC604.4050600@linaro.org> (raw)
In-Reply-To: <1386001205-11978-3-git-send-email-lorenzo.pieralisi@arm.com>
On 12/02/2013 05:20 PM, Lorenzo Pieralisi wrote:
> ARM based platforms implement a variety of power management schemes that
> allow processors to enter at run-time low-power states, aka C-states
> in ACPI jargon. The parameters defining these C-states vary on a per-platform
> basis forcing the OS to hardcode the state parameters in platform
> specific static tables whose size grows as the number of platforms supported
> in the kernel increases and hampers device drivers standardization.
>
> Therefore, this patch aims at standardizing C-state device tree bindings for
> ARM platforms. Bindings define C-state parameters inclusive of entry methods
> and state latencies, to allow operating systems to retrieve the
> configuration entries from the device tree and initialize the related
> power management drivers, paving the way for common code in the kernel
> to deal with power states and removing the need for static data in current
> and previous kernel versions.
>
> Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Hi Lorenzo,
thanks for the detailed description.
Just a couple of typos below.
[ ... ]
> +- cpu-power-states node
> +
> + Usage: Optional - On ARM systems, is a container of processor C-state
> + nodes. If the system does not provide CPU power
> + management capabilities or the processor just
> + supports WFI (C1 state) a cpu-power-states node is
> + not required.
> +
> + Description: cpu-power-states node is a container node, where its
> + subnodes describe the CPU low-power C-states.
> +
> + Node name must be "cpu-power-states".
> +
> + The cpu-power-states node's parent node must be cpus node.
> +
> + The cpu-power-states node's child nodes can be:
> +
> + - one or more state nodes
> +
> + The cpu-power-states node must contain the following properties:
> +
> + - compatible
> + Value type: <stringlist>
> + Usage: Required
Invert the field above to be consistent with the definitions below.
[ ... ]
> + - power-depth
> + Usage: Required
> + Value type: <u32>
> + Definition: Integer value, starting from 2 (value 0 meaning
> + running and value 1 representing power depth of
> + wfi (C1)), that defines the level of depth of a
> + power state.
> + The system denotes power states with different
> + depths, an increasing value meaning less power
> + consumption and might involve powering down more
> + components. Devices that are affected by
^^^ extra space
[ ... ]
Thanks
-- Daniel
--
<http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2013-12-03 11:52 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 16:20 [PATCH RFC 0/2] ARM: defining power states DT bindings Lorenzo Pieralisi
2013-12-02 16:20 ` Lorenzo Pieralisi
[not found] ` <1386001205-11978-1-git-send-email-lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org>
2013-12-02 16:20 ` [PATCH RFC 1/2] Documentation: arm: add cache " Lorenzo Pieralisi
2013-12-02 16:20 ` Lorenzo Pieralisi
2013-12-02 17:28 ` Kumar Gala
2013-12-02 17:28 ` Kumar Gala
2013-12-02 17:50 ` Lorenzo Pieralisi
2013-12-02 17:50 ` Lorenzo Pieralisi
2013-12-02 17:59 ` Kumar Gala
2013-12-02 17:59 ` Kumar Gala
2013-12-02 18:34 ` Lorenzo Pieralisi
2013-12-02 18:34 ` Lorenzo Pieralisi
2013-12-04 13:29 ` Dave Martin
2013-12-04 13:29 ` Dave Martin
2013-12-04 15:00 ` Lorenzo Pieralisi
2013-12-04 15:00 ` Lorenzo Pieralisi
2013-12-02 16:20 ` [PATCH RFC 2/2] Documentation: arm: define DT C-states bindings Lorenzo Pieralisi
2013-12-02 16:20 ` Lorenzo Pieralisi
2013-12-02 18:08 ` Kumar Gala
2013-12-02 18:08 ` Kumar Gala
2013-12-03 10:40 ` Lorenzo Pieralisi
2013-12-03 10:40 ` Lorenzo Pieralisi
2013-12-04 15:36 ` Kumar Gala
2013-12-04 15:36 ` Kumar Gala
2013-12-04 16:31 ` Lorenzo Pieralisi
2013-12-04 16:31 ` Lorenzo Pieralisi
[not found] ` <1386001205-11978-3-git-send-email-lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org>
2013-12-03 11:52 ` Daniel Lezcano [this message]
2013-12-03 11:52 ` Daniel Lezcano
2013-12-04 15:20 ` Dave Martin
2013-12-04 15:20 ` Dave Martin
2013-12-04 17:06 ` Lorenzo Pieralisi
2013-12-04 17:06 ` Lorenzo Pieralisi
2013-12-06 14:54 ` Vincent Guittot
2013-12-06 14:54 ` Vincent Guittot
2013-12-10 6:31 ` Antti Miettinen
2013-12-10 6:31 ` Antti Miettinen
2013-12-10 13:27 ` Lorenzo Pieralisi
2013-12-10 13:27 ` Lorenzo Pieralisi
2013-12-10 22:04 ` Antti Miettinen
2013-12-10 22:04 ` Antti Miettinen
2013-12-16 12:11 ` Lorenzo Pieralisi
2013-12-16 12:11 ` Lorenzo Pieralisi
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=529DC604.4050600@linaro.org \
--to=daniel.lezcano-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=Charles.Garcia-Tobin-5wv7dgnIgG8@public.gmane.org \
--cc=amit.kucheria-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=dave.martin-5wv7dgnIgG8@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=hanjun.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org \
--cc=mark.hambleton-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=nico-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
--cc=santosh.shilimkar-l0cyMroinI0@public.gmane.org \
--cc=sudeep.karkadanagesha-5wv7dgnIgG8@public.gmane.org \
--cc=vincent.guittot-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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.