[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMo8BfJCPQWa-AGODDO5o2XZU3d-BbaxjSSG9SOoMzoXpYtr-A@mail.gmail.com>
Date: Thu, 22 Jan 2015 23:36:25 +0300
From: Max Filippov <jcmvbkbc@...il.com>
To: Wolfram Sang <wsa@...-dreams.de>
Cc: Peter Korsgaard <peter@...sgaard.com>,
Peter Korsgaard <jacmet@...site.dk>, linux-i2c@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] i2c-ocores: add common clock support
On Thu, Jan 22, 2015 at 9:57 PM, Wolfram Sang <wsa@...-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.
--
Thanks.
-- Max
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists