From: santosh shilimkar <santosh.shilimkar@oracle.com>
To: Michael Turquette <mturquette@linaro.org>,
Murali Karicheri <m-karicheri2@ti.com>,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
ssantosh@kernel.org, sboyd@codeaurora.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org, linux@arm.linux.org.uk,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] clk: keystone: add support for post divider register for main pll
Date: Thu, 18 Jun 2015 15:55:32 -0700 [thread overview]
Message-ID: <55834C64.6020703@oracle.com> (raw)
In-Reply-To: <20150618223728.9112.75331@quantum>
On 6/18/2015 3:37 PM, Michael Turquette wrote:
> Quoting Murali Karicheri (2015-05-29 09:04:12)
>> Main PLL controller has post divider bits in a separate register in
>> pll controller. Use the value from this register instead of fixed
>> divider when available.
>>
>> Signed-off-by: Murali Karicheri <m-karicheri2@ti.com>
>
> Applied to clk-next.
>
Thanks Mike !!
next prev parent reply other threads:[~2015-06-18 22:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 16:04 [PATCH 1/2] clk: keystone: add support for post divider register for main pll Murali Karicheri
[not found] ` <1432915453-409-1-git-send-email-m-karicheri2-l0cyMroinI0@public.gmane.org>
2015-05-29 16:04 ` [PATCH 2/2] ARM: dts: keystone: fix dt bindings to use post div register for mainpll Murali Karicheri
2015-07-31 14:20 ` Murali Karicheri
2015-07-31 15:30 ` santosh shilimkar
2015-07-31 15:30 ` santosh shilimkar
2015-07-31 20:30 ` Olof Johansson
2015-07-31 22:06 ` santosh.shilimkar
2015-06-09 15:25 ` [PATCH 1/2] clk: keystone: add support for post divider register for main pll Murali Karicheri
2015-06-15 16:26 ` Murali Karicheri
2015-06-18 22:37 ` Michael Turquette
2015-06-18 22:55 ` santosh shilimkar [this message]
[not found] ` <55834C64.6020703-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2015-06-22 20:15 ` Murali Karicheri
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=55834C64.6020703@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@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=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=ssantosh@kernel.org \
/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).