From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] clk: change clk_ops' ->round_rate() prototype
Date: Fri, 5 Jun 2015 13:38:03 +0200 [thread overview]
Message-ID: <20150605133803.59990a66@bbrezillon> (raw)
In-Reply-To: <alpine.DEB.2.02.1506042258530.12316@utopia.booyaka.com>
Hi Paul,
On Thu, 4 Jun 2015 23:02:25 +0000 (UTC)
Paul Walmsley <paul@pwsan.com> wrote:
> Hi folks
>
> just a brief comment on this one:
>
> On Thu, 30 Apr 2015, Boris Brezillon wrote:
>
> > Clock rates are stored in an unsigned long field, but ->round_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.
> >
> > Change ->round_rate() prototype to return 0 or an error code, and pass the
> > requested rate as a pointer so that it can be adjusted depending on
> > hardware capabilities.
>
> ...
>
> > diff --git a/Documentation/clk.txt b/Documentation/clk.txt
> > index 0e4f90a..fca8b7a 100644
> > --- a/Documentation/clk.txt
> > +++ b/Documentation/clk.txt
> > @@ -68,8 +68,8 @@ the operations defined in clk.h:
> > int (*is_enabled)(struct clk_hw *hw);
> > unsigned long (*recalc_rate)(struct clk_hw *hw,
> > unsigned long parent_rate);
> > - long (*round_rate)(struct clk_hw *hw,
> > - unsigned long rate,
> > + int (*round_rate)(struct clk_hw *hw,
> > + unsigned long *rate,
> > unsigned long *parent_rate);
> > long (*determine_rate)(struct clk_hw *hw,
> > unsigned long rate,
>
> I'd suggest that we should probably go straight to 64-bit rates. There
> are already plenty of clock sources that can generate rates higher than
> 4GiHz.
Yep, that was something I was considering too. If Stephen agrees I'll
change that in the next version.
BTW, you're referring to the second version of this patch, but things
have changed a bit: Stephen recommended to only modify the
->determine_rate() prototype and pass a structure instead of a list of
arguments.
Here is the last version of this series [1].
Best Regards,
Boris
[1]http://patchwork.linux-mips.org/patch/10092/
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-06-05 11:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 15:30 [PATCH v2 0/2] clk: adapt ->round_rate()/->determine_rate() prototypes Boris Brezillon
2015-04-30 15:30 ` [PATCH v2 1/2] clk: change clk_ops' ->round_rate() prototype Boris Brezillon
2015-05-07 6:39 ` Stephen Boyd
2015-05-07 7:37 ` Boris Brezillon
2015-05-15 15:40 ` Boris Brezillon
2015-05-16 11:14 ` Mikko Perttunen
2015-05-20 1:01 ` Stephen Boyd
2015-06-04 23:02 ` Paul Walmsley
2015-06-05 8:46 ` Jon Hunter
2015-06-05 11:39 ` Boris Brezillon
2015-06-08 8:46 ` Jon Hunter
[not found] ` <20150610030254.6017.98627@quantum>
2015-06-10 7:00 ` Boris Brezillon
2015-06-05 11:38 ` Boris Brezillon [this message]
2015-04-30 15:30 ` [PATCH v2 2/2] clk: change clk_ops' ->determine_rate() prototype Boris Brezillon
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=20150605133803.59990a66@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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