summaryrefslogtreecommitdiffstats
path: root/drivers/watchdog
diff options
context:
space:
mode:
authorSudeep Holla <sudeep.holla@arm.com>2022-11-10 13:45:05 +0000
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2022-11-14 19:09:07 +0100
commit1d280ce099db396e092cac1aa9bf2ea8beee6d76 (patch)
tree3ee185f93f7c73c7f8b9ee1ee3166652d9340574 /drivers/watchdog
parente81c782c16844dc758a784899c2fe5260386211b (diff)
downloadlinux-stable-1d280ce099db396e092cac1aa9bf2ea8beee6d76.tar.gz
linux-stable-1d280ce099db396e092cac1aa9bf2ea8beee6d76.tar.bz2
linux-stable-1d280ce099db396e092cac1aa9bf2ea8beee6d76.zip
arm64: Add architecture specific ACPI FFH Opregion callbacks
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 in the SMCCC SiP Service, OEM Service and FF-A specific call range are allowed in FFH Opregions. 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. Acked-by: Catalin Marinas <catalin.marinas@arm.com> Cc: Will Deacon <will@kernel.org> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/watchdog')
0 files changed, 0 insertions, 0 deletions