Skip to contentSkip to conversation

regulator: dt-bindings: rpi-panel: Mark 7" Raspberry Pi as GPIO controller

PATCH In review Marek Vasut 2 participants 2 messages Jan 7 – Jan 13

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 regulator: dt-bindings: rpi-panel: Mark 7" Raspberry Pi as GPIO controller

Mark the Raspberry Pi 7" Display 1 ATTINY based regulator as GPIO controller, because the hardware behaves that way in addition to being a regulator. Add fixed gpio-cells as well.

---
Cc: Broadcom internal kernel review list <[email protected]>
Cc: Conor Dooley <[email protected]>
Cc: Florian Fainelli <[email protected]>
Cc: Krzysztof Kozlowski <[email protected]>
Cc: Liam Girdwood <[email protected]>
Cc: Mark Brown <[email protected]>
Cc: Rob Herring <[email protected]>
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]

---
 .../raspberrypi,7inch-touchscreen-panel-regulator.yaml       | 5 +++++
 1 file changed, 5 insertions(+)
Documentation/devicetree/bindings/regulator/raspberrypi,7inch-touchscreen-panel-regulator.yaml +5 -0
index 41678400e63fa..6c23f18a32c6c 100644
@@ -24,6 +24,11 @@ properties:
   reg:
     maxItems: 1
 
+  gpio-controller: true
+
+  "#gpio-cells":
+    const: 2
+
 additionalProperties: false
 
 required:
Signature · 1 line
2.51.0
maintainer
#1 lore raw
Quoted 6 lines · Marek Vasut

Mark the Raspberry Pi 7" Display 1 ATTINY based regulator as GPIO controller, because the hardware behaves that way in addition to being a regulator. Add fixed gpio-cells as well.

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/1] regulator: dt-bindings: rpi-panel: Mark 7" Raspberry Pi as GPIO controller

      commit: 62b04225e99a5d1c71c5c73d2aa6618bc2c0738f

All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying to this mail.

Thanks,
Mark