linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: gabriel.fernandez@st.com (gabriel.fernandez at st.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/6] ARM: dts: stm32f429: add LSI and LSE clocks
Date: Fri, 14 Oct 2016 11:18:15 +0200	[thread overview]
Message-ID: <1476436699-21879-3-git-send-email-gabriel.fernandez@st.com> (raw)
In-Reply-To: <1476436699-21879-1-git-send-email-gabriel.fernandez@st.com>

From: Gabriel Fernandez <gabriel.fernandez@st.com>

This patch adds lsi / lse oscillators. These clocks can be use by
RTC clocks.
The clock drivers needs to disable the power domain write protection using
syscon / regmap to enable these clocks.

Signed-off-by: Gabriel Fernandez <gabriel.fernandez@st.com>
---
 arch/arm/boot/dts/stm32f429.dtsi | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/arch/arm/boot/dts/stm32f429.dtsi b/arch/arm/boot/dts/stm32f429.dtsi
index 336ee4f..2700449 100644
--- a/arch/arm/boot/dts/stm32f429.dtsi
+++ b/arch/arm/boot/dts/stm32f429.dtsi
@@ -56,6 +56,18 @@
 			compatible = "fixed-clock";
 			clock-frequency = <0>;
 		};
+
+		clk-lse {
+			#clock-cells = <0>;
+			compatible = "fixed-clock";
+			clock-frequency = <32768>;
+		};
+
+		clk-lsi {
+			#clock-cells = <0>;
+			compatible = "fixed-clock";
+			clock-frequency = <32000>;
+		};
 	};
 
 	soc {
@@ -185,6 +197,11 @@
 			interrupts = <1>, <2>, <3>, <6>, <7>, <8>, <9>, <10>, <23>, <40>, <41>, <42>, <62>, <76>;
 		};
 
+		pwrcfg: power-config at 40007000 {
+			compatible = "syscon";
+			reg = <0x40007000 0x400>;
+		};
+
 		pin-controller {
 			#address-cells = <1>;
 			#size-cells = <1>;
@@ -340,6 +357,7 @@
 			compatible = "st,stm32f42xx-rcc", "st,stm32-rcc";
 			reg = <0x40023800 0x400>;
 			clocks = <&clk_hse>;
+			st,syscfg = <&pwrcfg>;
 		};
 
 		dma1: dma-controller at 40026000 {
-- 
1.9.1

  parent reply	other threads:[~2016-10-14  9:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14  9:18 [PATCH v2 0/6] STM32F4 Add RTC & QSPI clocks gabriel.fernandez at st.com
2016-10-14  9:18 ` [PATCH v2 1/6] clk: stm32f4: Add LSI & LSE clocks gabriel.fernandez at st.com
2016-10-19 20:24   ` Stephen Boyd
2016-10-20  7:47     ` Gabriel Fernandez
2016-10-20 16:05     ` Gabriel Fernandez
2016-10-14  9:18 ` gabriel.fernandez at st.com [this message]
2016-10-14  9:18 ` [PATCH v2 3/6] arm: stmf32: Enable SYSCON gabriel.fernandez at st.com
2016-10-14  9:18 ` [PATCH v2 4/6] clk: stm32f4: Add RTC clock gabriel.fernandez at st.com
2016-10-19 20:45   ` Stephen Boyd
2016-10-20  7:50     ` Gabriel Fernandez
2016-10-20  7:55     ` Gabriel Fernandez
2016-10-14  9:18 ` [PATCH v2 5/6] clk: stm32f469: Add QSPI clock gabriel.fernandez at st.com
2016-10-18 14:17   ` Rob Herring
2016-10-19 20:32   ` Stephen Boyd
2016-10-20 15:44     ` Gabriel Fernandez
2016-10-14  9:18 ` [PATCH v2 6/6] ARM: dts: stm32f429: " gabriel.fernandez at st.com
2016-11-03 16:45   ` Alexandre Torgue
2016-10-18 23:51 ` [PATCH v2 0/6] STM32F4 Add RTC & QSPI clocks Stephen Boyd
2016-10-19  8:34   ` Gabriel Fernandez
2016-10-19 20:29     ` Stephen Boyd
2016-10-20  7:52       ` Gabriel Fernandez
2016-11-03  8:52 ` Alexandre Torgue
2016-11-03  8:57   ` Gabriel Fernandez

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=1476436699-21879-3-git-send-email-gabriel.fernandez@st.com \
    --to=gabriel.fernandez@st.com \
    --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).