From: Wolfram Sang <wsa@the-dreams.de>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Peter Korsgaard <peter@korsgaard.com>,
Peter Korsgaard <jacmet@sunsite.dk>,
linux-i2c@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i2c-ocores: add common clock support
Date: Thu, 22 Jan 2015 21:41:47 +0100 [thread overview]
Message-ID: <20150122204147.GA16770@katana> (raw)
In-Reply-To: <CAMo8BfJCPQWa-AGODDO5o2XZU3d-BbaxjSSG9SOoMzoXpYtr-A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]
On Thu, Jan 22, 2015 at 11:36:25PM +0300, Max Filippov wrote:
> On Thu, Jan 22, 2015 at 9:57 PM, Wolfram Sang <wsa@the-dreams.de> wrote:
> > 2?) a new binding is present to specify the IP clock speed:
> > - is this needed? is somebody using the driver without CCF?
> > - if so, the new binding is parsed and evaluated
> > - I couldn't find an existing binding to specify a clock speed.
> > Please have a look, too. Otherwise we need to introduce sth
> > like "opencores,ip-clock-khz" probably.
> > - "clock-frequency" is describing the bus speed as usual
>
> ePAPR document says that clock-frequency 'specifies the frequency
> of a clock in Hz', not identifying which clock. Outside i2c drivers
> subtree it is commonly used to specify input clock frequency of IP
> blocks, even for bus controllers, e.g. SPI.
I know; it was established in I2C this way before I took over.
I don't think it is a good idea to change that.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-01-22 20:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 10:21 [PATCH] i2c-ocores: add common clock support Max Filippov
[not found] ` <1421230899-7843-1-git-send-email-jcmvbkbc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-16 22:36 ` Peter Korsgaard
2015-01-16 22:36 ` Peter Korsgaard
2015-01-22 14:45 ` Wolfram Sang
2015-01-22 15:01 ` Max Filippov
2015-01-22 15:01 ` Max Filippov
[not found] ` <CAMo8Bf+XJY_bY+OB2i_SZQmAavwERG39BR8FVj202V-E3UidPg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-22 15:07 ` Wolfram Sang
2015-01-22 15:07 ` Wolfram Sang
2015-01-22 18:28 ` Peter Korsgaard
2015-01-22 18:28 ` Peter Korsgaard
2015-01-22 18:57 ` Wolfram Sang
2015-01-22 19:15 ` Max Filippov
2015-01-22 19:15 ` Max Filippov
[not found] ` <CAMo8BfJdmB-=i4bJypHzGvegxgBPafpiT_hyQXLhvzBUmE+u_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-22 19:26 ` Wolfram Sang
2015-01-22 19:26 ` Wolfram Sang
2015-01-22 20:53 ` Max Filippov
2015-01-22 20:53 ` Max Filippov
[not found] ` <CAMo8BfJqS1O=ZiVs89wsuNuQ_Qt=2BJtcens=09POucM_OjXrQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-22 23:21 ` Wolfram Sang
2015-01-22 23:21 ` Wolfram Sang
2015-01-22 20:36 ` Max Filippov
2015-01-22 20:36 ` Max Filippov
2015-01-22 20:41 ` Wolfram Sang [this message]
2015-01-22 15:21 ` Peter Korsgaard
2015-01-22 15:21 ` Peter Korsgaard
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=20150122204147.GA16770@katana \
--to=wsa@the-dreams.de \
--cc=jacmet@sunsite.dk \
--cc=jcmvbkbc@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@korsgaard.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.