[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=VjgO=4j+5=yC+THE2hWM_zSXhyvo22oHHXOjm98LkaAA@mail.gmail.com>
Date: Tue, 7 Oct 2014 09:56:32 -0700
From: Doug Anderson <dianders@...omium.org>
To: Kever Yang <kever.yang@...k-chips.com>
Cc: Heiko Stübner <heiko@...ech.de>,
Mike Turquette <mturquette@...aro.org>,
Sonny Rao <sonnyrao@...omium.org>,
Addy Ke <addy.ke@...k-chips.com>,
Eddie Cai <cf@...k-chips.com>, Jianqun Xu <xjq@...k-chips.com>,
han jiang <hj@...k-chips.com>,
Tao Huang <huangtao@...k-chips.com>,
戴克霖 (Jack) <dkl@...k-chips.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
linux-rockchip@...ts.infradead.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] clk: rockchip: add 400MHz and 500MHz for rk3288 clock rate
Kever,
On Tue, Oct 7, 2014 at 2:33 AM, Kever Yang <kever.yang@...k-chips.com> wrote:
> This patch add 400MHz and 500MHz to clock rate table for rk3288.
>
> Signed-off-by: Kever Yang <kever.yang@...k-chips.com>
> ---
>
> drivers/clk/rockchip/clk-rk3288.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/clk/rockchip/clk-rk3288.c b/drivers/clk/rockchip/clk-rk3288.c
> index d053529..f6ea9c6 100644
> --- a/drivers/clk/rockchip/clk-rk3288.c
> +++ b/drivers/clk/rockchip/clk-rk3288.c
> @@ -86,8 +86,10 @@ struct rockchip_pll_rate_table rk3288_pll_rates[] = {
> RK3066_PLL_RATE( 594000000, 2, 198, 4),
> RK3066_PLL_RATE( 552000000, 1, 46, 2),
> RK3066_PLL_RATE( 504000000, 1, 84, 4),
> + RK3066_PLL_RATE( 500000000, 3, 125, 2),
> RK3066_PLL_RATE( 456000000, 1, 76, 4),
> RK3066_PLL_RATE( 408000000, 1, 68, 4),
> + RK3066_PLL_RATE( 400000000, 3, 50, 1),
This violates the constraints in the TRM. That says:
Fvco = (Fin/NR)*NF value range requirement: 440MHz – 2200MHz
I believe you end up with 400Mhz, not 440. Are you aware of this? Is
there some reason it's OK to violate the TRM in this case?
-Doug
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists