[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2530516.Iqqf6HUmr5@diego>
Date: Fri, 15 Apr 2016 09:31:55 +0200
From: Heiko Stübner <heiko@...ech.de>
To: Wolfram Sang <wsa@...-dreams.de>
Cc: David Wu <david.wu@...k-chips.com>, dianders@...omium.org,
andy.shevchenko@...il.com, huangtao@...k-chips.com,
hl@...k-chips.com, xjq@...k-chips.com, zyw@...k-chips.com,
cf@...k-chips.com, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-i2c@...r.kernel.org,
linux-kernel@...r.kernel.org, David Wu <wdc@...k-chips.com>
Subject: Re: [PATCH v5 2/2] i2c: rk3x: add i2c support for rk3399 soc
David,
Am Donnerstag, 14. April 2016, 20:48:48 schrieb Wolfram Sang:
> > + - input-clk-rate : frequency rate of function clock used(in Hz). If
> > omitted, + the default clock rate is used. It is just used at rk3399 soc.
>
> Why is this needed? Why don't we simply use the default or calculate the
> best value somehow?
if you need to _get_ the clock-rate, clk_get_rate is the abvious choice and if
you need to _set_ some specific rate, I guess it should be done via the
assigned-clocks mechanism in the devicetree - see veyron dts files that already
do this for some other parts.
Powered by blists - more mailing lists