From: Leyfoon Tan <leyfoon.tan@starfivetech.com>
To: Conor Dooley <conor@kernel.org>,
"palmer@dabbelt.com" <palmer@dabbelt.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jonathan Corbet <corbet@lwn.net>, "Alex Shi" <alexs@kernel.org>,
Yanteng Si <siyanteng@loongson.cn>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: RE: [PATCH v1 1/2] dt-bindings: arm: move cpu-capacity to a shared loation
Date: Thu, 5 Jan 2023 01:53:52 +0000 [thread overview]
Message-ID: <9350bdbcd0604507812a52e705fc3f77@EXMBX161.cuchost.com> (raw)
In-Reply-To: <20230104180513.1379453-2-conor@kernel.org>
>
> From: Conor Dooley <conor.dooley@microchip.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@microchip.com>
Hi Conor
I plan to move cpu-capacity.txt binding to generic directory as well after [1]. Thanks for your patch series helping this.
[1] https://patchwork.kernel.org/project/linux-riscv/patch/20230103035316.3841303-1-leyfoon.tan@starfivetech.com/
Reviewed-by: Ley Foon Tan <leyfoon.tan@starfivetech.com>
Regards
Ley Foon
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-01-05 18:43 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 [this message]
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
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=9350bdbcd0604507812a52e705fc3f77@EXMBX161.cuchost.com \
--to=leyfoon.tan@starfivetech.com \
--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=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