From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Tim Harvey <tharvey@gateworks.com>,
linux-clk <linux-clk@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Shawn Guo <shawnguo@kernel.org>
Cc: NXP Linux Team <linux-imx@nxp.com>,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Marek Vasut <marex@denx.de>
Subject: Re: BD71847 clk driver disables clk-32k-out causing RTC/WDT failure
Date: Fri, 2 Sep 2022 07:14:01 +0300 [thread overview]
Message-ID: <59b6dd0a-7cbb-5dbd-8da0-57baeba3327e@gmail.com> (raw)
In-Reply-To: <CAJ+vNU1Za2CPGVX3q4HKufsxbL5zRrk1B5CWFpKritetrTs4dA@mail.gmail.com>
Hi Tim,
On 9/2/22 01:23, Tim Harvey wrote:
> Greetings,
>
> I've found that the bd71847 clk driver (CONFIG_COMMON_CLK_BD718XX
> drivers/clk/clk-bd718x7.c) disables clk-32k-out (the BD71847 C32K_OUT
> pin) which is connected IMX8MM RTC_XTALI which ends up disabling the
> IMX RTC as well as the IMX WDOG functionality.
//snip
> This happens via clk_unprepare_unused() as nothing is flagging the
> clk-32k-out as being used. What should be added to the device-tree to
> signify that this clk is indeed necessary and should not be disabled?
I have seen following proposal from Marek Vasut:
https://lore.kernel.org/all/20220517235919.200375-1-marex@denx.de/T/#m52d6d0831bf43d5f293e35cb27f3021f278d0564
I am not sure if the discussion is completed though. I guess it was
agreed this was needed/usefull and maybe the remaining thing to decide
was just the property naming.
Best Regards
-- Matti
--
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland
~~ When things go utterly wrong vim users can always type :help! ~~
next prev parent reply other threads:[~2022-09-02 4:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 22:23 BD71847 clk driver disables clk-32k-out causing RTC/WDT failure Tim Harvey
2022-09-02 4:14 ` Matti Vaittinen [this message]
2022-09-08 16:00 ` Tim Harvey
2022-09-08 16:55 ` Marek Vasut
2022-09-08 19:25 ` Tim Harvey
2022-09-08 20:39 ` Marek Vasut
2022-09-09 2:06 ` Peng Fan
2022-09-09 2:35 ` Marek Vasut
2022-09-09 5:06 ` Matti Vaittinen
2022-09-12 7:40 ` Peng Fan
2022-09-12 17:15 ` Tim Harvey
2022-09-12 20:40 ` Matti Vaittinen
2022-09-13 2:27 ` Peng Fan
2022-09-13 15:21 ` Sebastian Reichel
2022-09-13 17:01 ` Matti Vaittinen
2022-09-13 2:30 ` Peng Fan
2022-09-09 6:56 ` Peng Fan
2022-09-09 7:01 ` Peng Fan
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=59b6dd0a-7cbb-5dbd-8da0-57baeba3327e@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=festevam@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=tharvey@gateworks.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).