From: kernel test robot <lkp@intel.com>
To: Pankaj Gupta <pankaj.gupta@nxp.com>,
Jonathan Corbet <corbet@lwn.net>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Frank Li <Frank.Li@nxp.com>
Subject: Re: [PATCH v21 3/7] firmware: imx: add driver for NXP EdgeLock Enclave
Date: Sun, 14 Dec 2025 10:44:22 +0800 [thread overview]
Message-ID: <202512141039.nVscnjzl-lkp@intel.com> (raw)
In-Reply-To: <20251212-imx-se-if-v21-3-ee7d6052d848@nxp.com>
Hi Pankaj,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 4a26e7032d7d57c998598c08a034872d6f0d3945]
url: https://github.com/intel-lab-lkp/linux/commits/Pankaj-Gupta/Documentation-firmware-add-imx-se-to-other_interfaces/20251212-172535
base: 4a26e7032d7d57c998598c08a034872d6f0d3945
patch link: https://lore.kernel.org/r/20251212-imx-se-if-v21-3-ee7d6052d848%40nxp.com
patch subject: [PATCH v21 3/7] firmware: imx: add driver for NXP EdgeLock Enclave
config: powerpc-randconfig-r131-20251213 (https://download.01.org/0day-ci/archive/20251214/202512141039.nVscnjzl-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 13.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251214/202512141039.nVscnjzl-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202512141039.nVscnjzl-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/firmware/imx/ele_base_msg.c:77:52: sparse: sparse: non size-preserving pointer to integer cast
vim +77 drivers/firmware/imx/ele_base_msg.c
16
17 int ele_get_info(struct se_if_priv *priv, struct ele_dev_info *s_info)
18 {
19 struct se_api_msg *tx_msg = NULL;
20 struct se_api_msg *rx_msg = NULL;
21 dma_addr_t get_info_addr = 0;
22 u32 *get_info_data = NULL;
23 int ret = 0;
24
25 if (!priv)
26 return -EINVAL;
27
28 memset(s_info, 0x0, sizeof(*s_info));
29
30 tx_msg = kzalloc(ELE_GET_INFO_REQ_MSG_SZ, GFP_KERNEL);
31 if (!tx_msg)
32 return -ENOMEM;
33
34 rx_msg = kzalloc(ELE_GET_INFO_RSP_MSG_SZ, GFP_KERNEL);
35 if (!rx_msg) {
36 ret = -ENOMEM;
37 goto exit;
38 }
39
40 if (priv->mem_pool)
41 get_info_data = gen_pool_dma_alloc(priv->mem_pool,
42 ELE_GET_INFO_BUFF_SZ,
43 &get_info_addr);
44 else
45 get_info_data = dma_alloc_coherent(priv->dev,
46 ELE_GET_INFO_BUFF_SZ,
47 &get_info_addr,
48 GFP_KERNEL);
49 if (!get_info_data) {
50 dev_dbg(priv->dev,
51 "%s: Failed to allocate get_info_addr.", __func__);
52 ret = -ENOMEM;
53 goto exit;
54 }
55
56 ret = se_fill_cmd_msg_hdr(priv, (struct se_msg_hdr *)&tx_msg->header,
57 ELE_GET_INFO_REQ, ELE_GET_INFO_REQ_MSG_SZ,
58 true);
59 if (ret)
60 goto exit;
61
62 tx_msg->data[0] = upper_32_bits(get_info_addr);
63 tx_msg->data[1] = lower_32_bits(get_info_addr);
64 tx_msg->data[2] = sizeof(*s_info);
65 ret = ele_msg_send_rcv(priv, tx_msg, ELE_GET_INFO_REQ_MSG_SZ, rx_msg,
66 ELE_GET_INFO_RSP_MSG_SZ);
67 if (ret < 0)
68 goto exit;
69
70 ret = se_val_rsp_hdr_n_status(priv, rx_msg, ELE_GET_INFO_REQ,
71 ELE_GET_INFO_RSP_MSG_SZ, true);
72
73 memcpy(s_info, get_info_data, sizeof(*s_info));
74
75 exit:
76 if (priv->mem_pool)
> 77 gen_pool_free(priv->mem_pool, (u64)get_info_data,
78 ELE_GET_INFO_BUFF_SZ);
79 else
80 dma_free_coherent(priv->dev, ELE_GET_INFO_BUFF_SZ,
81 get_info_data, get_info_addr);
82
83 kfree(tx_msg);
84 kfree(rx_msg);
85 return ret;
86 }
87
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-12-14 2:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 9:14 [PATCH v21 0/7] firmware: imx: driver for NXP secure-enclave Pankaj Gupta
2025-12-12 9:14 ` [PATCH v21 1/7] Documentation/firmware: add imx/se to other_interfaces Pankaj Gupta
2025-12-15 3:51 ` kernel test robot
2025-12-12 9:14 ` [PATCH v21 2/7] dt-bindings: arm: fsl: add imx-se-fw binding doc Pankaj Gupta
2025-12-12 9:14 ` [PATCH v21 3/7] firmware: imx: add driver for NXP EdgeLock Enclave Pankaj Gupta
2025-12-13 0:45 ` kernel test robot
2025-12-13 0:45 ` kernel test robot
2025-12-14 2:44 ` kernel test robot [this message]
2025-12-12 9:14 ` [PATCH v21 4/7] firmware: imx: device context dedicated to priv Pankaj Gupta
2025-12-12 9:14 ` [PATCH v21 5/7] firmware: drivers: imx: adds miscdev Pankaj Gupta
2025-12-12 16:54 ` Frank Li
2025-12-17 8:40 ` Pankaj Gupta
2025-12-12 9:14 ` [PATCH v21 6/7] arm64: dts: imx8ulp: add secure enclave node Pankaj Gupta
2025-12-12 9:14 ` [PATCH v21 7/7] arm64: dts: imx8ulp-evk: add reserved memory property 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=202512141039.nVscnjzl-lkp@intel.com \
--to=lkp@intel.com \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pankaj.gupta@nxp.com \
--cc=robh@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