From: Tero Kristo <t-kristo@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Paul Walmsley <paul@pwsan.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: OMAP3: clock: remove un-used core dpll re-program code
Date: Wed, 14 Oct 2015 14:50:00 +0300 [thread overview]
Message-ID: <561E4168.3050508@ti.com> (raw)
In-Reply-To: <20151012170141.GE23801@atomide.com>
On 10/12/2015 08:01 PM, Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [150812 03:59]:
>> * Tony Lindgren <tony@atomide.com> [150812 00:29]:
>>> * Tero Kristo <t-kristo@ti.com> [150716 01:10]:
>>>> Remove the OMAP3 core DPLL re-program code, and the associated SRAM
>>>> code that does the low-level programming of the DPLL divider, idling
>>>> of the SDRAM etc.
>>>>
>>>> This code was never fully implemented in the kernel; things missing
>>>> were driver side handling of core clock changes (they need to account
>>>> for their functional clock rate being changed on-the-fly), and the whole
>>>> framework required for handling this. Thus, there is not much point
>>>> to keep carrying the low-level support code either.
>>>
>>> OK I'm applying this into omap-for-v4.3/soc. If we ever need the code
>>> it will be in the git history.
>>
>> Actually I'll wait on this one and apply it later on as it currently
>> adds merge conflicts into Linux next.
>
> Looks like this needs to be updated to apply on v4.3-rc4, can you
> please repost?
Ok, just posted it.
-Tero
>
> Using v4.3-rc4 as the base for v4.4 because it contains most of the
> mmc fixes.
>
> Regards,
>
> Tony
>
prev parent reply other threads:[~2015-10-14 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 8:08 [PATCH] ARM: OMAP3: clock: remove un-used core dpll re-program code Tero Kristo
2015-08-12 7:25 ` Tony Lindgren
2015-08-12 10:56 ` Tony Lindgren
2015-10-12 17:01 ` Tony Lindgren
2015-10-14 11:50 ` 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=561E4168.3050508@ti.com \
--to=t-kristo@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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;
as well as URLs for NNTP newsgroup(s).