From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Pankaj Gupta <pankaj.gupta@nxp.com>,
shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, clin@suse.com, conor+dt@kernel.org,
pierre.gondois@arm.com, festevam@gmail.com, linux-imx@nxp.com,
davem@davemloft.net, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, gaurav.jain@nxp.com,
alexander.stein@ew.tq-group.com, V.Sethi@nxp.com
Subject: Re: [PATCH v7 07/11] firmware: imx: add driver for NXP EdgeLock Enclave
Date: Mon, 30 Oct 2023 19:02:48 +0100 [thread overview]
Message-ID: <0148c072-feaa-4553-8a25-a0fced1bfad0@linaro.org> (raw)
In-Reply-To: <20231030095849.3456820-8-pankaj.gupta@nxp.com>
On 30/10/2023 10:58, Pankaj Gupta wrote:
> The Edgelock Enclave , is the secure enclave embedded in the SoC
> to support the features like HSM, SHE & V2X, using message based
> communication channel.
>
> ELE FW communicates on a dedicated MU with application core where
> kernel is running. It exists on specific i.MX processors. e.g.
> i.MX8ULP, i.MX93.
>
> User-space library using this driver:
> - i.MX Secure Enclave library:
> -- URL: https://github.com/nxp-imx/imx-secure-enclave.git,
> - i.MX Secure Middle-Ware:
> -- URL: https://github.com/nxp-imx/imx-smw.git
OK, I got your patch #7. Thanks for documenting the user-space.
>
> Signed-off-by: Pankaj Gupta <pankaj.gupta@nxp.com>
...
> diff --git a/drivers/firmware/imx/ele_common.c b/drivers/firmware/imx/ele_common.c
> new file mode 100644
> index 000000000000..4410245a19ec
> --- /dev/null
> +++ b/drivers/firmware/imx/ele_common.c
> @@ -0,0 +1,139 @@
> +// SPDX-License-Identifier: GPL-2.0+
> +/*
> + * Copyright 2023 NXP
> + */
> +
> +#include "ele_common.h"
> +#include "se_fw.h"
> +
> +int imx_se_alloc_tx_rx_buf(struct ele_mu_priv *priv)
> +{
> + int ret = 0;
> +
> + priv->tx_msg = devm_kzalloc(priv->dev,
> + sizeof(*priv->tx_msg),
> + GFP_KERNEL);
> + if (!priv->tx_msg) {
> + ret = -ENOMEM;
> + dev_err(priv->dev, "Fail allocate mem for tx_msg.\n");
No improvements. I assume rest of feedback could still be ignored. I am
not going to check. It's your duty to implement the comments, not mine
to check every line whether you did it or not. Trust does not work like
that.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-10-30 18:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 9:58 [PATCH v7 00/11] firmware: imx: NXP Secure-Enclave FW Driver Pankaj Gupta
2023-10-30 9:58 ` [PATCH v7 01/11] Documentation/firmware: added imx/se-fw to other_interfaces Pankaj Gupta
2023-10-30 17:57 ` Krzysztof Kozlowski
2023-10-30 17:59 ` Krzysztof Kozlowski
2023-10-30 9:58 ` [PATCH v7 02/11] dt-bindings: arm: fsl: add imx-se-fw binding doc Pankaj Gupta
2023-10-30 16:30 ` Rob Herring
2023-10-30 17:51 ` Krzysztof Kozlowski
2023-10-30 9:58 ` [PATCH v7 03/11] arm64: dts: imx8ulp-evk: added nxp secure enclave firmware Pankaj Gupta
2023-10-30 17:52 ` Krzysztof Kozlowski
2023-10-30 9:58 ` [PATCH v7 04/11] arm64: dts: imx8ulp-evk: reserved mem-ranges to constrain ele_fw dma-range Pankaj Gupta
2023-10-30 9:58 ` [PATCH v7 05/11] arm64: dts: imx93-11x11-evk: added nxp secure enclave fw Pankaj Gupta
2023-10-30 17:52 ` Krzysztof Kozlowski
2023-10-30 9:58 ` [PATCH v7 06/11] arm64: dts: imx93-11x11-evk: reserved mem-ranges Pankaj Gupta
2023-10-30 17:55 ` Krzysztof Kozlowski
2023-10-30 9:58 ` [PATCH v7 07/11] firmware: imx: add driver for NXP EdgeLock Enclave Pankaj Gupta
2023-10-30 18:02 ` Krzysztof Kozlowski [this message]
2023-10-30 9:58 ` [PATCH v7 08/11] firmware: imx: init-fw api exchange on imx93 Pankaj Gupta
2023-10-30 9:58 ` [PATCH v7 09/11] firmware: imx: enable trng Pankaj Gupta
2023-10-30 9:58 ` [PATCH v7 10/11] firmware: imx: enclave-fw: add handling for save/restore IMEM region Pankaj Gupta
2023-10-30 9:58 ` [PATCH v7 11/11] MAINTAINERS: Added maintainer details Pankaj Gupta
2024-03-15 12:23 ` [PATCH v7 00/11] firmware: imx: NXP Secure-Enclave FW Driver Pankaj Gupta
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=0148c072-feaa-4553-8a25-a0fced1bfad0@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=V.Sethi@nxp.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=clin@suse.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gaurav.jain@nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.gupta@nxp.com \
--cc=pierre.gondois@arm.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®