From: "Rajendra Nayak" <rnayak@codeaurora.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: santosh shilimkar <santosh.shilimkar@oracle.com>,
Kevin Hilman <khilman@kernel.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Santosh Shilimkar <ssantosh@kernel.org>,
Tony Lindgren <tony@atomide.com>, Sekhar Nori <nsekhar@ti.com>,
Magnus Damm <magnus.damm@gmail.com>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>
Subject: Re: [RFC 0/5] PM / clock_ops: provide default runtime ops and cleanup users
Date: Tue, 21 Apr 2015 08:56:49 -0000 [thread overview]
Message-ID: <775b18eaf35d4319ae4762098e558d1b.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <CAMuHMdX3-Ces57VcpyXEJBSUB07ZtpcCiN8ZpiStGcQnDEHt4A@mail.gmail.com>
> On Tue, Apr 21, 2015 at 1:25 AM, santosh shilimkar
> <santosh.shilimkar@oracle.com> wrote:
>> On 4/20/2015 4:21 PM, Kevin Hilman wrote:
>>>
>>> Rajendra Nayak <rnayak@codeaurora.org> writes:
>>>
>>>> Most users of PM clocks do the exact same thing in runtime callbacks.
>>>
>>>
>>> Probably because they were all copied from mach-davinci. ;)
>>>
>> Yep. ;-)
>
> If you're interested in the history, I did some digging last year:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2014-March/242352.html
>
>>>> Provide default callbacks and cleanup the existing users
>>>> (keystone/davinci/omap1/sh)
>>>
>>>
>>> Very nice cleanup, Thanks!
>
> Note that the new code always has a dev_pm_domain, while the old code had
> it
> conditionally on CONFIG_PM.
Right, but since USE_PM_CLK_RUNTIME_OPS is actually a nop with
!CONFIG_PM, we don't really need the checks anymore.
>
> I don't think that matters much, as we seem to be having more and more
> systems that rely on CONFIG_PM=y...
>
>>> For the series:
>>>
>>> Reviewed-by: Kevin Hilman <khilman@linaro.org>
>>>
>> Acked-by: Santosh Shilimkar <ssantosh@kernel.org>
>
> Looks good to me, and works fine on (pre-Clock Domain) r8a7791/koelsch
> and r8a7740/armadillo-legacy (with PM Domains, but still relying on the
> drivers/sh/pm_runtime.c hack for devices in the C5 "always on" domain).
>
> This code is no longer used in multiplatform kernels on shmobile boards
> with real PM Domains.
>
> Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>
Thanks,
Rajendra
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
> geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker.
> But
> when I'm talking to journalists I just say "programmer" or something like
> that.
> -- Linus Torvalds
>
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2015-04-21 8:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 13:34 [RFC 0/5] PM / clock_ops: provide default runtime ops and cleanup users Rajendra Nayak
2015-04-14 13:34 ` [RFC 1/5] PM / clock_ops: Provide default runtime ops to users Rajendra Nayak
2015-04-14 13:34 ` [RFC 2/5] arm: keystone: remove boilerplate code and use USE_PM_CLK_RUNTIME_OPS Rajendra Nayak
2015-04-14 13:34 ` [RFC 3/5] arm: omap1: " Rajendra Nayak
2015-04-14 13:34 ` [RFC 4/5] arm: davinci: " Rajendra Nayak
2015-04-14 13:34 ` [RFC 5/5] drivers: sh: " Rajendra Nayak
2015-04-20 23:21 ` [RFC 0/5] PM / clock_ops: provide default runtime ops and cleanup users Kevin Hilman
2015-04-20 23:25 ` santosh shilimkar
2015-04-21 8:01 ` Geert Uytterhoeven
2015-04-21 8:56 ` Rajendra Nayak [this message]
2015-04-21 9:04 ` Geert Uytterhoeven
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=775b18eaf35d4319ae4762098e558d1b.squirrel@www.codeaurora.org \
--to=rnayak@codeaurora.org \
--cc=geert@linux-m68k.org \
--cc=khilman@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=nsekhar@ti.com \
--cc=rjw@rjwysocki.net \
--cc=santosh.shilimkar@oracle.com \
--cc=ssantosh@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox