[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <C7AA677C-664F-4305-B74D-B13F3FF0A199@gmail.com>
Date: Fri, 29 Dec 2017 11:52:38 +0300
From: Alexander Kochetkov <al.kochet@...il.com>
To: Stephen Boyd <sboyd@...eaurora.org>
Cc: linux-clk@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
LAK <linux-arm-kernel@...ts.infradead.org>,
linux-rockchip@...ts.infradead.org,
Michael Turquette <mturquette@...libre.com>,
Heiko Stuebner <heiko@...ech.de>,
Elaine Zhang <zhangqing@...k-chips.com>
Subject: Re: [PATCH 1/2] clk: rename clk_core_get_boundaries() to clk_hw_get_boundaries() and expose
> 29 дек. 2017 г., в 3:14, Stephen Boyd <sboyd@...eaurora.org> написал(а):
>
> I'm asking if the rate is capped on the consumer side with
> clk_set_max_rate() or if it's capped on the clk provider side to
> express a hardware constraint.
I do that using clk_set_max_rate() at provider size inside clk-rk3188.c.
>
> Sounds like there are some things to be figured out here still. I
> can take a closer look next week. Maybe Heiko will respond before
> then.
I will be very grateful for the ideas. I can continue to work on this next
week too.
Happy New Year and Merry Christmas!
Regards,
Alexander.
Powered by blists - more mailing lists