From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [ PATCH v2 00/17] ARM: shmobile: Enable drivers/sh/pm_runtime.c on multi-platform
Date: Wed, 16 Apr 2014 07:53:01 +0000 [thread overview]
Message-ID: <20140416075301.GD12344@verge.net.au> (raw)
In-Reply-To: <1397565253-22741-1-git-send-email-geert+renesas@glider.be>
On Wed, Apr 16, 2014 at 09:15:35AM +0200, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Wed, Apr 16, 2014 at 2:18 AM, Simon Horman <horms@verge.net.au> wrote:
> >> > This patchset enables the PM runtime code in drivers/sh/pm_runtime.c when
> >> > running a multi-platform ARM kernel including support for shmobile.
> >> > Before this code was only enabled for legacy shmobile kernels, leading to
> >> > disabled clocks in multiplatform kernels, depending on implicit reset state
> >> > or on the bootloader.
> >> > It also contains some related cleanups, and removals of workarounds.
> >
> > I am wondering what kind of overhead this introduces for non shmobile
> > platforms that use a kernel compiled with ARCH_SHMOBILE_MULTI enabled.
>
> The only overhead for non-shmobile platforms is the compilation of the code,
> and the late_initcall(sh_pm_runtime_late_init), which will return immediately.
> It's not enabled unless called from a shmobile .init_machine.
Thanks, that sounds entirely reasonable to me.
next prev parent reply other threads:[~2014-04-16 7:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 12:33 [ PATCH v2 00/17] ARM: shmobile: Enable drivers/sh/pm_runtime.c on multi-platform Geert Uytterhoeven
2014-04-15 14:49 ` Laurent Pinchart
2014-04-15 15:52 ` Geert Uytterhoeven
2014-04-16 0:18 ` Simon Horman
2014-04-16 1:02 ` Simon Horman
2014-04-16 7:15 ` Geert Uytterhoeven
2014-04-16 7:53 ` Simon Horman [this message]
2014-04-25 16:55 ` 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=20140416075301.GD12344@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@vger.kernel.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 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.