From: Tero Kristo <t-kristo@ti.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>
Cc: <linux-omap@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] clk: ti: clk-7xx: Remove hardwired ABE clock configuration
Date: Fri, 25 Sep 2015 10:03:40 +0300 [thread overview]
Message-ID: <5604F1CC.5080809@ti.com> (raw)
In-Reply-To: <5604F0D8.60402@ti.com>
On 09/25/2015 09:59 AM, Peter Ujfalusi wrote:
> Tero,
>
> On 09/16/2015 09:42 AM, Tero Kristo wrote:
>> On 09/14/2015 11:52 AM, Peter Ujfalusi wrote:
>>> Hi Tero,
>>>
>>> On 08/24/2015 10:35 AM, Peter Ujfalusi wrote:
>>>> The ABE related clocks should be configured via DT and not have it wired
>>>> inside of the kernel.
>>>
>>> can you take a look at this patch? It will not cause any regression since we
>>> do not have audio support mainline and the pending series does not need this
>>> part anymore.
>>
>> This patch looks okay to me. So, you are saying this doesn't depend on
>> anything? Isn't this causing any boot-time issues with the ABE DPLL left
>> dangling with boot setup, potentially blocking PM? I am just wondering if we
>> should group this patch with the rest of the audio support patches for dra7.
>
> Without this patch the ABE DPLL will have frequency which is not going to be
> correct to be used with the ATL. The ATL is disabled by default and only
> enabled when we use the audio. Which is not the case w/o the other series.
>
Ok, queuing for 4.3-rc fixes.
-Tero
prev parent reply other threads:[~2015-09-25 7:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 7:35 [PATCH] clk: ti: clk-7xx: Remove hardwired ABE clock configuration Peter Ujfalusi
2015-09-14 8:52 ` Peter Ujfalusi
2015-09-16 6:42 ` Tero Kristo
2015-09-25 6:59 ` Peter Ujfalusi
2015-09-25 7:03 ` Tero Kristo [this message]
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=5604F1CC.5080809@ti.com \
--to=t-kristo@ti.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peter.ujfalusi@ti.com \
--cc=sboyd@codeaurora.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).