[PATCH 3/4] dt-bindings: arm: Document Renesas R-Car M3-N-based Salvator-X board
From: horms@verge.net.au (Simon Horman)
Date: 2018-02-27 08:22:39
Also in:
linux-devicetree, linux-renesas-soc
On Mon, Feb 26, 2018 at 07:03:44PM +0100, Geert Uytterhoeven wrote:
The Renesas Salvator-X development board can be equipped with an R-Car H3, M3-W, or M3-N SiP, which are pin-compatible. Document board part number and compatible values for the version with R-Car M3-N. The board part number was extracted from a big patch by Takeshi Kihara in the BSP.
That I have verified.
quoted hunk ↗ jump to hunk
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> --- Documentation/devicetree/bindings/arm/shmobile.txt | 2 ++ 1 file changed, 2 insertions(+)diff --git a/Documentation/devicetree/bindings/arm/shmobile.txt b/Documentation/devicetree/bindings/arm/shmobile.txt index 82908a9447e4b051..51e4428856be4557 100644 --- a/Documentation/devicetree/bindings/arm/shmobile.txt +++ b/Documentation/devicetree/bindings/arm/shmobile.txt@@ -108,6 +108,8 @@ Boards: compatible = "renesas,salvator-x", "renesas,r8a7795" - Salvator-X (RTP0RC7796SIPB0011S)
Here we have: Name (Part No)
compatible = "renesas,salvator-x", "renesas,r8a7796" + - Salvator-X (RTP0RC7796SIPB0011S (M3N))
Here we have: Name (Part No (SoC))
+ compatible = "renesas,salvator-x", "renesas,r8a77965" - Salvator-XS (Salvator-X 2nd version, RTP0RC7795SIPB0012S)
And here we have: Name (Version, Part No)
compatible = "renesas,salvator-xs", "renesas,r8a7795" - Salvator-XS (Salvator-X 2nd version, RTP0RC7796SIPB0012S)
Can we think about making this more consistent?