Linux EFI development
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-efi@vger.kernel.org
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	Jose Marinho <jose.marinho@arm.com>
Subject: [PATCH 0/3] ACPI: Enable Platform Runtime Mechanism(PRM) support on ARM64
Date: Fri, 24 Jun 2022 16:23:28 +0100	[thread overview]
Message-ID: <20220624152331.4009502-1-sudeep.holla@arm.com> (raw)

Hi,

This tiny series is to enable Platform Runtime Mechanism(PRM) support on
ARM64. Not much changes. Just enabling the build and moving the config
option so that it is not listed under the topmost menu for ARM64.

Regards,
Sudeep

Sudeep Holla (3):
  arm64: efi: Simplify arch_efi_call_virt macro by not using efi_##f##_t type
  ACPI: Enable Platform Runtime Mechanism(PRM) support on ARM64
  ACPI: Move PRM config option under the main ACPI config

 arch/arm64/include/asm/efi.h |  4 +---
 drivers/acpi/Kconfig         | 30 +++++++++++++++---------------
 2 files changed, 16 insertions(+), 18 deletions(-)

--
2.36.1


             reply	other threads:[~2022-06-24 15:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 15:23 Sudeep Holla [this message]
2022-06-24 15:23 ` [PATCH 1/3] arm64: efi: Simplify arch_efi_call_virt macro by not using efi_##f##_t type Sudeep Holla
2022-06-24 17:45   ` Ard Biesheuvel
2022-06-25 10:10     ` Sudeep Holla
2022-06-25 16:01       ` Ard Biesheuvel
2022-06-24 15:23 ` [PATCH 2/3] ACPI: Enable Platform Runtime Mechanism(PRM) support on ARM64 Sudeep Holla
2022-06-24 17:41   ` Ard Biesheuvel
2022-06-24 15:23 ` [PATCH 3/3] ACPI: Move PRM config option under the main ACPI config Sudeep Holla
2022-06-24 17:42   ` Ard Biesheuvel

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=20220624152331.4009502-1-sudeep.holla@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=ardb@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=jose.marinho@arm.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox