[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <167321452534.325217.3239534782123890748.robh@kernel.org>
Date: Sun, 8 Jan 2023 15:48:46 -0600
From: Rob Herring <robh@...nel.org>
To: Conor Dooley <conor@...nel.org>
Cc: linux-doc@...r.kernel.org, palmer@...belt.com,
devicetree@...r.kernel.org, Sudeep Holla <sudeep.holla@....com>,
Rob Herring <robh+dt@...nel.org>,
Jonathan Corbet <corbet@....net>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
linux-riscv@...ts.infradead.org, Alex Shi <alexs@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
linux-kernel@...r.kernel.org,
Ley Foon Tan <leyfoon.tan@...rfivetech.com>,
Yanteng Si <siyanteng@...ngson.cn>,
Conor Dooley <conor.dooley@...rochip.com>
Subject: Re: [PATCH v1 1/2] dt-bindings: arm: move cpu-capacity to a shared
loation
On Wed, 04 Jan 2023 18:05:13 +0000, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@...rochip.com>
>
> RISC-V uses the same generic topology code as arm64 & while there
> currently exists no binding for cpu-capacity on RISC-V, the code paths
> can be hit if the property is present.
>
> Move the documentation of cpu-capacity to a shared location, ahead of
> defining a binding for capacity-dmips-mhz on RISC-V. Update some
> references to this document in the process.
>
> Signed-off-by: Conor Dooley <conor.dooley@...rochip.com>
> ---
> I wasn't sure what to do with reference [1], but since the property will
> be the same on RISC-V, I left it as is.
> ---
> Documentation/devicetree/bindings/arm/cpus.yaml | 2 +-
> .../devicetree/bindings/{arm => cpu}/cpu-capacity.txt | 4 ++--
> Documentation/scheduler/sched-capacity.rst | 2 +-
> Documentation/translations/zh_CN/scheduler/sched-capacity.rst | 2 +-
> 4 files changed, 5 insertions(+), 5 deletions(-)
> rename Documentation/devicetree/bindings/{arm => cpu}/cpu-capacity.txt (98%)
>
Acked-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists