From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Keerthy <j-keerthy@ti.com>
Cc: sboyd@codeaurora.org, t-kristo@ti.com, mturquette@baylibre.com,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, Russ Dill <Russ.Dill@ti.com>
Subject: Re: [PATCH] clk: Add functions to save and restore clock/dpll context en-masse
Date: Wed, 3 May 2017 19:52:51 +0100 [thread overview]
Message-ID: <20170503185251.GR23750@n2100.armlinux.org.uk> (raw)
In-Reply-To: <1492492369-19662-1-git-send-email-j-keerthy@ti.com>
On Tue, Apr 18, 2017 at 10:42:49AM +0530, Keerthy wrote:
> From: Russ Dill <Russ.Dill@ti.com>
>
> The clock/dpll registers are in the WKUP power domain. Under both RTC-only
> suspend and hibernation, these registers are lost. Hence save/restore
> them accordingly.
This looks like a huge hammer, and I think this will cause problems for
some systems, especially where some clocks are on remote devices which
need to be controlled via I2C buses.
The generic part walks all root clocks in the system, and all children
of those clocks. If we have clocks on an I2C device, then we could
very well end up with a circular dependency - the I2C controller needs
its clocks restored in order for control of the clocks on the I2C device
to be accessible.
So, I think this needs more thought - clocks are not just about core SoC
clocks - and cracking this nut with such a big hammer is likely to cause
regressions all over the place.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2017-05-03 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 5:12 [PATCH] clk: Add functions to save and restore clock/dpll context en-masse Keerthy
2017-04-18 15:00 ` Tero Kristo
2017-04-25 6:00 ` Keerthy
2017-05-03 18:52 ` Russell King - ARM Linux [this message]
2017-05-04 8:58 ` Tero Kristo
2017-05-04 7:51 ` Peter De Schrijver
2017-05-04 8:17 ` Tero Kristo
2017-05-04 8:26 ` Keerthy
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=20170503185251.GR23750@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Russ.Dill@ti.com \
--cc=j-keerthy@ti.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=t-kristo@ti.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