Skip to content

Commit a452816

Browse files
SiFiveHollandpalmer-dabbelt
authored andcommitted
dt-bindings: riscv: cpus: Clarify mmu-type interpretation
The current description implies that only a single address translation mode is available to the operating system. However, some implementations support multiple address translation modes, and the operating system is free to choose between them. Per the RISC-V privileged specification, Sv48 implementations must also implement Sv39, and likewise Sv57 implies support for Sv48. This means it is possible to describe all supported address translation modes using a single value, by naming the largest supported mode. This appears to have been the intended usage of the property, so note it explicitly. Fixes: 4fd669a ("dt-bindings: riscv: convert cpu binding to json-schema") Signed-off-by: Samuel Holland <[email protected]> Reviewed-by: Conor Dooley <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Palmer Dabbelt <[email protected]>
1 parent 951df4e commit a452816

File tree

1 file changed

+2
-2
lines changed
  • Documentation/devicetree/bindings/riscv

1 file changed

+2
-2
lines changed

Documentation/devicetree/bindings/riscv/cpus.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -63,8 +63,8 @@ properties:
6363

6464
mmu-type:
6565
description:
66-
Identifies the MMU address translation mode used on this
67-
hart. These values originate from the RISC-V Privileged
66+
Identifies the largest MMU address translation mode supported by
67+
this hart. These values originate from the RISC-V Privileged
6868
Specification document, available from
6969
https://riscv.org/specifications/
7070
$ref: /schemas/types.yaml#/definitions/string

0 commit comments

Comments
 (0)