From: Quentin Perret <qperret@google.com>
To: Sebastian Ene <sebastianene@google.com>
Cc: catalin.marinas@arm.com, joey.gouly@arm.com, maz@kernel.org,
oliver.upton@linux.dev, snehalreddy@google.com,
sudeep.holla@arm.com, suzuki.poulose@arm.com,
vdonnefort@google.com, will@kernel.org, yuzenghui@huawei.com,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: Re: [PATCH v4 2/3] firmware: arm_ffa: Move the ffa_to_linux definition to the ffa header
Date: Wed, 26 Mar 2025 16:44:58 +0000 [thread overview]
Message-ID: <Z-QvCvGBCtkxNG-e@google.com> (raw)
In-Reply-To: <20250326113901.3308804-3-sebastianene@google.com>
On Wednesday 26 Mar 2025 at 11:39:00 (+0000), Sebastian Ene wrote:
> Keep the ffa_to_linux error map in the header and move it away
> from the arm ffa driver to make it accessible for other components.
>
> Signed-off-by: Sebastian Ene <sebastianene@google.com>
> Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
Reviewed-by: Quentin Perret <qperret@google.com>
> ---
> drivers/firmware/arm_ffa/driver.c | 26 --------------------------
> include/linux/arm_ffa.h | 27 +++++++++++++++++++++++++++
> 2 files changed, 27 insertions(+), 26 deletions(-)
>
> diff --git a/drivers/firmware/arm_ffa/driver.c b/drivers/firmware/arm_ffa/driver.c
> index 2c2ec3c35f15..3f88509a15b7 100644
> --- a/drivers/firmware/arm_ffa/driver.c
> +++ b/drivers/firmware/arm_ffa/driver.c
> @@ -61,30 +61,6 @@
>
> static ffa_fn *invoke_ffa_fn;
>
> -static const int ffa_linux_errmap[] = {
> - /* better than switch case as long as return value is continuous */
> - 0, /* FFA_RET_SUCCESS */
> - -EOPNOTSUPP, /* FFA_RET_NOT_SUPPORTED */
> - -EINVAL, /* FFA_RET_INVALID_PARAMETERS */
> - -ENOMEM, /* FFA_RET_NO_MEMORY */
> - -EBUSY, /* FFA_RET_BUSY */
> - -EINTR, /* FFA_RET_INTERRUPTED */
> - -EACCES, /* FFA_RET_DENIED */
> - -EAGAIN, /* FFA_RET_RETRY */
> - -ECANCELED, /* FFA_RET_ABORTED */
> - -ENODATA, /* FFA_RET_NO_DATA */
> - -EAGAIN, /* FFA_RET_NOT_READY */
> -};
> -
> -static inline int ffa_to_linux_errno(int errno)
> -{
> - int err_idx = -errno;
> -
> - if (err_idx >= 0 && err_idx < ARRAY_SIZE(ffa_linux_errmap))
> - return ffa_linux_errmap[err_idx];
> - return -EINVAL;
> -}
> -
> struct ffa_pcpu_irq {
> struct ffa_drv_info *info;
> };
> @@ -238,8 +214,6 @@ static int ffa_features(u32 func_feat_id, u32 input_props,
> return 0;
> }
>
> -#define PARTITION_INFO_GET_RETURN_COUNT_ONLY BIT(0)
> -
> /* buffer must be sizeof(struct ffa_partition_info) * num_partitions */
> static int
> __ffa_partition_info_get(u32 uuid0, u32 uuid1, u32 uuid2, u32 uuid3,
> diff --git a/include/linux/arm_ffa.h b/include/linux/arm_ffa.h
> index 74169dd0f659..cdaa162060f4 100644
> --- a/include/linux/arm_ffa.h
> +++ b/include/linux/arm_ffa.h
> @@ -223,6 +223,9 @@ extern const struct bus_type ffa_bus_type;
> /* The FF-A 1.0 partition structure lacks the uuid[4] */
> #define FFA_1_0_PARTITON_INFO_SZ (8)
>
> +/* Return the count of partitions deployed in the system */
> +#define PARTITION_INFO_GET_RETURN_COUNT_ONLY BIT(0)
> +
> /* FFA transport related */
> struct ffa_partition_info {
> u16 id;
> @@ -475,4 +478,28 @@ struct ffa_ops {
> const struct ffa_notifier_ops *notifier_ops;
> };
>
> +static const int ffa_linux_errmap[] = {
> + /* better than switch case as long as return value is continuous */
> + 0, /* FFA_RET_SUCCESS */
> + -EOPNOTSUPP, /* FFA_RET_NOT_SUPPORTED */
> + -EINVAL, /* FFA_RET_INVALID_PARAMETERS */
> + -ENOMEM, /* FFA_RET_NO_MEMORY */
> + -EBUSY, /* FFA_RET_BUSY */
> + -EINTR, /* FFA_RET_INTERRUPTED */
> + -EACCES, /* FFA_RET_DENIED */
> + -EAGAIN, /* FFA_RET_RETRY */
> + -ECANCELED, /* FFA_RET_ABORTED */
> + -ENODATA, /* FFA_RET_NO_DATA */
> + -EAGAIN, /* FFA_RET_NOT_READY */
> +};
> +
> +static inline int ffa_to_linux_errno(int errno)
> +{
> + int err_idx = -errno;
> +
> + if (err_idx >= 0 && err_idx < ARRAY_SIZE(ffa_linux_errmap))
> + return ffa_linux_errmap[err_idx];
> + return -EINVAL;
> +}
> +
> #endif /* _LINUX_ARM_FFA_H */
> --
> 2.49.0.395.g12beb8f557-goog
>
next prev parent reply other threads:[~2025-03-26 16:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 11:38 [PATCH v4 0/3] KVM: arm64: Separate the hyp FF-A buffers init from the host Sebastian Ene
2025-03-26 11:38 ` [PATCH v4 1/3] KVM: arm64: Use the static initializer for the version lock Sebastian Ene
2025-03-26 16:44 ` Quentin Perret
2025-03-26 11:39 ` [PATCH v4 2/3] firmware: arm_ffa: Move the ffa_to_linux definition to the ffa header Sebastian Ene
2025-03-26 16:44 ` Quentin Perret [this message]
2025-03-26 11:39 ` [PATCH v4 3/3] KVM: arm64: Release the ownership of the hyp rx buffer to Trustzone Sebastian Ene
2025-03-26 16:48 ` Quentin Perret
2025-03-27 9:37 ` Sebastian Ene
2025-03-27 9:48 ` Sudeep Holla
2025-03-28 11:39 ` Quentin Perret
2025-03-28 14:18 ` Sebastian Ene
2025-04-01 12:00 ` Quentin Perret
2025-04-01 12:55 ` Sudeep Holla
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=Z-QvCvGBCtkxNG-e@google.com \
--to=qperret@google.com \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=kernel-team@android.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=sebastianene@google.com \
--cc=snehalreddy@google.com \
--cc=sudeep.holla@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=vdonnefort@google.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).