All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tero Kristo <t-kristo@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Mike Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Paul Walmsley <paul@pwsan.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	<linux-clk@vger.kernel.org>
Subject: Re: [GIT PULL] clk: ti: clock driver code migration to drivers
Date: Tue, 14 Jul 2015 13:32:00 +0300	[thread overview]
Message-ID: <55A4E520.8050804@ti.com> (raw)
In-Reply-To: <20150714095431.GJ17550@atomide.com>

On 07/14/2015 12:54 PM, Tony Lindgren wrote:
> * Tero Kristo <t-kristo@ti.com> [150714 01:56]:
>>
>> This pull request contains the TI clock driver set to move the clock
>> implementations under clock driver. Some small portions of the clock driver
>> code still remain under mach-omap2 after this, it should be decided whether
>> this code is now obsolete and should be deleted or should someone try to fix
>> it.
>
> Hmm care to clarify what is obsolete or broken after this series?

Not after this series, was broken/obsolete already before.

A couple of omap2/omap3 specific clock files still remain under 
mach-omap2, they are DVFS related. OMAP3 core dvfs support is currently 
completely unused (this could probably be removed, or shall we 
re-introduce the painful core dvfs at some point again?), and parts of 
the omap2 core dpll handling code should probably be re-written; or at 
least verified that it actually works properly. I can't test OMAP2 DVFS 
myself so don't dare to fiddle with it.... I could probably try to get 
some sort of DVFS test case to work on the board farm OMAP2 board I have 
access to though, I can investigate this.

> And I take it's not obsolete or broken because of this series? :)

No, this series does not touch the above mentioned pieces of code, so 
this definitely should not break anything. :)

-Tero

>
> Also, I just gave this branch a quick boot test and it seems to
> behave for me.
>
> Regards,
>
> Tony
>

  reply	other threads:[~2015-07-14 10:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14  8:54 [GIT PULL] clk: ti: clock driver code migration to drivers Tero Kristo
2015-07-14  9:54 ` Tony Lindgren
2015-07-14 10:32   ` Tero Kristo [this message]
2015-07-14 10:40     ` Tony Lindgren
2015-07-16  1:51       ` Paul Walmsley
2015-07-16  6:02         ` Tero Kristo
2015-07-24  0:37       ` Michael Turquette
2015-07-14 19:29 ` Stephen Boyd
2015-07-14 20:09   ` Tero Kristo
2015-07-14 20:31     ` Stephen Boyd
2015-07-15 11:44       ` 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=55A4E520.8050804@ti.com \
    --to=t-kristo@ti.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=paul@pwsan.com \
    --cc=sboyd@codeaurora.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.