[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5710DA93.1020708@rock-chips.com>
Date: Fri, 15 Apr 2016 20:12:03 +0800
From: "David.Wu" <david.wu@...k-chips.com>
To: Heiko Stübner <heiko@...ech.de>,
Wolfram Sang <wsa@...-dreams.de>
Cc: 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
Hi Heiko,
在 2016/4/15 15:31, Heiko Stübner 写道:
> 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.
Okay, i will try it, thank you.
>
>
>
>
Powered by blists - more mailing lists