firmware/psci: Fix MEM_PROTECT_RANGE function numbers
authorWill Deacon <will@kernel.org>
Fri, 25 Nov 2022 10:18:26 +0000 (10:18 +0000)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 18 Jan 2023 10:58:16 +0000 (11:58 +0100)
commita30aafcfba8f9ec2a9f58769c5cdc9a2f3816008
tree4ab82f3a3017148ce8aeedb8e5fa531088bb0787
parentb107b08c41b3076a508113fbaaffe15ce1fe7f65
firmware/psci: Fix MEM_PROTECT_RANGE function numbers

commit f3dc61cde80d48751999c4cb46daf3b2185e6895 upstream.

PSCI v1.1 offers 32-bit and 64-bit variants of the MEM_PROTECT_RANGE
call using function identifier 20.

Fix the incorrect definitions of the MEM_PROTECT_CHECK_RANGE calls in
the PSCI UAPI header.

Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Lorenzo Pieralisi <lpieralisi@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Fixes: 3137f2e60098 ("firmware/psci: Add debugfs support to ease debugging")
Acked-by: Marc Zyngier <maz@kernel.org>
Acked-by: Mark Rutland <mark.rutland@arm.com>
Link: https://lore.kernel.org/r/20221125101826.22404-1-will@kernel.org
Signed-off-by: Will Deacon <will@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
include/uapi/linux/psci.h