From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Thu, 4 Jun 2015 08:44:34 +0200 From: Boris Brezillon To: Stephen Boyd Cc: Mike Turquette , linux-clk@vger.kernel.org, Mikko Perttunen , Tomeu Vizoso , Jonathan Corbet , Tony Lindgren , Ralf Baechle , Emilio L??pez , Maxime Ripard , Tero Kristo , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org, linux-mips@linux-mips.org Subject: Re: [PATCH v3] clk: change clk_ops' ->determine_rate() prototype Message-ID: <20150604084434.48939141@bbrezillon> In-Reply-To: <20150603233728.GA490@codeaurora.org> References: <1432138345-19044-1-git-send-email-boris.brezillon@free-electrons.com> <20150603233728.GA490@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 List-ID: Hi Stefen, On Wed, 3 Jun 2015 16:37:28 -0700 Stephen Boyd wrote: > On 05/20, Boris Brezillon wrote: > > Clock rates are stored in an unsigned long field, but ->determine_rate() > > (which returns a rounded rate from a requested one) returns a long > > value (errors are reported using negative error codes), which can lead > > to long overflow if the clock rate exceed 2Ghz. > >=20 > > Change ->determine_rate() prototype to return 0 or an error code, and p= ass > > a pointer to a clk_rate_request structure containing the expected target > > rate and the rate constraints imposed by clk users. > >=20 > > The clk_rate_request structure might be extended in the future to conta= in > > other kind of constraints like the rounding policy, the maximum clock > > inaccuracy or other things that are not yet supported by the CCF > > (power consumption constraints ?). > >=20 > > Signed-off-by: Boris Brezillon > >=20 > > CC: Jonathan Corbet > > CC: Tony Lindgren > > CC: Ralf Baechle > > CC: "Emilio L=C3=B3pez" > > CC: Maxime Ripard > > CC: Tero Kristo > > CC: linux-doc@vger.kernel.org > > CC: linux-kernel@vger.kernel.org > > CC: linux-arm-kernel@lists.infradead.org > > CC: linux-omap@vger.kernel.org > > CC: linux-mips@linux-mips.org > > --- > >=20 > > Hi Stephen, > >=20 > > This patch is based on clk-next and contains the changes you suggested > > in your previous review. > >=20 > > It was tested on sama5d4 and compile tested on several ARM platforms > > (those enabled in multi_v7_defconfig). > >=20 >=20 > Thanks. I think we should wait until the next -rc1 drops to apply the > patch for the next merge window. That will make it least likely to confli= ct > with other trees, and we can provide it on a stable branch should there > be clock providers going through other trees somewhere. Please > remind me if I forget. No problem. >=20 > > @@ -1186,15 +1191,21 @@ EXPORT_SYMBOL_GPL(__clk_determine_rate); > > */ > > unsigned long __clk_round_rate(struct clk *clk, unsigned long rate) > > { > > - unsigned long min_rate; > > - unsigned long max_rate; > > + > > + struct clk_rate_request req; > > + int ret; > > =20 > > if (!clk) > > return 0; > > =20 > > - clk_core_get_boundaries(clk->core, &min_rate, &max_rate); > > + clk_core_get_boundaries(clk->core, &req.min_rate, &req.max_rate); > > + req.rate =3D rate; > > + > > + ret =3D clk_core_round_rate_nolock(clk->core, &req); > > + if (ret) > > + return ret; >=20 > This returns a negative int for unsigned long. Is that intentional? Nope, should be replaced by 'return 0;'. Thanks, Boris --=20 Boris Brezillon, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com