devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v6 07/11] firmware: imx: add driver for NXP EdgeLock Enclave
Date: Wed, 4 Oct 2023 08:40:46 +0200	[thread overview]
Message-ID: <f664546b-b287-46bd-9f83-34a571d0f512@linaro.org> (raw)
In-Reply-To: <20230927175401.1962733-8-pankaj.gupta@nxp.com>

On 27/09/2023 19:53, 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.
> 
> Signed-off-by: Pankaj Gupta <pankaj.gupta@nxp.com>

Where is the user-space tool? Please include it in the commit msg. We
talked about this already.

> ---
>  Documentation/ABI/testing/se-cdev         |   41 +
>  drivers/firmware/imx/Kconfig              |   12 +


...

> +
> +	ret = ele_mu_request_channel(dev, &priv->rx_chan,
> +				     &priv->ele_mb_cl, info->mbox_rx_name);
> +	if (ret) {
> +		if (ret != -EPROBE_DEFER)
> +			dev_err(dev, "Failed to request rx channel\n");
> +
> +		goto exit;
> +	}
> +
> +	priv->ctxs = devm_kzalloc(dev, sizeof(dev_ctx) * priv->max_dev_ctx,
> +				  GFP_KERNEL);
> +
> +	if (!priv->ctxs) {
> +		ret = -ENOMEM;
> +		dev_err(dev, "Fail allocate mem for private dev-ctxs.\n");

So you ignored the feedback... I assume you ignored it all, so:

NAK

Please go back and implement the feedback.

Best regards,
Krzysztof


  reply	other threads:[~2023-10-04  6:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 17:53 [PATCH v6 00/11] firmware: imx: NXP Secure-Enclave FW Driver Pankaj Gupta
2023-09-27 17:53 ` [PATCH v6 01/11] Documentation/firmware: added imx/se-fw to other_interfaces Pankaj Gupta
2023-09-27 17:53 ` [PATCH v6 02/11] dt-bindings: arm: fsl: add imx-se-fw binding doc Pankaj Gupta
2023-09-28 18:51   ` Rob Herring
2023-10-04  4:10     ` [EXT] " Pankaj Gupta
2023-10-04  6:36       ` Krzysztof Kozlowski
2023-10-26 11:23         ` Pankaj Gupta
2023-10-26 13:55           ` Conor Dooley
2023-10-27  7:08           ` Krzysztof Kozlowski
2023-09-27 17:53 ` [PATCH v6 03/11] arm64: dts: imx8ulp-evk: added nxp secure enclave firmware Pankaj Gupta
2023-09-27 17:53 ` [PATCH v6 04/11] arm64: dts: imx8ulp-evk: reserved mem-ranges to constrain ele_fw dma-range Pankaj Gupta
2023-09-27 17:53 ` [PATCH v6 05/11] arm64: dts: imx93-11x11-evk: added nxp secure enclave fw Pankaj Gupta
2023-09-27 17:53 ` [PATCH v6 06/11] arm64: dts: imx93-11x11-evk: reserved mem-ranges Pankaj Gupta
2023-09-27 17:53 ` [PATCH v6 07/11] firmware: imx: add driver for NXP EdgeLock Enclave Pankaj Gupta
2023-10-04  6:40   ` Krzysztof Kozlowski [this message]
2023-10-26 11:18     ` [EXT] " Pankaj Gupta
2023-09-27 17:53 ` [PATCH v6 08/11] firmware: imx: init-fw api exchange on imx93 Pankaj Gupta
2023-09-27 17:53 ` [PATCH v6 09/11] firmware: imx: enable trng Pankaj Gupta
2023-10-01  5:25   ` kernel test robot
2023-09-27 17:54 ` [PATCH v6 10/11] firmware: imx: enclave-fw: add handling for save/restore IMEM region Pankaj Gupta
2023-09-27 17:54 ` [PATCH v6 11/11] MAINTAINERS: Added maintainer details 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=f664546b-b287-46bd-9f83-34a571d0f512@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;
as well as URLs for NNTP newsgroup(s).