From: treding@nvidia.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] ARM: Availability of psci_smp_available depends on CONFIG_SMP
Date: Thu, 8 Oct 2015 18:04:29 +0200 [thread overview]
Message-ID: <20151008160427.GA29417@ulmo.nvidia.com> (raw)
In-Reply-To: <20151006151857.GA2416@arm.com>
On Tue, Oct 06, 2015 at 04:18:58PM +0100, Will Deacon wrote:
> On Tue, Oct 06, 2015 at 10:11:24AM +0200, Thierry Reding wrote:
> > On Wed, Sep 23, 2015 at 08:39:43AM +0200, Jan Kiszka wrote:
> > > Ensure that we can use psci_smp_available without checking for
> > > CONFIG_SMP first.
> > >
> > > Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> > > ---
> > > arch/arm/include/asm/psci.h | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/arch/arm/include/asm/psci.h b/arch/arm/include/asm/psci.h
> > > index 68ee3ce..ff956f4 100644
> > > --- a/arch/arm/include/asm/psci.h
> > > +++ b/arch/arm/include/asm/psci.h
> > > @@ -16,7 +16,7 @@
> > >
> > > extern struct smp_operations psci_smp_ops;
> > >
> > > -#ifdef CONFIG_ARM_PSCI
> > > +#if defined(CONFIG_ARM_PSCI) && defined(CONFIG_SMP)
> > > bool psci_smp_available(void);
> > > #else
> > > static inline bool psci_smp_available(void) { return false; }
> >
> > Hi Will,
>
> Hi Thierry,
>
> > you had questions about this when this was first submitted back in
> > May[0], but discussion stalled. Can you take another look, please?
> >
> > I think irrespective of what the series is trying to do this is a
> > correct fix. The arch/arm/kernel/psci_smp.c file is only compiled if
> > both ARM_PSCI and SMP are selected. Builds break if we don't mirror
> > that conditional in the header because for ARM_PSCI && !SMP no dummy
> > will be defined, but the implementation for the prototype won't be
> > available either, leading to a linker error.
>
> Sure, I'm fine with this patch in isolation, I just didn't (don't) fully
> grok what the series is trying to achieve.
The goal is to prevent the kernel from registering a CPU idle driver if
PSCI is going to be used for SMP. This is necessary because both the CPU
idle driver and the PSCI implementation (provided by U-Boot in this
case) access the same resources. The effect of having both enabled is
usually that the system will simply hang sometime during boot.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20151008/586b161c/attachment-0001.sig>
next prev parent reply other threads:[~2015-10-08 16:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 6:39 [PATCH v2 0/2] Make Tegra cpuidle driver PSCI compatible Jan Kiszka
2015-09-23 6:39 ` [PATCH v2 1/2] ARM: Availability of psci_smp_available depends on CONFIG_SMP Jan Kiszka
2015-10-06 8:11 ` Thierry Reding
2015-10-06 15:18 ` Will Deacon
2015-10-08 16:04 ` Thierry Reding [this message]
2015-11-12 9:43 ` Sebastian Andrzej Siewior
2015-11-12 9:49 ` Will Deacon
2015-11-12 10:07 ` Sebastian Andrzej Siewior
2015-09-23 6:39 ` [PATCH v2 2/2] ARM: tegra: Disable cpuidle driver if PSCI is present Jan Kiszka
2015-10-06 8:21 ` Thierry Reding
2015-10-06 8:36 ` Jan Kiszka
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=20151008160427.GA29417@ulmo.nvidia.com \
--to=treding@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.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).