From: Sudeep Holla <sudeep.holla@arm.com>
To: peng.fan@nxp.com
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
f.fainelli@gmail.com, festevam@gmail.com,
jassisinghbrar@gmail.com, linux-kernel@vger.kernel.org,
Sudeep Holla <sudeep.holla@arm.com>,
robh+dt@kernel.org, linux-imx@nxp.com, kernel@pengutronix.de,
andre.przywara@arm.com, van.freenix@gmail.com,
shawnguo@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2 2/2] mailbox: introduce ARM SMC based mailbox
Date: Thu, 20 Jun 2019 10:23:01 +0100 [thread overview]
Message-ID: <20190620092301.GD1248@e107155-lin> (raw)
In-Reply-To: <20190603083005.4304-3-peng.fan@nxp.com>
On Mon, Jun 03, 2019 at 04:30:05PM +0800, peng.fan@nxp.com wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> This mailbox driver implements a mailbox which signals transmitted data
> via an ARM smc (secure monitor call) instruction. The mailbox receiver
> is implemented in firmware and can synchronously return data when it
> returns execution to the non-secure world again.
> An asynchronous receive path is not implemented.
> This allows the usage of a mailbox to trigger firmware actions on SoCs
> which either don't have a separate management processor or on which such
> a core is not available. A user of this mailbox could be the SCP
> interface.
>
> Modified from Andre Przywara's v2 patch
> https://lore.kernel.org/patchwork/patch/812999/
>
> Cc: Andre Przywara <andre.przywara@arm.com>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
>
> V2:
> Add interrupts notification support.
>
> drivers/mailbox/Kconfig | 7 ++
> drivers/mailbox/Makefile | 2 +
> drivers/mailbox/arm-smc-mailbox.c | 190 ++++++++++++++++++++++++++++++++
> include/linux/mailbox/arm-smc-mailbox.h | 10 ++
> 4 files changed, 209 insertions(+)
> create mode 100644 drivers/mailbox/arm-smc-mailbox.c
> create mode 100644 include/linux/mailbox/arm-smc-mailbox.h
>
> diff --git a/drivers/mailbox/Kconfig b/drivers/mailbox/Kconfig
> index 595542bfae85..c3bd0f1ddcd8 100644
> --- a/drivers/mailbox/Kconfig
> +++ b/drivers/mailbox/Kconfig
> @@ -15,6 +15,13 @@ config ARM_MHU
> The controller has 3 mailbox channels, the last of which can be
> used in Secure mode only.
>
> +config ARM_SMC_MBOX
> + tristate "Generic ARM smc mailbox"
> + depends on OF && HAVE_ARM_SMCCC
> + help
> + Generic mailbox driver which uses ARM smc calls to call into
> + firmware for triggering mailboxes.
> +
> config IMX_MBOX
> tristate "i.MX Mailbox"
> depends on ARCH_MXC || COMPILE_TEST
> diff --git a/drivers/mailbox/Makefile b/drivers/mailbox/Makefile
> index c22fad6f696b..93918a84c91b 100644
> --- a/drivers/mailbox/Makefile
> +++ b/drivers/mailbox/Makefile
> @@ -7,6 +7,8 @@ obj-$(CONFIG_MAILBOX_TEST) += mailbox-test.o
>
> obj-$(CONFIG_ARM_MHU) += arm_mhu.o
>
> +obj-$(CONFIG_ARM_SMC_MBOX) += arm-smc-mailbox.o
> +
> obj-$(CONFIG_IMX_MBOX) += imx-mailbox.o
>
> obj-$(CONFIG_ARMADA_37XX_RWTM_MBOX) += armada-37xx-rwtm-mailbox.o
> diff --git a/drivers/mailbox/arm-smc-mailbox.c b/drivers/mailbox/arm-smc-mailbox.c
> new file mode 100644
> index 000000000000..fef6e38d8b98
> --- /dev/null
> +++ b/drivers/mailbox/arm-smc-mailbox.c
> @@ -0,0 +1,190 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Copyright (C) 2016,2017 ARM Ltd.
> + * Copyright 2019 NXP
> + */
> +
> +#include <linux/arm-smccc.h>
> +#include <linux/device.h>
> +#include <linux/kernel.h>
> +#include <linux/interrupt.h>
> +#include <linux/mailbox_controller.h>
> +#include <linux/mailbox/arm-smc-mailbox.h>
> +#include <linux/module.h>
> +#include <linux/platform_device.h>
> +
> +#define ARM_SMC_MBOX_USE_HVC BIT(0)
> +#define ARM_SMC_MBOX_USB_IRQ BIT(1)
> +
> +struct arm_smc_chan_data {
> + u32 function_id;
> + u32 flags;
> + int irq;
> +};
> +
> +static int arm_smc_send_data(struct mbox_chan *link, void *data)
> +{
> + struct arm_smc_chan_data *chan_data = link->con_priv;
> + struct arm_smccc_mbox_cmd *cmd = data;
> + struct arm_smccc_res res;
> + u32 function_id;
> +
> + if (chan_data->function_id != UINT_MAX)
> + function_id = chan_data->function_id;
> + else
> + function_id = cmd->a0;
> +
> + if (chan_data->flags & ARM_SMC_MBOX_USE_HVC)
> + arm_smccc_hvc(function_id, cmd->a1, cmd->a2, cmd->a3, cmd->a4,
> + cmd->a5, cmd->a6, cmd->a7, &res);
> + else
> + arm_smccc_smc(function_id, cmd->a1, cmd->a2, cmd->a3, cmd->a4,
> + cmd->a5, cmd->a6, cmd->a7, &res);
> +
So how will the SMC/HVC handler in EL3/2 find which mailbox is being referred
with this command ? I prefer 2nd argument to be the mailbox number.
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Sudeep Holla <sudeep.holla@arm.com>
To: peng.fan@nxp.com
Cc: robh+dt@kernel.org, mark.rutland@arm.com,
jassisinghbrar@gmail.com, f.fainelli@gmail.com,
kernel@pengutronix.de, linux-imx@nxp.com, shawnguo@kernel.org,
festevam@gmail.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, andre.przywara@arm.com,
van.freenix@gmail.com, Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH V2 2/2] mailbox: introduce ARM SMC based mailbox
Date: Thu, 20 Jun 2019 10:23:01 +0100 [thread overview]
Message-ID: <20190620092301.GD1248@e107155-lin> (raw)
In-Reply-To: <20190603083005.4304-3-peng.fan@nxp.com>
On Mon, Jun 03, 2019 at 04:30:05PM +0800, peng.fan@nxp.com wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> This mailbox driver implements a mailbox which signals transmitted data
> via an ARM smc (secure monitor call) instruction. The mailbox receiver
> is implemented in firmware and can synchronously return data when it
> returns execution to the non-secure world again.
> An asynchronous receive path is not implemented.
> This allows the usage of a mailbox to trigger firmware actions on SoCs
> which either don't have a separate management processor or on which such
> a core is not available. A user of this mailbox could be the SCP
> interface.
>
> Modified from Andre Przywara's v2 patch
> https://lore.kernel.org/patchwork/patch/812999/
>
> Cc: Andre Przywara <andre.przywara@arm.com>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
>
> V2:
> Add interrupts notification support.
>
> drivers/mailbox/Kconfig | 7 ++
> drivers/mailbox/Makefile | 2 +
> drivers/mailbox/arm-smc-mailbox.c | 190 ++++++++++++++++++++++++++++++++
> include/linux/mailbox/arm-smc-mailbox.h | 10 ++
> 4 files changed, 209 insertions(+)
> create mode 100644 drivers/mailbox/arm-smc-mailbox.c
> create mode 100644 include/linux/mailbox/arm-smc-mailbox.h
>
> diff --git a/drivers/mailbox/Kconfig b/drivers/mailbox/Kconfig
> index 595542bfae85..c3bd0f1ddcd8 100644
> --- a/drivers/mailbox/Kconfig
> +++ b/drivers/mailbox/Kconfig
> @@ -15,6 +15,13 @@ config ARM_MHU
> The controller has 3 mailbox channels, the last of which can be
> used in Secure mode only.
>
> +config ARM_SMC_MBOX
> + tristate "Generic ARM smc mailbox"
> + depends on OF && HAVE_ARM_SMCCC
> + help
> + Generic mailbox driver which uses ARM smc calls to call into
> + firmware for triggering mailboxes.
> +
> config IMX_MBOX
> tristate "i.MX Mailbox"
> depends on ARCH_MXC || COMPILE_TEST
> diff --git a/drivers/mailbox/Makefile b/drivers/mailbox/Makefile
> index c22fad6f696b..93918a84c91b 100644
> --- a/drivers/mailbox/Makefile
> +++ b/drivers/mailbox/Makefile
> @@ -7,6 +7,8 @@ obj-$(CONFIG_MAILBOX_TEST) += mailbox-test.o
>
> obj-$(CONFIG_ARM_MHU) += arm_mhu.o
>
> +obj-$(CONFIG_ARM_SMC_MBOX) += arm-smc-mailbox.o
> +
> obj-$(CONFIG_IMX_MBOX) += imx-mailbox.o
>
> obj-$(CONFIG_ARMADA_37XX_RWTM_MBOX) += armada-37xx-rwtm-mailbox.o
> diff --git a/drivers/mailbox/arm-smc-mailbox.c b/drivers/mailbox/arm-smc-mailbox.c
> new file mode 100644
> index 000000000000..fef6e38d8b98
> --- /dev/null
> +++ b/drivers/mailbox/arm-smc-mailbox.c
> @@ -0,0 +1,190 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Copyright (C) 2016,2017 ARM Ltd.
> + * Copyright 2019 NXP
> + */
> +
> +#include <linux/arm-smccc.h>
> +#include <linux/device.h>
> +#include <linux/kernel.h>
> +#include <linux/interrupt.h>
> +#include <linux/mailbox_controller.h>
> +#include <linux/mailbox/arm-smc-mailbox.h>
> +#include <linux/module.h>
> +#include <linux/platform_device.h>
> +
> +#define ARM_SMC_MBOX_USE_HVC BIT(0)
> +#define ARM_SMC_MBOX_USB_IRQ BIT(1)
> +
> +struct arm_smc_chan_data {
> + u32 function_id;
> + u32 flags;
> + int irq;
> +};
> +
> +static int arm_smc_send_data(struct mbox_chan *link, void *data)
> +{
> + struct arm_smc_chan_data *chan_data = link->con_priv;
> + struct arm_smccc_mbox_cmd *cmd = data;
> + struct arm_smccc_res res;
> + u32 function_id;
> +
> + if (chan_data->function_id != UINT_MAX)
> + function_id = chan_data->function_id;
> + else
> + function_id = cmd->a0;
> +
> + if (chan_data->flags & ARM_SMC_MBOX_USE_HVC)
> + arm_smccc_hvc(function_id, cmd->a1, cmd->a2, cmd->a3, cmd->a4,
> + cmd->a5, cmd->a6, cmd->a7, &res);
> + else
> + arm_smccc_smc(function_id, cmd->a1, cmd->a2, cmd->a3, cmd->a4,
> + cmd->a5, cmd->a6, cmd->a7, &res);
> +
So how will the SMC/HVC handler in EL3/2 find which mailbox is being referred
with this command ? I prefer 2nd argument to be the mailbox number.
--
Regards,
Sudeep
next prev parent reply other threads:[~2019-06-20 9:23 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 8:30 [PATCH V2 0/2] mailbox: arm: introduce smc triggered mailbox peng.fan
2019-06-03 8:30 ` peng.fan
2019-06-03 8:30 ` [PATCH V2 1/2] DT: mailbox: add binding doc for the ARM SMC mailbox peng.fan
2019-06-03 8:30 ` peng.fan
2019-06-03 16:22 ` Florian Fainelli
2019-06-03 16:22 ` Florian Fainelli
2019-06-03 16:56 ` Sudeep Holla
2019-06-03 16:56 ` Sudeep Holla
2019-06-03 17:18 ` Andre Przywara
2019-06-03 17:18 ` Andre Przywara
2019-06-03 17:18 ` Andre Przywara
2019-06-06 2:51 ` Florian Fainelli
2019-06-06 2:51 ` Florian Fainelli
2019-06-06 3:24 ` Peng Fan
2019-06-06 3:24 ` Peng Fan
2019-06-20 9:22 ` Sudeep Holla
2019-06-20 9:22 ` Sudeep Holla
2019-06-20 16:13 ` Andre Przywara
2019-06-20 16:13 ` Andre Przywara
2019-06-20 16:13 ` Andre Przywara
2019-06-20 16:27 ` Jassi Brar
2019-06-20 16:27 ` Jassi Brar
2019-07-08 22:19 ` Rob Herring
2019-07-08 22:19 ` Rob Herring
2019-07-09 1:40 ` Peng Fan
2019-07-09 1:40 ` Peng Fan
2019-07-09 13:31 ` Rob Herring
2019-07-09 13:31 ` Rob Herring
2019-06-03 8:30 ` [PATCH V2 2/2] mailbox: introduce ARM SMC based mailbox peng.fan
2019-06-03 8:30 ` peng.fan
2019-06-03 16:32 ` Florian Fainelli
2019-06-03 16:32 ` Florian Fainelli
2019-06-06 3:35 ` Peng Fan
2019-06-06 3:35 ` Peng Fan
2019-06-06 13:20 ` Andre Przywara
2019-06-06 13:20 ` Andre Przywara
2019-06-10 1:32 ` Peng Fan
2019-06-10 1:32 ` Peng Fan
2019-06-10 1:32 ` Peng Fan
2019-06-10 10:00 ` Andre Przywara
2019-06-10 10:00 ` Andre Przywara
2019-06-12 12:59 ` Peng Fan
2019-06-12 12:59 ` Peng Fan
2019-06-12 17:18 ` Andre Przywara
2019-06-12 17:18 ` Andre Przywara
2019-06-20 9:23 ` Sudeep Holla [this message]
2019-06-20 9:23 ` Sudeep Holla
2019-06-20 10:21 ` Peng Fan
2019-06-20 10:21 ` Peng Fan
2019-06-20 11:15 ` Sudeep Holla
2019-06-20 11:15 ` Sudeep Holla
2019-06-25 7:28 ` Peng Fan
2019-06-25 7:28 ` Peng Fan
2019-06-20 16:50 ` Jassi Brar
2019-06-20 16:50 ` Jassi Brar
2019-06-25 7:20 ` Peng Fan
2019-06-25 7:20 ` Peng Fan
2019-06-26 17:05 ` André Przywara
2019-06-26 17:05 ` André Przywara
2019-06-26 17:07 ` Florian Fainelli
2019-06-26 17:07 ` Florian Fainelli
2019-06-25 7:30 ` Peng Fan
2019-06-25 7:30 ` Peng Fan
2019-06-25 14:36 ` Jassi Brar
2019-06-25 14:36 ` Jassi Brar
2019-06-26 13:31 ` Peng Fan
2019-06-26 13:31 ` Peng Fan
2019-06-26 16:31 ` Jassi Brar
2019-06-26 16:31 ` Jassi Brar
2019-06-26 16:44 ` Florian Fainelli
2019-06-26 16:44 ` Florian Fainelli
2019-06-26 16:44 ` Florian Fainelli
2019-06-26 17:09 ` Sudeep Holla
2019-06-26 17:09 ` Sudeep Holla
2019-06-27 18:10 ` Florian Fainelli
2019-06-27 18:10 ` Florian Fainelli
2019-06-26 18:27 ` Jassi Brar
2019-06-26 18:27 ` Jassi Brar
2019-06-26 18:27 ` Jassi Brar
2019-06-27 9:09 ` Sudeep Holla
2019-06-27 9:09 ` Sudeep Holla
2019-06-27 15:32 ` Jassi Brar
2019-06-27 15:32 ` Jassi Brar
2019-06-27 17:07 ` Sudeep Holla
2019-06-27 17:07 ` Sudeep Holla
2019-06-26 17:02 ` Sudeep Holla
2019-06-26 17:02 ` 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=20190620092301.GD1248@e107155-lin \
--to=sudeep.holla@arm.com \
--cc=andre.przywara@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=festevam@gmail.com \
--cc=jassisinghbrar@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=van.freenix@gmail.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 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.