From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: NXP Linux Team <linux-imx@nxp.com>,
"A. Sverdlin" <alexander.sverdlin@siemens.com>,
Dong Aisheng <aisheng.dong@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] i2c: lpi2c: cache peripheral clock rate
Date: Fri, 21 Apr 2023 15:59:52 +0200 [thread overview]
Message-ID: <20230421-kinfolk-glancing-e185fd9c47b4-mkl@pengutronix.de> (raw)
In-Reply-To: <9272339.EvYhyI6sBW@steina-w>
[-- Attachment #1: Type: text/plain, Size: 611 bytes --]
On 21.04.2023 15:48:59, Alexander Stein wrote:
[...]
> Now lpi2c_runtime_resume will call into clk_prepare() which also calls
> clk_prepare_lock() (identical to clk_get_rate).
IIRC this is a general problem^w limitation of the clock framework,
clock providers cannot use clocks themselves in certain callback, e.g.
set_rate.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung Nürnberg | Phone: +49-5121-206917-129 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-04-21 14:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 13:08 A. Sverdlin
2023-04-21 13:48 ` Alexander Stein
2023-04-21 13:59 ` Marc Kleine-Budde [this message]
2023-04-24 7:03 ` Alexander Stein
2023-04-30 7:05 ` Wolfram Sang
2023-05-02 6:50 ` Alexander Stein
2023-05-02 7:03 ` Marc Kleine-Budde
2023-04-21 14:10 ` Sverdlin, Alexander
2023-05-15 9:11 ` Alexander Stein
2023-05-15 12:04 ` Sverdlin, Alexander
2023-05-15 12:32 ` Alexander Stein
2023-05-15 12:37 ` Sverdlin, Alexander
2023-05-15 13:11 ` Sverdlin, Alexander
2023-04-24 8:08 ` Alexander Stein
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=20230421-kinfolk-glancing-e185fd9c47b4-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=aisheng.dong@nxp.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=alexander.sverdlin@siemens.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®