Commit 74791d15 authored by Rob Herring's avatar Rob Herring Committed by Simon Horman
Browse files

dt-bindings: arm: renesas: Move 'renesas,prr' binding to its own doc



In preparation to convert board-level bindings to json-schema, move
various misc SoC bindings out to their own file.

Signed-off-by: default avatarRob Herring <robh@kernel.org>
Reviewed-by: default avatarGeert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: default avatarSimon Horman <horms+renesas@verge.net.au>
parent ea456bf9
Loading
Loading
Loading
Loading
+20 −0
Original line number Diff line number Diff line
Renesas Product Register

Most Renesas ARM SoCs have a Product Register or Boundary Scan ID Register that
allows to retrieve SoC product and revision information.  If present, a device
node for this register should be added.

Required properties:
  - compatible: Must be one of:
    "renesas,prr"
    "renesas,bsid"
  - reg: Base address and length of the register block.


Examples
--------

	prr: chipid@ff000044 {
		compatible = "renesas,prr";
		reg = <0 0xff000044 0 4>;
	};
+0 −18
Original line number Diff line number Diff line
@@ -153,21 +153,3 @@ Boards:
    compatible = "renesas,v3msk", "renesas,r8a77970"
  - Wheat (RTP0RC7792ASKB0000JE)
    compatible = "renesas,wheat", "renesas,r8a7792"


Most Renesas ARM SoCs have a Product Register or Boundary Scan ID Register that
allows to retrieve SoC product and revision information.  If present, a device
node for this register should be added.

Required properties:
  - compatible: Must be "renesas,prr" or "renesas,bsid"
  - reg: Base address and length of the register block.


Examples
--------

	prr: chipid@ff000044 {
		compatible = "renesas,prr";
		reg = <0 0xff000044 0 4>;
	};