linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: ux500: Enable Snowball's GPIO controlled Ethernet regulator in DT
Date: Mon, 21 Jan 2013 13:35:23 +0000	[thread overview]
Message-ID: <1358775323-8155-1-git-send-email-lee.jones@linaro.org> (raw)

The Snowball Board's Ethernet chip is configured in a slightly
non-standard way. Its SoC has an address space usually reserved
for a NOR-flash device. However, on the Snowball, that external
bus is populated by the SMSC9115 Ethernet chip. So, to power on
the Ethernet chip, we have to enable the GPIO controlled
regulator which usually controls the NOR-flash. In this patch
we inform the Snowball's Device Tree which GPIO is used to
operate it.

Signed-off-by: Lee Jones <lee.jones@linaro.org>
---
 arch/arm/boot/dts/snowball.dts |    9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/arch/arm/boot/dts/snowball.dts b/arch/arm/boot/dts/snowball.dts
index 27f31a5..4733a96 100644
--- a/arch/arm/boot/dts/snowball.dts
+++ b/arch/arm/boot/dts/snowball.dts
@@ -134,6 +134,7 @@
 				reg = <0 0x10000>;
 				interrupts = <12 0x1>;
 				interrupt-parent = <&gpio4>;
+
 				vdd33a-supply = <&en_3v3_reg>;
 				vddvario-supply = <&db8500_vape_reg>;
 
@@ -153,6 +154,7 @@
 			bus-width = <4>;
 			mmc-cap-mmc-highspeed;
 			vmmc-supply = <&ab8500_ldo_aux3_reg>;
+			vqmmc-supply = <&vmmci>;
 
 			cd-gpios  = <&gpio6 26 0x4>; // 218
 			cd-inverted;
@@ -346,5 +348,12 @@
 				};
 			};
 		};
+
+		vmmci: regulator-gpio {
+			gpios = <&gpio7 4 0x4>;        // 228
+			enable-gpio = <&gpio6 25 0x4>; // 217
+
+			status = "okay";
+		};
 	};
 };
-- 
1.7.9.5

             reply	other threads:[~2013-01-21 13:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-21 13:35 Lee Jones [this message]
2013-01-23  9:46 ` [PATCH 1/1] ARM: ux500: Enable Snowball's GPIO controlled Ethernet regulator in DT Linus Walleij

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1358775323-8155-1-git-send-email-lee.jones@linaro.org \
    --to=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).