From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5] clk: change clk_ops' ->determine_rate() prototype
Date: Tue, 14 Jul 2015 12:47:48 +0200 [thread overview]
Message-ID: <20150714124748.55dd6213@bbrezillon> (raw)
In-Reply-To: <20150713230217.GI30412@codeaurora.org>
On Mon, 13 Jul 2015 16:02:18 -0700
Stephen Boyd <sboyd@codeaurora.org> wrote:
> On 07/09, Boris Brezillon wrote:
> > Hi Stephen,
> >
> > On Wed, 08 Jul 2015 11:07:42 -0700
> > Stephen Boyd <sboyd@codeaurora.org> wrote:
> >
> > > On 07/08/2015 02:00 AM, Boris Brezillon wrote:
> > > > Hi Stephen,
> > > >
> > > > On Tue, 7 Jul 2015 17:57:48 -0700
> > > > Stephen Boyd <sboyd@codeaurora.org> wrote:
> > > >
> > > >> On 07/07, Boris Brezillon wrote:
> > > >>>
> > > >>> } else {
> > > >>> pr_err("clk: clk_composite_determine_rate function called, but no mux or rate callback set!\n");
> > > >>> + req->rate = 0;
> > > >>> return 0;
> > > >> Shouldn't this return an error now? And then assigning req->rate
> > > >> wouldn't be necessary. Sorry I must have missed this last round.
> > > >>
> > > > Actually I wanted to keep the existing behavior: return a 0 rate (not
> > > > an error) when there is no mux or rate ops.
> > > >
> > > > That's something we can change afterwards, but it might reveals
> > > > new bugs if some users are checking for a 0 rate to detect errors.
> > > >
> > >
> > > Ok. Care to send the patch now to do that while we're thinking about it?
> > > We can test it out for a month or two.
> > >
> >
> > Here is a patch modifying a few drivers to return errors instead of a 0
> > rate. Feel free to squash it in the previous one if you think this is
> > better.
> >
> > Best Regards,
> >
> > Boris
> >
> > --- >8 ---
> >
> > From dca9c28301042cf19dad4b1e4555cdb7c1063745 Mon Sep 17 00:00:00 2001
> > From: Boris Brezillon <boris.brezillon@free-electrons.com>
> > Date: Thu, 9 Jul 2015 12:20:21 +0200
> > Subject: [PATCH] clk: fix some determine_rate implementations
> >
> > Some determine_rate implementations are not returning an error when then
> > failed to adapt the rate according to the rate request.
> > Fix them so that they return an error instead of silently returning 0.
> >
> > Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
>
> The linewrap is seriously messed up here. Please fix your mailer
> next time. I had to hand edit the patch to get it to apply. I've
> applied this in top of the original patch as a different commit,
> in case we need to revert it later.
Sorry about that, I forgot to remove the line wrapper when copying the
content of the patch into my mailer :-/.
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-14 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 18:48 [PATCH v5] clk: change clk_ops' ->determine_rate() prototype Boris Brezillon
2015-07-08 0:57 ` Stephen Boyd
2015-07-08 9:00 ` Boris Brezillon
2015-07-08 18:07 ` Stephen Boyd
2015-07-09 20:39 ` Boris Brezillon
2015-07-13 23:02 ` Stephen Boyd
2015-07-14 10:47 ` Boris Brezillon [this message]
2015-07-13 9:01 ` Tero Kristo
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=20150714124748.55dd6213@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;
as well as URLs for NNTP newsgroup(s).