All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] arm64: SMCCC conduit cleanup
Date: Wed, 23 May 2018 15:51:37 +0100	[thread overview]
Message-ID: <20180523145137.GB2983@arm.com> (raw)
In-Reply-To: <20180503170330.5591-1-mark.rutland@arm.com>

On Thu, May 03, 2018 at 06:03:26PM +0100, Mark Rutland wrote:
> Currently, the cpu errata code goes digging into PSCI internals to
> discover the SMCCC conduit, using the (arguably misnamed) PSCI_CONDUIT_*
> definitions. This lack of abstraction is somewhat unfortunate.
> 
> Further, the SDEI code has an almost identical set of CONDUIT_*
> definitions, and the duplication is rather unfortunate.
> 
> Let's unify things behind a common set of SMCCC_CONDUIT_* definitions,
> and expose the SMCCCv1.1 conduit via a new helper that hides the PSCI
> driver internals.

For the series:

Acked-by: Will Deacon <will.deacon@arm.com>

Will

  parent reply	other threads:[~2018-05-23 14:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03 17:03 [PATCH 0/4] arm64: SMCCC conduit cleanup Mark Rutland
2018-05-03 17:03 ` [PATCH 1/4] arm/arm64: smccc/psci: add arm_smccc_get_conduit() Mark Rutland
2018-05-04 17:54   ` Robin Murphy
2018-05-04 18:02     ` Mark Rutland
2018-05-03 17:03 ` [PATCH 2/4] arm64: errata: use arm_smccc_get_conduit() Mark Rutland
2018-05-03 17:03 ` [PATCH 3/4] firmware/psci: use common SMCCC_CONDUIT_* Mark Rutland
2018-05-03 17:03 ` [PATCH 4/4] firmware: arm_sdei: " Mark Rutland
2018-05-14 15:12   ` James Morse
2018-05-14 11:43 ` [PATCH 0/4] arm64: SMCCC conduit cleanup Lorenzo Pieralisi
2018-05-23 14:51 ` Will Deacon [this message]
2019-02-12 15:24 ` Will Deacon
2019-02-12 17:20   ` Catalin Marinas
2019-02-13 11:42     ` 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=20180523145137.GB2983@arm.com \
    --to=will.deacon@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 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.