From: Stephen Boyd <sboyd@codeaurora.org>
To: Mason <slash.tmp@free.fr>
Cc: Michael Turquette <mturquette@baylibre.com>,
Sebastian Frias <sf84@laposte.net>,
clk <linux-clk@vger.kernel.org>
Subject: Re: [PATCH v3] clk: tango4: improve clkgen driver
Date: Mon, 2 May 2016 17:36:50 -0700 [thread overview]
Message-ID: <20160503003650.GF3492@codeaurora.org> (raw)
In-Reply-To: <5711F947.4010204@free.fr>
On 04/16, Mason wrote:
> On 16/04/2016 02:16, Stephen Boyd wrote:
>
> > Applied to clk-next
>
> Great! Thanks.
>
> Hopefully, I won't have to write any more clk code until Tango5.
>
> The last feature missing is support for fractional dividers.
> We discussed this back in March on IRC, and you mentioned
> "libifying" some parts of the code.
>
> Could you say a bit more to put me on the right track?
I mean that clk-fractional-divider.c can become more like
clk-divider.c and grow functions like
fractional_divider_round_rate(), fractional_divider_get_val(),
and fractional_divider_recalc_rate() that would parallel
divider_round_rate(), divider_get_val() and divider_recalc_rate()
respectively. If any sort of flags are needed to change rounding
behavior, etc. then a flags argument could be used similar to how
the divider code has one.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2016-05-03 0:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 16:58 [PATCH RFC] tango4 clk rewrite Mason
2016-02-25 22:08 ` Stephen Boyd
2016-02-26 10:51 ` Mason
2016-02-26 14:52 ` [PATCH v2] clk: tango4: improve clkgen driver Mason
2016-04-04 9:21 ` [PATCH v3] " Mason
2016-04-13 20:44 ` Mason
2016-04-16 0:16 ` Stephen Boyd
2016-04-16 8:35 ` Mason
2016-05-03 0:36 ` Stephen Boyd [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=20160503003650.GF3492@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sf84@laposte.net \
--cc=slash.tmp@free.fr \
/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).