From: Krzysztof Kozlowski <krzk@kernel.org>
To: Rob Herring <robh+dt@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Krzysztof Kozlowski <krzk@kernel.org>
Subject: [PATCH v2 02/14] arm64: dts: imx8mm-evk: Add 32.768 kHz clock to PMIC
Date: Fri, 4 Sep 2020 08:27:31 +0200 [thread overview]
Message-ID: <20200904062743.6273-2-krzk@kernel.org> (raw)
In-Reply-To: <20200904062743.6273-1-krzk@kernel.org>
The ROHM BD71847 PMIC has a 32.768 kHz clock. Adding necessary parent
allows to probe the bd718x7 clock driver fixing boot errors:
bd718xx-clk bd71847-clk.1.auto: No parent clk found
bd718xx-clk: probe of bd71847-clk.1.auto failed with error -22
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
Acked-By: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
---
arch/arm64/boot/dts/freescale/imx8mm-evk.dts | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/imx8mm-evk.dts b/arch/arm64/boot/dts/freescale/imx8mm-evk.dts
index 38134d201eef..1c39a2b90ee1 100644
--- a/arch/arm64/boot/dts/freescale/imx8mm-evk.dts
+++ b/arch/arm64/boot/dts/freescale/imx8mm-evk.dts
@@ -169,6 +169,10 @@
interrupts = <3 GPIO_ACTIVE_LOW>;
rohm,reset-snvs-powered;
+ #clock-cells = <0>;
+ clocks = <&osc_32k 0>;
+ clock-output-names = "clk-32k-out";
+
regulators {
buck1_reg: BUCK1 {
regulator-name = "buck1";
--
2.17.1
next prev parent reply other threads:[~2020-09-04 6:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 6:27 [PATCH v2 01/14] arm64: dts: imx8mm-beacon: Align pin configuration group names with schema Krzysztof Kozlowski
2020-09-04 6:27 ` Krzysztof Kozlowski [this message]
2020-09-04 6:27 ` [PATCH v2 03/14] arm64: dts: imx8mm-evk: " Krzysztof Kozlowski
2020-09-04 6:27 ` [PATCH v2 04/14] arm64: dts: imx8mm-ddr4-evk: " Krzysztof Kozlowski
2020-09-04 6:27 ` [PATCH v2 05/14] arm64: dts: imx8mn-ddr4-evk: Align regulator " Krzysztof Kozlowski
2020-09-04 6:27 ` [PATCH v2 06/14] arm64: dts: imx8mn-evk: Align pin configuration group " Krzysztof Kozlowski
2020-09-04 6:27 ` [PATCH v2 07/14] arm64: dts: imx8mq-evk: " Krzysztof Kozlowski
2020-09-04 6:27 ` [PATCH v2 08/14] arm64: dts: imx8mq-librem5-devkit: " Krzysztof Kozlowski
2020-09-04 6:27 ` [PATCH v2 09/14] arm64: dts: imx8mq-phanbell: " Krzysztof Kozlowski
2020-09-04 6:27 ` [PATCH v2 10/14] arm64: dts: imx8mq-pico-pi: " Krzysztof Kozlowski
2020-09-04 6:27 ` [PATCH v2 11/14] arm64: dts: imx8mq-sr-som: " Krzysztof Kozlowski
2020-09-04 6:27 ` [PATCH v2 12/14] arm64: dts: imx8mq-hummingboard-pulse: " Krzysztof Kozlowski
2020-09-04 6:27 ` [PATCH v2 13/14] arm64: dts: imx8qxp-colibri: " Krzysztof Kozlowski
2020-09-04 6:27 ` [PATCH v2 14/14] ARM: dts: imx28-m28: Align GPMI NAND node name " Krzysztof Kozlowski
2020-09-05 8:05 ` Shawn Guo
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=20200904062743.6273-2-krzk@kernel.org \
--to=krzk@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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).