Re: [RFC PATCH 6/7] dt-bindings: riscv: Remove "riscv,svXX" property from device-tree

From: Anup Patel
Date: Thu Mar 26 2020 - 03:04:03 EST


+Device tree mailing list

On Sun, Mar 22, 2020 at 4:36 PM Alexandre Ghiti <alex@xxxxxxxx> wrote:
>
> This property can not be used before virtual memory is set up
> and then the distinction between sv39 and sv48 is done at runtime
> using SATP csr property: this property is now useless, so remove it.
>
> Signed-off-by: Alexandre Ghiti <alex@xxxxxxxx>
> ---
> Documentation/devicetree/bindings/riscv/cpus.yaml | 13 -------------
> 1 file changed, 13 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/riscv/cpus.yaml b/Documentation/devicetree/bindings/riscv/cpus.yaml
> index 04819ad379c2..12baabbac213 100644
> --- a/Documentation/devicetree/bindings/riscv/cpus.yaml
> +++ b/Documentation/devicetree/bindings/riscv/cpus.yaml
> @@ -39,19 +39,6 @@ properties:
> Identifies that the hart uses the RISC-V instruction set
> and identifies the type of the hart.
>
> - mmu-type:
> - allOf:
> - - $ref: "/schemas/types.yaml#/definitions/string"
> - - enum:
> - - riscv,sv32
> - - riscv,sv39
> - - riscv,sv48
> - description:
> - Identifies the MMU address translation mode used on this
> - hart. These values originate from the RISC-V Privileged
> - Specification document, available from
> - https://riscv.org/specifications/
> -
> riscv,isa:
> allOf:
> - $ref: "/schemas/types.yaml#/definitions/string"
> --
> 2.20.1
>

Looks good to me.

Reviewed-by: Anup Patel <anup@xxxxxxxxxxxxxx>

Regards,
Anup