dt-bindings: fuse: Document compatible string for Tegra264 FUSE

From: Thierry Reding <[email protected]>

This hardware block is mostly the same as the one found on earlier generations. However, the exact register regions that can be accessed differ, so a new compatible string is required.

---
 Documentation/devicetree/bindings/fuse/nvidia,tegra20-fuse.yaml | 1 +
 1 file changed, 1 insertion(+)

index 02f0b0462377..bf9923b63852 100644
@@ -22,6 +22,7 @@ properties:
           - nvidia,tegra186-efuse
           - nvidia,tegra194-efuse
           - nvidia,tegra234-efuse
+          - nvidia,tegra264-efuse
 
       - items:
           - const: nvidia,tegra132-efuse

2.52.0

From: Thierry Reding <[email protected]>

The FUSE block contains a number of registers exposing information that is useful for certain drivers and/or userspace to read at runtime.

---
 arch/arm64/boot/dts/nvidia/tegra264.dtsi | 7 +++++++
 1 file changed, 7 insertions(+)

index 8dbce25dfa3a..efb4d21aa4e3 100644
@@ -41,6 +41,13 @@ misc@100000 {
 			      <0x0 0x0c140000 0x0 0x10000>;
 		};
 
+		fuse@1000000 {
+			compatible = "nvidia,tegra264-efuse";
+			reg = <0x0 0x1000000 0x0 0x10000>;
+			clocks = <&bpmp TEGRA264_CLK_FUSE>;
+			clock-names = "fuse";
+		};
+
 		timer@8000000 {
 			compatible = "nvidia,tegra234-timer";
 			reg = <0x0 0x08000000 0x0 0x140000>;

2.52.0

New compatible string is always needed.

Confusing commit msg, same comments as for other patchset.

Best regards,
Krzysztof