lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <cd14275c-4a81-ad92-ffc7-d81ead203fad@microchip.com>
Date:   Tue, 13 Jul 2021 15:31:02 +0000
From:   <Conor.Dooley@...rochip.com>
To:     <bmeng.cn@...il.com>, <palmer@...belt.com>,
        <paul.walmsley@...ive.com>, <atish.patra@....com>,
        <linux-kernel@...r.kernel.org>, <linux-riscv@...ts.infradead.org>
CC:     <bin.meng@...driver.com>
Subject: Re: [PATCH] riscv: dts: microchip: Define hart clocks

On 16/06/2021 07:27, Bin Meng wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> From: Bin Meng <bin.meng@...driver.com>
>
> Declare that each hart in the DT is clocked by <&clkcfg 0>.
>
> Signed-off-by: Bin Meng <bin.meng@...driver.com>
>
> ---
> Similar to https://patchwork.kernel.org/project/linux-riscv/patch/1592308864-30205-3-git-send-email-yash.shah@sifive.com/,
> this adds the same <clock> property to PolarFire SoC CPU nodes so that we can
> calculate the running frequency of the hart.
>
>   arch/riscv/boot/dts/microchip/microchip-mpfs.dtsi | 5 +++++
>   1 file changed, 5 insertions(+)
>
> diff --git a/arch/riscv/boot/dts/microchip/microchip-mpfs.dtsi b/arch/riscv/boot/dts/microchip/microchip-mpfs.dtsi
> index a00d9dc560d3..0659068b62f7 100644
> --- a/arch/riscv/boot/dts/microchip/microchip-mpfs.dtsi
> +++ b/arch/riscv/boot/dts/microchip/microchip-mpfs.dtsi
> @@ -24,6 +24,7 @@ cpu@0 {
>                          i-cache-size = <16384>;
>                          reg = <0>;
>                          riscv,isa = "rv64imac";
> +                       clocks = <&clkcfg 0>;
>                          status = "disabled";
>
>                          cpu0_intc: interrupt-controller {
> @@ -50,6 +51,7 @@ cpu@1 {
>                          reg = <1>;
>                          riscv,isa = "rv64imafdc";
>                          tlb-split;
> +                       clocks = <&clkcfg 0>;
>                          status = "okay";
>
>                          cpu1_intc: interrupt-controller {
> @@ -76,6 +78,7 @@ cpu@2 {
>                          reg = <2>;
>                          riscv,isa = "rv64imafdc";
>                          tlb-split;
> +                       clocks = <&clkcfg 0>;
>                          status = "okay";
>
>                          cpu2_intc: interrupt-controller {
> @@ -102,6 +105,7 @@ cpu@3 {
>                          reg = <3>;
>                          riscv,isa = "rv64imafdc";
>                          tlb-split;
> +                       clocks = <&clkcfg 0>;
>                          status = "okay";
>
>                          cpu3_intc: interrupt-controller {
> @@ -128,6 +132,7 @@ cpu@4 {
>                          reg = <4>;
>                          riscv,isa = "rv64imafdc";
>                          tlb-split;
> +                       clocks = <&clkcfg 0>;
>                          status = "okay";
>                          cpu4_intc: interrupt-controller {
>                                  #interrupt-cells = <1>;
> --
> 2.25.1
>

Reviewed-by: conor dooley<conor.dooley@...rochip.com>

> _______________________________________________
> linux-riscv mailing list
> linux-riscv@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ