public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: david.wu@rock-chips•com (David.Wu)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v5 2/2] i2c: rk3x: add i2c support for rk3399 soc
Date: Fri, 15 Apr 2016 20:12:03 +0800	[thread overview]
Message-ID: <5710DA93.1020708@rock-chips.com> (raw)
In-Reply-To: <2530516.Iqqf6HUmr5@diego>

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.

>
>
>
>

  reply	other threads:[~2016-04-15 12:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16 16:57 [PATCH v5 0/2] updates for rk3399 i2c support David Wu
2016-03-16 16:57 ` [PATCH v5 1/2] i2c: rk3x: switch to i2c generic dt parsing David Wu
2016-04-14 18:39   ` Wolfram Sang
2016-03-16 16:57 ` [PATCH v5 2/2] i2c: rk3x: add i2c support for rk3399 soc David Wu
2016-04-14 18:48   ` Wolfram Sang
2016-04-15  7:31     ` Heiko Stübner
2016-04-15 12:12       ` David.Wu [this message]
2016-04-15 12:10     ` David.Wu
2016-04-15 17:58       ` Wolfram Sang
2016-04-18 13:15         ` David.Wu
2016-04-15 12:17   ` Heiko Stübner
2016-04-19 13:55   ` [PATCH v6] " David Wu
2016-04-21 22:00     ` Andy Shevchenko
2016-04-27 20:56     ` Doug Anderson
     [not found]       ` <572212AE.5060904@rock-chips.com>
2016-04-28 21:28         ` Doug Anderson

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=5710DA93.1020708@rock-chips.com \
    --to=david.wu@rock-chips$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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