From: Andreas Kemnade <andreas@kemnade.info>
To: Johan Hovold <johan@kernel.org>,
mark.rutland@arm.com, devicetree@vger.kernel.org,
letux-kernel@openphoenux.org, tony@atomide.com,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
bcousson@baylibre.com, linux-omap@vger.kernel.org
Cc: Andreas Kemnade <andreas@kemnade.info>
Subject: [PATCH v3 1/2] arm: dts: gta04: add ldo 3v3 regulator
Date: Thu, 31 Jan 2019 19:06:39 +0100 [thread overview]
Message-ID: <20190131180640.14480-2-andreas@kemnade.info> (raw)
In-Reply-To: <20190131180640.14480-1-andreas@kemnade.info>
Required for completeness sake to be able to specify
a regulator for devices having a non-optional regulator
property. It corresponds to the "3V3" net in the
schematics.
Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
---
new in v3
arch/arm/boot/dts/omap3-gta04.dtsi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-gta04.dtsi b/arch/arm/boot/dts/omap3-gta04.dtsi
index e53d32691308..02d8274a2f47 100644
--- a/arch/arm/boot/dts/omap3-gta04.dtsi
+++ b/arch/arm/boot/dts/omap3-gta04.dtsi
@@ -32,6 +32,14 @@
display1 = &tv0;
};
+ ldo_3v3: fixedregulator {
+ compatible = "regulator-fixed";
+ regulator-name = "ldo_3v3";
+ regulator-min-microvolt = <3300000>;
+ regulator-max-microvolt = <3300000>;
+ regulator-always-on;
+ };
+
/* fixed 26MHz oscillator */
hfclk_26m: oscillator {
#clock-cells = <0>;
--
2.11.0
next prev parent reply other threads:[~2019-01-31 18:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 18:06 [PATCH v3 0/2] arm: dts: gta04: add gps support Andreas Kemnade
2019-01-31 18:06 ` Andreas Kemnade [this message]
2019-02-01 10:02 ` [PATCH v3 1/2] arm: dts: gta04: add ldo 3v3 regulator Johan Hovold
2019-01-31 18:06 ` [PATCH v3 2/2] arm: dts: gta04: add gps support Andreas Kemnade
2019-02-01 10:04 ` Johan Hovold
2019-02-01 19:06 ` Andreas Kemnade
2019-02-01 20:09 ` [Letux-kernel] " H. Nikolaus Schaller
2019-02-04 8:30 ` Johan Hovold
2019-02-07 17:31 ` Tony Lindgren
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=20190131180640.14480-2-andreas@kemnade.info \
--to=andreas@kemnade.info \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=johan@kernel.org \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
/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).