From: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
To: Mike Turquette <mturquette@linaro.org>,
dbaryshkov@gmail.com, dwmw2@infradead.org, lee.jones@linaro.org,
santosh.shilimkar@ti.com, arnd@arndb.de, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
grant.likely@linaro.org
Cc: rdunlap@infradead.org, linux@arm.linux.org.uk,
grygorii.strashko@ti.com, olof@lixom.net, w-kwok2@ti.com,
sboyd@codeaurora.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, m-karicheri2@ti.com,
sergei.shtylyov@cogentembedded.com
Subject: Re: [Patch v7 2/7] clock: keystone-pllctrl: add bindings for keystone pll controller
Date: Fri, 23 May 2014 21:41:28 +0300 [thread overview]
Message-ID: <537F9658.1040507@ti.com> (raw)
In-Reply-To: <20140523183218.23136.51518@quantum>
On 05/23/2014 09:32 PM, Mike Turquette wrote:
> Quoting Ivan Khoronzhuk (2014-05-23 08:43:27)
>> The main pll controller used to drive theC66x CorePacs, the switch fabric,
>> and a majority of the peripheral clocks (all but the ARM CorePacs, DDR3 and
>> the NETCP modules) requires a PLL Controller to manage the various clock
>> divisions, gating, and synchronization.
>>
>> Reviewed-by: Arnd Bergmann <arnd@arndb.de>
>> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
> Acked-by: Mike Turquette <mturquette@linaro.org>
>
> Regards,
> Mike
Thanks!
--
Regards,
Ivan Khoronzhuk
next prev parent reply other threads:[~2014-05-23 18:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 15:43 [Patch v7 0/7] Introduce keystone reset driver Ivan Khoronzhuk
2014-05-23 15:43 ` [Patch v7 1/7] power: reset: keystone-reset: introduce " Ivan Khoronzhuk
2014-05-23 15:43 ` [Patch v7 2/7] clock: keystone-pllctrl: add bindings for keystone pll controller Ivan Khoronzhuk
2014-05-23 18:32 ` Mike Turquette
2014-05-23 18:35 ` Santosh Shilimkar
2014-05-23 18:41 ` Ivan Khoronzhuk [this message]
2014-05-23 15:43 ` [Patch v7 3/7] mfd: ti-keystone-devctrl: add bindings for device state control Ivan Khoronzhuk
2014-05-27 9:24 ` Lee Jones
2014-05-23 15:43 ` [Patch v7 4/7] power: reset: add bindings for keystone reset driver Ivan Khoronzhuk
2014-05-23 15:43 ` [Patch v7 5/7] ARM: keystone: remove redundant reset stuff Ivan Khoronzhuk
2014-05-23 15:43 ` [Patch v7 6/7] ARM: dts: keystone: update reset node to work with reset driver Ivan Khoronzhuk
2014-05-23 15:43 ` [Patch v7 7/7] ARM: keystone: enable reset driver support Ivan Khoronzhuk
2014-05-23 21:28 ` [Patch v7 0/7] Introduce keystone reset driver Santosh Shilimkar
2014-05-23 21:38 ` Ivan Khoronzhuk
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=537F9658.1040507@ti.com \
--to=ivan.khoronzhuk@ti.com \
--cc=arnd@arndb.de \
--cc=dbaryshkov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=grygorii.strashko@ti.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m-karicheri2@ti.com \
--cc=mark.rutland@arm.com \
--cc=mturquette@linaro.org \
--cc=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=sboyd@codeaurora.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=w-kwok2@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).