From: Rob Herring <robh@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: Alex Shi <alexs@kernel.org>,
devicetree@vger.kernel.org, Yanteng Si <siyanteng@loongson.cn>,
Ley Foon Tan <leyfoon.tan@starfivetech.com>,
linux-kernel@vger.kernel.org, Sudeep Holla <sudeep.holla@arm.com>,
linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-riscv@lists.infradead.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
palmer@dabbelt.com, Rob Herring <robh+dt@kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v1 2/2] dt-bindings: riscv: add a capacity-dmips-mhz cpu property
Date: Sun, 8 Jan 2023 15:49:07 -0600 [thread overview]
Message-ID: <167321454620.325726.1419996484202189237.robh@kernel.org> (raw)
In-Reply-To: <20230104180513.1379453-3-conor@kernel.org>
On Wed, 04 Jan 2023 18:05:14 +0000, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> Since commit 03f11f03dbfe ("RISC-V: Parse cpu topology during boot.")
> RISC-V has used the generic arch topology code, which provides for
> disparate CPU capacities. We never defined a binding to acquire this
> information from the DT though, so document the one already used by the
> generic arch topology code: "capacity-dmips-mhz".
>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> Documentation/devicetree/bindings/riscv/cpus.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2023-01-08 21:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 18:05 [PATCH v1 0/2] dt-bindings: Add a cpu-capacity property for RISC-V Conor Dooley
2023-01-04 18:05 ` [PATCH v1 1/2] dt-bindings: arm: move cpu-capacity to a shared loation Conor Dooley
2023-01-05 1:53 ` Leyfoon Tan
2023-01-08 21:48 ` Rob Herring
2023-01-10 9:02 ` Yanteng Si
2023-01-04 18:05 ` [PATCH v1 2/2] dt-bindings: riscv: add a capacity-dmips-mhz cpu property Conor Dooley
2023-01-05 1:55 ` Leyfoon Tan
2023-01-08 21:49 ` Rob Herring [this message]
2023-02-15 14:56 ` [PATCH v1 0/2] dt-bindings: Add a cpu-capacity property for RISC-V Palmer Dabbelt
2023-02-15 15:00 ` patchwork-bot+linux-riscv
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=167321454620.325726.1419996484202189237.robh@kernel.org \
--to=robh@kernel.org \
--cc=alexs@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leyfoon.tan@starfivetech.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=palmer@dabbelt.com \
--cc=robh+dt@kernel.org \
--cc=siyanteng@loongson.cn \
--cc=sudeep.holla@arm.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
all inboxes | Powered by JetHome®