Skip to contentSkip to conversation

ARM: u300: set up board power from device tree

PATCH In review Linus Walleij 2 participants 2 messages Apr 22, 2013 – Apr 24, 2013

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

PATCH 15/23 ARM: u300: set up board power from device tree

From: Linus Walleij <[email protected]>

This adds support for setting up the board power from the device tree on the U300. We use a board-specific node in the device tree for the S365 board and bind a regulator for the board power to this node.

---
Hi Mark, this was especially tricky due to the absence of a function to get a named regulator without a device node. After some cleverness introducing a node for the board akin to the solution I did for Nomadik, this seems to be an acceptable way forward, any other suggestions welcome.

---
 Documentation/devicetree/bindings/arm/ste-u300.txt | 13 +++++++
 arch/arm/mach-u300/regulator.c                     | 42 ++++++++++++++++++++--
 2 files changed, 52 insertions(+), 3 deletions(-)
Documentation/devicetree/bindings/arm/ste-u300.txt +13 -0
index 222dca5..cd9001a 100644
@@ -7,3 +7,16 @@ or board power regulator supplies.
 Required root node property:
 
 compatible="stericsson,u300";
+
+Boards with the U300 SoC include:
+
+S365 "Small Board U365":
+
+Required node: s365
+
+Example:
+
+s365 {
+	compatible = "stericsson,s365";
+	vana15-supply = <&ab3100_ldo_d_reg>;
+};
arch/arm/mach-u300/regulator.c +39 -3

68 lines not on this page · raw message

Signature · 1 line
1.7.11.3
#1 lore raw

PATCH 15/23 ARM: u300: set up board power from device tree

Quoted 5 lines · Linus Walleij

Hi Mark, this was especially tricky due to the absence of a function to get a named regulator without a device node. After some cleverness introducing a node for the board akin to the solution I did for Nomadik, this seems to be an acceptable way forward, any other suggestions welcome.

I would expect this to be bound based on the board name that appears in
the device tree which (given the way this stuff mostly works) I'd expect
to have a device node available.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130424/3a4ae311/attachment.sig>