From: "Heiko Stübner" <heiko@sntech.de>
To: Mike Turquette <mturquette@linaro.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Seungwon Jeon <tgih.jun@samsung.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Chris Ball <cjb@laptop.org>,
linux-mmc@vger.kernel.org, Grant Likely <grant.likely@linaro.org>,
Rob Herring <rob.herring@calxeda.com>,
Linus Walleij <linus.walleij@linaro.org>,
devicetree-discuss@lists.ozlabs.org,
Russell King <linux@arm.linux.org.uk>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH v3 1/7] clk: divider: add flag to limit possible dividers to even numbers
Date: Tue, 11 Jun 2013 21:23:50 +0200 [thread overview]
Message-ID: <201306112123.51843.heiko@sntech.de> (raw)
In-Reply-To: <20130611185750.8816.82691@quantum>
Am Dienstag, 11. Juni 2013, 20:57:50 schrieb Mike Turquette:
> Quoting Heiko Stübner (2013-06-11 04:29:32)
>
> > SoCs like the Rockchip Cortex-A9 ones contain divider some clocks
> > that use the regular mechanisms for storage but allow only even
> > dividers and 1 to be used.
> >
> > Therefore add a flag that lets _is_valid_div limit the valid dividers
> > to these values. _get_maxdiv is also adapted to return even values
> > for the CLK_DIVIDER_ONE_BASED case.
> >
> > Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> > ---
> >
> > drivers/clk/clk-divider.c | 14 ++++++++++++--
> > include/linux/clk-provider.h | 2 ++
> > 2 files changed, 14 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/clk/clk-divider.c b/drivers/clk/clk-divider.c
> > index ce5cfe9..bdee7cf 100644
> > --- a/drivers/clk/clk-divider.c
> > +++ b/drivers/clk/clk-divider.c
> > @@ -45,8 +45,16 @@ static unsigned int _get_table_maxdiv(const struct
> > clk_div_table *table)
> >
> > static unsigned int _get_maxdiv(struct clk_divider *divider)
> > {
> >
> > - if (divider->flags & CLK_DIVIDER_ONE_BASED)
> > - return div_mask(divider);
> > + if (divider->flags & CLK_DIVIDER_ONE_BASED) {
> > + unsigned int div = div_mask(divider);
> > +
> > + /* decrease to even number */
> > + if (divider->flags & CLK_DIVIDER_EVEN)
> > + div--;
> > +
> > + return div;
> > + }
> > +
> >
> > if (divider->flags & CLK_DIVIDER_POWER_OF_TWO)
> >
> > return 1 << div_mask(divider);
> >
> > if (divider->table)
> >
> > @@ -141,6 +149,8 @@ static bool _is_valid_div(struct clk_divider
> > *divider, unsigned int div)
> >
> > return is_power_of_2(div);
> >
> > if (divider->table)
> >
> > return _is_valid_table_div(divider->table, div);
> >
> > + if (divider->flags & CLK_DIVIDER_EVEN && div != 1 && (div % 2) !=
> > 0)
>
> Is it correct to check for 'div != 1' here? Wouldn't that check only be
> valid in the presence of CLK_DIVIDER_ONE_BASED?
>
> Maybe something like this would be more correct:
>
> if (divider->flags & CLK_DIVIDER_EVEN && (div % 2) != 0) {
> if (divider->flags & CLK_DIVIDER_ONE_BASED && div == 1)
> return true;
> return false;
> }
hmm, not necessarily. As I understand the doc DIVIDER_ONE_BASED describes how
the divider is stored in the register, i.e. if the register value is div-1 or
div.
When div is 1, it of course means don't divide [rate/1], and CLK_DIVIDER_EVEN
needs to just make sure that bigger dividers that really divide the rate are
even values (so limiting the possible dividers to 1 2 4 ...), independent on
how the divider value is stored in the register.
next prev parent reply other threads:[~2013-06-11 19:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 11:28 [PATCH v3 0/7] arm: add basic support for Rockchip Cortex-A9 SoCs Heiko Stübner
2013-06-11 11:29 ` [PATCH v3 1/7] clk: divider: add flag to limit possible dividers to even numbers Heiko Stübner
2013-06-11 11:51 ` Andy Shevchenko
2013-06-11 12:06 ` Heiko Stübner
2013-06-11 12:37 ` Andy Shevchenko
2013-06-11 12:39 ` Andy Shevchenko
2013-06-11 18:57 ` Mike Turquette
2013-06-11 19:23 ` Heiko Stübner [this message]
2013-06-11 11:29 ` [PATCH v3 2/7] mmc: dw_mmc-pltfm: remove static from dw_mci_pltfm_remove Heiko Stübner
2013-06-11 11:30 ` [PATCH v3 3/7] mmc: dw_mmc-pltfm: move probe and remove below dt match table Heiko Stübner
2013-06-12 1:16 ` Seungwon Jeon
2013-06-11 11:30 ` [PATCH v3 4/7] mmc: dw_mmc-pltfm: add Rockchip variant Heiko Stübner
2013-06-12 1:22 ` Seungwon Jeon
2013-06-11 11:31 ` [PATCH v3 5/7] clk: add basic Rockchip rk3066a clock support Heiko Stübner
2013-06-11 20:06 ` Mike Turquette
2013-06-12 22:45 ` Heiko Stübner
2013-06-12 23:02 ` Olof Johansson
2013-06-12 23:40 ` Heiko Stübner
2013-06-11 11:32 ` [PATCH v3 6/7] arm: add debug uarts for rockchip rk29xx and rk3xxx series Heiko Stübner
2013-06-11 11:32 ` [PATCH v3 7/7] arm: add basic support for Rockchip RK3066a boards Heiko Stübner
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=201306112123.51843.heiko@sntech.de \
--to=heiko@sntech.de \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=cjb@laptop.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@linaro.org \
--cc=jh80.chung@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mturquette@linaro.org \
--cc=olof@lixom.net \
--cc=rob.herring@calxeda.com \
--cc=tgih.jun@samsung.com \
--cc=thomas.petazzoni@free-electrons.com \
/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
Powered by JetHome