From: "Heiko Stübner" <heiko@sntech.de>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Andrew Bresticker <abrestic@chromium.org>,
linux-clk@vger.kernel.org, Michal Simek <michal.simek@xilinx.com>,
kernel@pengutronix.de, Georgi Djakov <georgi.djakov@linaro.org>,
Pawel Moll <pawel.moll@arm.com>,
Max Filippov <jcmvbkbc@gmail.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Ulf Hansson <ulf.hansson@linaro.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Santosh Shilimkar <ssantosh@kernel.org>,
Viresh Kumar <viresh.linux@gmail.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Zhangfei Gao <zhangfei.gao@linaro.org>,
Barry Song <baohua@kernel.org>, Alex Elder <elder@linaro.org>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
Dinh Nguyen <dinguyen@opensource.altera.com>,
linux-kernel@vger.kernel.org, emilio@elopez.com.ar,
dianders@chromium.org, Jason Cooper <jason@lakedaemon.net>,
Chao Xie <chao.xie@marvell.com>, Tero Kristo <t-kristo@ti.com>,
Gabriel FERNANDEZ <gabriel.fernandez@st.com>,
mturquette@linaro.org, sboyd@codeaurora.org
Subject: Re: [PATCH v3 0/2] clk: improve handling of orphan clocks
Date: Sat, 25 Apr 2015 15:44:11 +0200 [thread overview]
Message-ID: <8220650.vMaWphVIuC@diego> (raw)
In-Reply-To: <380631359.469897.1429964620007.JavaMail.open-xchange@oxbaltgw01.schlund.de>
Hi Stefan,
Am Samstag, 25. April 2015, 14:23:39 schrieb Stefan Wahren:
> > Heiko Stuebner <heiko@sntech.de> hat am 22. April 2015 um 22:53
> > geschrieben:
> >
> >
> > Using orphan clocks can introduce strange behaviour as they don't have
> > rate information at all and also of course don't track
> >
> > [...]
> >
> >
> > As this changes the behaviour for orphan clocks, it would of course
> > benefit from more testing than on my Rockchip boards. To keep the
> > recipent-list reasonable and not spam to much I selected one (the topmost)
> > from the get_maintainer output of each drivers/clk entry.
> > Hopefully some will provide Tested-by-tags :-)
>
> excuse me for my naive question, but what kind of tests do you expect
> (beside applying the patches)?
just a "everything that worked before still works" :-)
Using orphaned clocks should already produce strange issues most of the time -
for example I see clk_disable mismatches when suspending a rk3288 board,
before this patchset.
But nevertheless we now disallow the usage of orphaned clocks completely while
before it was possible to knowingly/unknowingly use them.
And while hopefully most drivers should handle an EPROBE_DEFER from clk_get
just fine, there may still be one or two lurking around that would need fixing
then ;-)
Heiko
next prev parent reply other threads:[~2015-04-25 13:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 20:53 [PATCH v3 0/2] clk: improve handling of orphan clocks Heiko Stuebner
2015-04-22 20:53 ` [PATCH v3 1/2] clk: track the orphan status of clocks and their children Heiko Stuebner
2015-04-30 23:20 ` Stephen Boyd
2015-04-22 20:53 ` [PATCH v3 2/2] clk: prevent orphan clocks from being used Heiko Stuebner
2015-04-30 23:20 ` Stephen Boyd
2015-04-25 12:23 ` [PATCH v3 0/2] clk: improve handling of orphan clocks Stefan Wahren
2015-04-25 13:44 ` Heiko Stübner [this message]
2015-04-26 19:58 ` Robert Jarzmik
2015-05-01 0:19 ` Stephen Boyd
2015-05-01 19:59 ` Heiko Stübner
2015-05-01 20:52 ` Stephen Boyd
2015-05-01 22:07 ` Heiko Stübner
2015-05-01 23:40 ` Stephen Boyd
2015-05-07 8:22 ` Tero Kristo
2015-05-07 18:18 ` Stephen Boyd
2015-05-08 11:41 ` Tero Kristo
2015-05-07 15:17 ` Kevin Hilman
2015-05-07 21:03 ` Stephen Boyd
2015-05-08 0:27 ` Kevin Hilman
2015-05-08 6:53 ` Stephen Boyd
2015-05-08 8:13 ` Sascha Hauer
2015-05-08 9:30 ` Heiko Stübner
2015-05-08 9:53 ` Sascha Hauer
2015-05-08 10:02 ` Maxime Ripard
2015-05-12 22:35 ` Stephen Boyd
2015-05-13 13:03 ` Maxime Ripard
2015-05-13 14:33 ` Kevin Hilman
2015-05-13 20:14 ` Maxime Ripard
2015-05-13 20:44 ` Kevin Hilman
2015-05-13 20:51 ` Maxime Ripard
2015-07-27 8:57 ` Heiko Stübner
2015-07-30 10:09 ` Maxime Ripard
2015-08-11 22:34 ` Stephen Boyd
2015-08-12 8:26 ` Heiko Stübner
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=8220650.vMaWphVIuC@diego \
--to=heiko@sntech.de \
--cc=abrestic@chromium.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=baohua@kernel.org \
--cc=boris.brezillon@free-electrons.com \
--cc=chao.xie@marvell.com \
--cc=dianders@chromium.org \
--cc=dinguyen@opensource.altera.com \
--cc=elder@linaro.org \
--cc=emilio@elopez.com.ar \
--cc=gabriel.fernandez@st.com \
--cc=geert+renesas@glider.be \
--cc=georgi.djakov@linaro.org \
--cc=jason@lakedaemon.net \
--cc=jcmvbkbc@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=mturquette@linaro.org \
--cc=pawel.moll@arm.com \
--cc=pdeschrijver@nvidia.com \
--cc=robert.jarzmik@free.fr \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@codeaurora.org \
--cc=ssantosh@kernel.org \
--cc=stefan.wahren@i2se.com \
--cc=swarren@wwwdotorg.org \
--cc=t-kristo@ti.com \
--cc=ulf.hansson@linaro.org \
--cc=viresh.linux@gmail.com \
--cc=zhangfei.gao@linaro.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).