All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	Will Deacon <will@kernel.org>
Subject: Re: [PATCH 3/3] arm64: Add architecture specific ACPI FFH Opregion callbacks
Date: Thu, 30 Jun 2022 14:35:19 +0100	[thread overview]
Message-ID: <Yr2ml0vMTgLi+EPZ@arm.com> (raw)
In-Reply-To: <20220616090106.2154906-4-sudeep.holla@arm.com>

On Thu, Jun 16, 2022 at 10:01:06AM +0100, Sudeep Holla wrote:
> FFH Operation Region space can be used to trigger SMC or HVC calls,
> using the Arm SMC Calling Convention (SMCCC). The choice of conduit
> (SMC or HVC) is based on what the kernel choose based on PSCI as with
> any other users of SMCCC within the kernel.
> 
> Function identifiers only the SMCCC SiP Service, OEM Service and FF-A
> specific call range.
> 
> Offset can be either 0(32 bit calling convention) or 1(64 bit calling
> convention). The length must be set with the range applicable based
> on the value of the offset.
> 
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>

Acked-by: Catalin Marinas <catalin.marinas@arm.com>

WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	Will Deacon <will@kernel.org>
Subject: Re: [PATCH 3/3] arm64: Add architecture specific ACPI FFH Opregion callbacks
Date: Thu, 30 Jun 2022 14:35:19 +0100	[thread overview]
Message-ID: <Yr2ml0vMTgLi+EPZ@arm.com> (raw)
In-Reply-To: <20220616090106.2154906-4-sudeep.holla@arm.com>

On Thu, Jun 16, 2022 at 10:01:06AM +0100, Sudeep Holla wrote:
> FFH Operation Region space can be used to trigger SMC or HVC calls,
> using the Arm SMC Calling Convention (SMCCC). The choice of conduit
> (SMC or HVC) is based on what the kernel choose based on PSCI as with
> any other users of SMCCC within the kernel.
> 
> Function identifiers only the SMCCC SiP Service, OEM Service and FF-A
> specific call range.
> 
> Offset can be either 0(32 bit calling convention) or 1(64 bit calling
> convention). The length must be set with the range applicable based
> on the value of the offset.
> 
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>

Acked-by: Catalin Marinas <catalin.marinas@arm.com>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-06-30 13:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16  9:01 [PATCH 0/3] ACPI: Implement FFH OpRegion support Sudeep Holla
2022-06-16  9:01 ` Sudeep Holla
2022-06-16  9:01 ` [PATCH 1/3] ACPICA: Add support for FFH Opregion special context data Sudeep Holla
2022-06-16  9:01   ` Sudeep Holla
2022-06-22 12:50   ` Rafael J. Wysocki
2022-06-22 12:50     ` Rafael J. Wysocki
2022-06-22 14:00     ` Sudeep Holla
2022-06-22 14:00       ` Sudeep Holla
2022-06-22 14:10       ` Rafael J. Wysocki
2022-06-22 14:10         ` Rafael J. Wysocki
2022-06-16  9:01 ` [PATCH 2/3] ACPI: Implement a generic FFH Opregion handler Sudeep Holla
2022-06-16  9:01   ` Sudeep Holla
2022-06-16  9:01 ` [PATCH 3/3] arm64: Add architecture specific ACPI FFH Opregion callbacks Sudeep Holla
2022-06-16  9:01   ` Sudeep Holla
2022-06-30 13:35   ` Catalin Marinas [this message]
2022-06-30 13:35     ` Catalin Marinas

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=Yr2ml0vMTgLi+EPZ@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lpieralisi@kernel.org \
    --cc=rafael@kernel.org \
    --cc=sudeep.holla@arm.com \
    --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 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.