linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 1/8] Documentation: arm: define DT cpu capacity-dmips-mhz bindings
Date: Mon, 12 Dec 2016 12:40:05 +0000	[thread overview]
Message-ID: <20161212124005.GA19177@red-moon> (raw)
In-Reply-To: <1473085372-2840-2-git-send-email-juri.lelli@arm.com>

On Mon, Sep 05, 2016 at 03:22:45PM +0100, Juri Lelli wrote:

[...]

> +===========================================
> +5 - References
> +===========================================
> +
> +[1] ARM Linux Kernel documentation - CPUs bindings
> +    Documentation/devicetree/bindings/arm/cpus.txt
> diff --git a/Documentation/devicetree/bindings/arm/cpus.txt b/Documentation/devicetree/bindings/arm/cpus.txt
> index e6782d50cbcd..c1dcf4cade2e 100644
> --- a/Documentation/devicetree/bindings/arm/cpus.txt
> +++ b/Documentation/devicetree/bindings/arm/cpus.txt
> @@ -241,6 +241,14 @@ nodes to be present and contain the properties described below.
>  			# List of phandles to idle state nodes supported
>  			  by this cpu [3].
>  
> +	- capacity-dmips-mhz
> +		Usage: Optional
> +		Value type: <u32>
> +		Definition:
> +			# u32 value representing CPU capacity [3] in
> +			  DMIPS/MHz, relative to highest capacity-dmips-mhz
> +			  in the system.
> +
>  	- rockchip,pmu
>  		Usage: optional for systems that have an "enable-method"
>  		       property value of "rockchip,rk3066-smp"
> @@ -464,3 +472,5 @@ cpus {
>  [2] arm/msm/qcom,kpss-acc.txt
>  [3] ARM Linux kernel documentation - idle states bindings
>      Documentation/devicetree/bindings/arm/idle-states.txt
> +[3] ARM Linux kernel documentation - cpu capacity bindings
> +    Documentation/devicetree/bindings/arm/cpu-capacity.txt

Trivia: bumped into this while reviewing something else, too many
threes, you will have to fix the added reference up.

Thanks,
Lorenzo

  reply	other threads:[~2016-12-12 12:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-05 14:22 [PATCH v7 0/8] CPUs capacity information for heterogeneous systems Juri Lelli
2016-09-05 14:22 ` [PATCH v7 1/8] Documentation: arm: define DT cpu capacity-dmips-mhz bindings Juri Lelli
2016-12-12 12:40   ` Lorenzo Pieralisi [this message]
2016-12-12 13:33     ` Juri Lelli
2016-09-05 14:22 ` [PATCH v7 2/8] arm: parse cpu capacity-dmips-mhz from DT Juri Lelli
2016-09-12  8:36   ` Vincent Guittot
2016-09-12  8:55     ` Juri Lelli
2016-09-05 14:22 ` [PATCH v7 3/8] arm, dts: add TC2 cpu capacity-dmips-mhz information Juri Lelli
2016-09-05 14:22 ` [PATCH v7 4/8] arm64: parse cpu capacity-dmips-mhz from DT Juri Lelli
2016-09-12  8:37   ` Vincent Guittot
2016-09-12  8:56     ` Juri Lelli
2016-09-05 14:22 ` [PATCH v7 5/8] arm64, dts: add Juno cpu capacity-dmips-mhz information Juri Lelli
2016-09-05 14:22 ` [PATCH v7 6/8] arm64, dts: add Juno r2 " Juri Lelli
2016-09-05 14:22 ` [PATCH v7 7/8] arm: add sysfs cpu_capacity attribute Juri Lelli
2016-09-05 14:22 ` [PATCH v7 8/8] arm64: " Juri Lelli
2016-09-12  7:24 ` [PATCH v7 0/8] CPUs capacity information for heterogeneous systems Juri Lelli
2016-09-19 11:10   ` Juri Lelli

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=20161212124005.GA19177@red-moon \
    --to=lorenzo.pieralisi@arm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).