From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
"Jerome Brunet <jbrunet@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Russell King <linux@armlinux.org.uk>,
Linus Walleij <linus.walleij@linaro.org>,
Quentin Schulz <quentin.schulz@free-electrons.com>,
Kevin Hilman <khilman@baylibre.com>,
Peter De Schrijver" <pdeschrijver@nvidia.com>,
Chen-Yu Tsai <wens@csie.org>
Subject: Re: [PATCH v4 00/10] clk: implement clock rate protection mechanism
Date: Tue, 14 Nov 2017 10:04:25 +0100 [thread overview]
Message-ID: <20171114090425.blmrlpfwsvbviysc@flea.lan> (raw)
In-Reply-To: <1509615364.24591.23.camel@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
Hi Jerome,
Sorry for the delay.
On Thu, Nov 02, 2017 at 10:36:04AM +0100, Jerome Brunet wrote:
> On Thu, 2017-11-02 at 10:04 +0100, Maxime Ripard wrote:
> > Hi Mike,
> >
> > On Thu, Oct 26, 2017 at 07:29:25AM +0200, Michael Turquette wrote:
> > > Quoting Jerome Brunet (2017-09-24 22:00:20)
> > > > This Patchset is related the RFC [0] and the discussion around
> > > > CLK_SET_RATE_GATE available here [1]
> > >
> > > + Maxime & ChenYu
> > >
> > > Have you tested this latest version? If it works for you as expected,
> > > please feel free to add your Tested-by's.
> >
> > We were not in Cc on this one (obviously) and I'm not subscribed to
> > linux-clk, is there a git branch available somewhere so we can test?
>
> Here it is:
> https://github.com/jeromebrunet/linux/commits/amlogic/wip/clk-lock
>
> Happy testing !
I just tested your current branch (133a1f17e38d) and it works just
fine.
Tested-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2017-11-14 9:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 20:00 [PATCH v4 00/10] clk: implement clock rate protection mechanism Jerome Brunet
2017-09-24 20:00 ` [PATCH v4 01/10] clk: fix incorrect usage of ENOSYS Jerome Brunet
2017-09-24 20:00 ` [PATCH v4 02/10] clk: take the prepare lock out of clk_core_set_parent Jerome Brunet
2017-09-24 20:00 ` [PATCH v4 03/10] clk: add clk_core_set_phase_nolock function Jerome Brunet
2017-09-24 20:00 ` [PATCH v4 04/10] clk: rework calls to round and determine rate callbacks Jerome Brunet
2017-09-24 20:00 ` [PATCH v4 05/10] clk: use round rate to bail out early in set_rate Jerome Brunet
2017-09-24 20:00 ` [PATCH v4 06/10] clk: add clock protection mechanism to clk core Jerome Brunet
2017-09-24 20:00 ` [PATCH v4 07/10] clk: cosmetic changes to clk_summary debugfs entry Jerome Brunet
2017-09-24 20:00 ` [PATCH v4 08/10] clk: fix CLK_SET_RATE_GATE with clock rate protection Jerome Brunet
2017-09-24 20:00 ` [PATCH v4 09/10] clk: add clk_rate_exclusive api Jerome Brunet
2017-10-26 5:26 ` Michael Turquette
2017-10-31 17:29 ` Jerome Brunet
2017-10-31 17:32 ` Michael Turquette
2017-09-24 20:00 ` [PATCH v4 10/10] clk: fix set_rate_range when current rate is out of range Jerome Brunet
2017-10-26 5:29 ` [PATCH v4 00/10] clk: implement clock rate protection mechanism Michael Turquette
2017-11-02 9:04 ` Maxime Ripard
2017-11-02 9:36 ` Jerome Brunet
2017-11-14 9:04 ` Maxime Ripard [this message]
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=20171114090425.blmrlpfwsvbviysc@flea.lan \
--to=maxime.ripard@free-electrons.com \
--cc=jbrunet@baylibre.com \
--cc=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
--cc=sboyd@codeaurora.org \
--cc=wens@csie.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).