From: Marek Vasut <marex@denx.de>
To: Tim Harvey <tharvey@gateworks.com>
Cc: linux-arm-kernel@lists.infradead.org,
Fabio Estevam <festevam@denx.de>,
NXP Linux Team <linux-imx@nxp.com>, Peng Fan <peng.fan@nxp.com>,
Shawn Guo <shawnguo@kernel.org>
Subject: Re: [PATCH] arm64: dts: imx8mm: Model PMIC to SNVS RTC clock path on Data Modul i.MX8M Mini eDM SBC
Date: Tue, 27 Sep 2022 22:10:51 +0200 [thread overview]
Message-ID: <0bb82751-a611-e8cd-54bd-e0d04b709133@denx.de> (raw)
In-Reply-To: <CAJ+vNU1gBFNC5j+8RbDCDjYynoZReR-3c9DmcHgWBhU4tv-ysw@mail.gmail.com>
On 9/27/22 21:43, Tim Harvey wrote:
Tim,
> Marek,
>
> The modeling here makes sense, but I tried this on the boards I have
> with the rohm,bd71847 and it did not bump the clk_enable_count for
> clk-32k-out and thus drivers/clk/clk-bd718x7.c still disables the
> clock. Is something else required to make that happen?
The only thing I can think of is, do you have SNVS_RTC driver enabled
and compiled in, just like the PMIC, or are they maybe modules ?
You can always try and add a printk() into the snvs rtc driver and see
whether the clk_get there doesn't fail for some reason, and what the
error code is.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-27 20:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-24 17:46 [PATCH] arm64: dts: imx8mm: Model PMIC to SNVS RTC clock path on Data Modul i.MX8M Mini eDM SBC Marek Vasut
2022-09-26 7:59 ` Peng Fan
2022-09-27 19:43 ` Tim Harvey
2022-09-27 20:10 ` Marek Vasut [this message]
2022-09-27 20:23 ` Tim Harvey
2022-09-27 20:31 ` Marek Vasut
2022-09-27 20:43 ` Tim Harvey
2022-09-27 21:08 ` Marek Vasut
2022-10-24 1:23 ` 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=0bb82751-a611-e8cd-54bd-e0d04b709133@denx.de \
--to=marex@denx.de \
--cc=festevam@denx.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=peng.fan@nxp.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.