From: Tero Kristo <t-kristo@ti.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>,
Mike Turquette <mturquette@linaro.org>
Cc: Tony Lindgren <tony@atomide.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] clk: ti: clk-7xx: Correct ABE DPLL configuration
Date: Wed, 30 Jul 2014 15:27:07 +0300 [thread overview]
Message-ID: <53D8E49B.3040600@ti.com> (raw)
In-Reply-To: <53D8886A.5020600@ti.com>
On 07/30/2014 08:53 AM, Peter Ujfalusi wrote:
> On 07/29/2014 07:12 PM, Mike Turquette wrote:
>>> Oh yea, seems this got lost into the myriad of branches I have. I can push
>>> this on top of my for-v3.17/ti-clk-drv if you like.
>>
>> That is the easiest thing for me. I think that Peter wanted to take
>> this as a fix for 3.16 though. Peter is that correct?
>
> Yes, it would have been better to have it in 3.16 along with the DRA7 ATL
> clock driver. W/O this patch the ATL will not going to be usable since the ABE
> DPLL is set too high to be usable for it's purpose.
>
Ok, this is now pushed on top of the for-v3.17/ti-clk-driver branch in
my git-repo. Mike, do you want a new pull-req for this just in case?
-Tero
next prev parent reply other threads:[~2014-07-30 12:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 13:48 [PATCH] clk: ti: clk-7xx: Correct ABE DPLL configuration Peter Ujfalusi
2014-04-02 14:12 ` Tero Kristo
2014-04-03 6:29 ` Peter Ujfalusi
2014-04-24 9:11 ` Peter Ujfalusi
2014-04-24 15:03 ` Tero Kristo
2014-05-06 13:39 ` Peter Ujfalusi
2014-05-19 12:29 ` Tero Kristo
2014-07-14 10:10 ` Peter Ujfalusi
2014-07-29 6:27 ` Mike Turquette
2014-07-29 8:23 ` Tero Kristo
2014-07-29 16:12 ` Mike Turquette
2014-07-30 5:53 ` Peter Ujfalusi
2014-07-30 12:27 ` Tero Kristo [this message]
2014-07-30 22:42 ` Mike Turquette
2014-07-31 6:37 ` Tero Kristo
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=53D8E49B.3040600@ti.com \
--to=t-kristo@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=peter.ujfalusi@ti.com \
--cc=tony@atomide.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