linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 11/12] ARM: migrate to common PSCI client code
Date: Fri, 5 Jun 2015 11:04:58 +0100	[thread overview]
Message-ID: <20150605100458.GD599@leverpostej> (raw)
In-Reply-To: <20150604094529.GB8346@e104818-lin.cambridge.arm.com>

On Thu, Jun 04, 2015 at 10:45:30AM +0100, Catalin Marinas wrote:
> Hi Mark,
> 
> On Wed, Jun 03, 2015 at 04:16:39PM +0100, Mark Rutland wrote:
> > On Tue, May 26, 2015 at 02:52:29PM +0100, Mark Rutland wrote:
> > > Now that the common PSCI client code has been factored out to
> > > drivers/firmware, and made safe for 32-bit use, move the 32-bit ARM code
> > > over to it. This results in a moderate reduction of duplicated lines,
> > > and will prevent further duplication as the PSCI client code is updated
> > > for PSCI 1.0 and beyond.
> > > 
> > > The two legacy platform users of the PSCI invocation code are updated to
> > > account for interface changes. In both cases the power state parameter
> > > is changed to an opaque u32 token in preparation for PSCI 1.0 power
> > > state changes.
> > > 
> > > Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> > > Acked-by: Catalin Marinas <catalin.marinas@arm.com>
> > > Cc: Ashwin Chaugule <ashwin.chaugule@linaro.org>
> > > Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> > > Cc: Rob Herring <robh@kernel.org>
> > > Cc: Russell King <rmk+kernel@arm.linux.org.uk>
> > > Cc: Will Deacon <will.deacon@arm.com>
> > > ---
> > >  arch/arm/Kconfig                  |   1 +
> > >  arch/arm/include/asm/psci.h       |  23 ---
> > >  arch/arm/kernel/Makefile          |   2 +-
> > >  arch/arm/kernel/psci.c            | 299 --------------------------------------
> > >  arch/arm/kernel/psci_smp.c        |  29 +++-
> > >  arch/arm/kernel/setup.c           |   3 +-
> > >  arch/arm/mach-highbank/highbank.c |   2 +-
> > >  arch/arm/mach-highbank/pm.c       |   8 +-
> > >  drivers/cpuidle/cpuidle-calxeda.c |   7 +-
> > >  9 files changed, 32 insertions(+), 342 deletions(-)
> > >  delete mode 100644 arch/arm/kernel/psci.c
> > 
> > Do you have any objections to the arch/arm changes in this patch?
> > 
> > If not, could I please have your ack?
> > 
> > As there are arm, arm64, and drivers changes in the series I was hoping
> > this could all go via arm-soc.
> 
> If we don't hear from Russell by the end of today, I propose that we
> merge patches 1-8 in the arm64 tree (mostly fixes for PSCI). This series
> is blocking other developments like PSCI 1.0, so I really want to get
> parts of it merged in 4.2.

I've pushed the first 8 patches to my arm64/psci-rework branch [1]. I've
pushed the whole series with the tags provided today to psci/rework [2].

I tried a merge with the arm64 for-next/core branch locally, and got a
trivial conflict in smp.c against the changes in "arm64: Use common
outgoing-CPU-notification code". Hopefully that's easy to fix up
locally.

> BTW, can we skip patch 11 in this series and still allow
> drivers/firmware/psci.c only for arm64, with the aim of moving the arm32
> code later?

We could, though I would prefer to have the two unified from the
beginning.

Thanks,
Mark.

[1] git://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git arm64/psci-rework
[2] git://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git psci/rework

  reply	other threads:[~2015-06-05 10:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26 13:52 [PATCHv3 00/12] arm/arm64: Unify PSCI client support Mark Rutland
2015-05-26 13:52 ` [PATCHv3 01/12] arm/arm64: kvm: add missing PSCI include Mark Rutland
2015-05-26 13:52 ` [PATCHv3 02/12] arm64: smp_plat: add get_logical_index Mark Rutland
2015-05-26 13:52 ` [PATCHv3 03/12] arm64: smp: consistently use error codes Mark Rutland
2015-05-26 13:52 ` [PATCHv3 04/12] arm64: psci: remove unnecessary id indirection Mark Rutland
2015-05-26 13:52 ` [PATCHv3 05/12] arm64: psci: support unsigned return values Mark Rutland
2015-05-26 13:52 ` [PATCHv3 06/12] arm64: psci: account for Trusted OS instances Mark Rutland
2015-05-26 13:52 ` [PATCHv3 07/12] arm64: psci: kill psci_power_state Mark Rutland
2015-05-26 13:52 ` [PATCHv3 08/12] arm64: psci: remove ACPI coupling Mark Rutland
2015-05-26 20:18   ` Al Stone
2015-05-26 13:52 ` [PATCHv3 09/12] arm64: psci: factor invocation code to drivers Mark Rutland
2015-05-26 13:52 ` [PATCHv3 10/12] drivers: psci: support native SMC{32,64} calls Mark Rutland
2015-05-26 13:52 ` [PATCHv3 11/12] ARM: migrate to common PSCI client code Mark Rutland
2015-05-27 12:01   ` Ashwin Chaugule
2015-05-27 12:41     ` Mark Rutland
2015-05-27 16:46   ` Rob Herring
2015-05-27 17:17     ` Mark Rutland
2015-06-03 15:19       ` Mark Rutland
2015-06-03 15:16   ` Mark Rutland
2015-06-04  9:45     ` Catalin Marinas
2015-06-05 10:04       ` Mark Rutland [this message]
2015-06-05 10:35         ` Catalin Marinas
2015-06-04  9:49     ` Russell King - ARM Linux
2015-05-26 13:52 ` [PATCHv3 12/12] MAINTAINERS: add PSCI entry Mark Rutland
2015-05-27  8:08 ` [PATCHv3 00/12] arm/arm64: Unify PSCI client support Hanjun Guo
2015-05-27 12:23   ` Mark Rutland

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=20150605100458.GD599@leverpostej \
    --to=mark.rutland@arm.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).