Revert "dt-bindings: pinctrl: bcm4708-pinmux: rework binding to use syscon"

This reverts commit 2ae80900f239484069569380e1fc4340fd6e0089.

My rework was unneeded & wrong. It replaced a clear & correct "reg"
property usage with a custom "offset" one.

Back then I didn't understand how to properly handle CRU block binding.
I heard / read about syscon and tried to use it in a totally invalid
way. That change also missed Rob's review (obviously).

Northstar's pin controller is a simple consistent hardware block that
can be cleanly mapped using a 0x24 long reg space.

Since the rework commit there wasn't any follow up modifying in-kernel
DTS files to use the new binding. Broadcom also isn't known to use that
bugged binding. There is close to zero chance this revert may actually
cause problems / regressions.

This commit is a simple revert. Example binding may (should) be updated
/ cleaned up but that can be handled separately.

Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20211008205938.29925-1-zajec5@gmail.com
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

authored by Rafał Miłecki and committed by Linus Walleij 0398adae 64570fbc

+19 -15
+6 -5
Documentation/devicetree/bindings/mfd/brcm,cru.yaml
··· 32 32 "#size-cells": 33 33 const: 1 34 34 35 - pinctrl: 36 - $ref: ../pinctrl/brcm,ns-pinmux.yaml 37 - 38 35 patternProperties: 39 36 '^clock-controller@[a-f0-9]+$': 40 37 $ref: ../clock/brcm,iproc-clocks.yaml 38 + 39 + '^pin-controller@[a-f0-9]+$': 40 + $ref: ../pinctrl/brcm,ns-pinmux.yaml 41 41 42 42 '^thermal@[a-f0-9]+$': 43 43 $ref: ../thermal/brcm,ns-thermal.yaml ··· 73 73 "iprocfast", "sata1", "sata2"; 74 74 }; 75 75 76 - pinctrl { 76 + pin-controller@1c0 { 77 77 compatible = "brcm,bcm4708-pinmux"; 78 - offset = <0x1c0>; 78 + reg = <0x1c0 0x24>; 79 + reg-names = "cru_gpio_control"; 79 80 }; 80 81 81 82 thermal@2c0 {
+13 -10
Documentation/devicetree/bindings/pinctrl/brcm,ns-pinmux.yaml
··· 17 17 18 18 A list of pins varies across chipsets so few bindings are available. 19 19 20 - Node of the pinmux must be nested in the CRU (Central Resource Unit) "syscon" 21 - node. 22 - 23 20 properties: 24 21 compatible: 25 22 enum: ··· 24 27 - brcm,bcm4709-pinmux 25 28 - brcm,bcm53012-pinmux 26 29 27 - offset: 28 - description: offset of pin registers in the CRU block 30 + reg: 29 31 maxItems: 1 30 - $ref: /schemas/types.yaml#/definitions/uint32-array 32 + 33 + reg-names: 34 + const: cru_gpio_control 31 35 32 36 patternProperties: 33 37 '-pins$': ··· 70 72 uart1_grp ] 71 73 72 74 required: 73 - - offset 75 + - reg 76 + - reg-names 74 77 75 78 additionalProperties: false 76 79 77 80 examples: 78 81 - | 79 82 cru@1800c100 { 80 - compatible = "syscon", "simple-mfd"; 83 + compatible = "simple-bus"; 81 84 reg = <0x1800c100 0x1a4>; 85 + ranges; 86 + #address-cells = <1>; 87 + #size-cells = <1>; 82 88 83 - pinctrl { 89 + pin-controller@1c0 { 84 90 compatible = "brcm,bcm4708-pinmux"; 85 - offset = <0xc0>; 91 + reg = <0x1c0 0x24>; 92 + reg-names = "cru_gpio_control"; 86 93 87 94 spi-pins { 88 95 function = "spi";