From: kernel test robot <lkp@intel.com>
To: Andre Przywara <andre.przywara@arm.com>,
Corentin Labbe <clabbe.montjoie@gmail.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-crypto@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/4] crypto: sun8i-ce - wrap accesses to descriptor address fields
Date: Tue, 18 Jun 2024 21:38:35 +0800 [thread overview]
Message-ID: <202406182149.eAIruF9N-lkp@intel.com> (raw)
In-Reply-To: <20240616220719.26641-3-andre.przywara@arm.com>
Hi Andre,
kernel test robot noticed the following build warnings:
[auto build test WARNING on sunxi/sunxi/for-next]
[also build test WARNING on herbert-cryptodev-2.6/master herbert-crypto-2.6/master linus/master v6.10-rc4 next-20240617]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Andre-Przywara/dt-bindings-crypto-sun8i-ce-Add-compatible-for-H616/20240617-061144
base: https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git sunxi/for-next
patch link: https://lore.kernel.org/r/20240616220719.26641-3-andre.przywara%40arm.com
patch subject: [PATCH 2/4] crypto: sun8i-ce - wrap accesses to descriptor address fields
config: mips-randconfig-r121-20240618 (https://download.01.org/0day-ci/archive/20240618/202406182149.eAIruF9N-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 78ee473784e5ef6f0b19ce4cb111fb6e4d23c6b2)
reproduce: (https://download.01.org/0day-ci/archive/20240618/202406182149.eAIruF9N-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/202406182149.eAIruF9N-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/crypto/allwinner/sun8i-ce/sun8i-ce-core.c:175:34: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected unsigned int [usertype] val @@ got restricted __le32 @@
drivers/crypto/allwinner/sun8i-ce/sun8i-ce-core.c:175:34: sparse: expected unsigned int [usertype] val
drivers/crypto/allwinner/sun8i-ce/sun8i-ce-core.c:175:34: sparse: got restricted __le32
vim +175 drivers/crypto/allwinner/sun8i-ce/sun8i-ce-core.c
167
168 mutex_lock(&ce->mlock);
169
170 v = readl(ce->base + CE_ICR);
171 v |= 1 << flow;
172 writel(v, ce->base + CE_ICR);
173
174 reinit_completion(&ce->chanlist[flow].complete);
> 175 writel(sun8i_ce_desc_addr(ce, ce->chanlist[flow].t_phy),
176 ce->base + CE_TDQ);
177
178 ce->chanlist[flow].status = 0;
179 /* Be sure all data is written before enabling the task */
180 wmb();
181
182 /* Only H6 needs to write a part of t_common_ctl along with "1", but since it is ignored
183 * on older SoCs, we have no reason to complicate things.
184 */
185 v = 1 | ((le32_to_cpu(ce->chanlist[flow].tl->t_common_ctl) & 0x7F) << 8);
186 writel(v, ce->base + CE_TLR);
187 mutex_unlock(&ce->mlock);
188
189 wait_for_completion_interruptible_timeout(&ce->chanlist[flow].complete,
190 msecs_to_jiffies(ce->chanlist[flow].timeout));
191
192 if (ce->chanlist[flow].status == 0) {
193 dev_err(ce->dev, "DMA timeout for %s (tm=%d) on flow %d\n", name,
194 ce->chanlist[flow].timeout, flow);
195 err = -EFAULT;
196 }
197 /* No need to lock for this read, the channel is locked so
198 * nothing could modify the error value for this channel
199 */
200 v = readl(ce->base + CE_ESR);
201 switch (ce->variant->esr) {
202 case ESR_H3:
203 /* Sadly, the error bit is not per flow */
204 if (v) {
205 dev_err(ce->dev, "CE ERROR: %x for flow %x\n", v, flow);
206 err = -EFAULT;
207 print_hex_dump(KERN_INFO, "TASK: ", DUMP_PREFIX_NONE, 16, 4,
208 cet, sizeof(struct ce_task), false);
209 }
210 if (v & CE_ERR_ALGO_NOTSUP)
211 dev_err(ce->dev, "CE ERROR: algorithm not supported\n");
212 if (v & CE_ERR_DATALEN)
213 dev_err(ce->dev, "CE ERROR: data length error\n");
214 if (v & CE_ERR_KEYSRAM)
215 dev_err(ce->dev, "CE ERROR: keysram access error for AES\n");
216 break;
217 case ESR_A64:
218 case ESR_D1:
219 case ESR_H5:
220 case ESR_R40:
221 v >>= (flow * 4);
222 v &= 0xF;
223 if (v) {
224 dev_err(ce->dev, "CE ERROR: %x for flow %x\n", v, flow);
225 err = -EFAULT;
226 print_hex_dump(KERN_INFO, "TASK: ", DUMP_PREFIX_NONE, 16, 4,
227 cet, sizeof(struct ce_task), false);
228 }
229 if (v & CE_ERR_ALGO_NOTSUP)
230 dev_err(ce->dev, "CE ERROR: algorithm not supported\n");
231 if (v & CE_ERR_DATALEN)
232 dev_err(ce->dev, "CE ERROR: data length error\n");
233 if (v & CE_ERR_KEYSRAM)
234 dev_err(ce->dev, "CE ERROR: keysram access error for AES\n");
235 break;
236 case ESR_H6:
237 v >>= (flow * 8);
238 v &= 0xFF;
239 if (v) {
240 dev_err(ce->dev, "CE ERROR: %x for flow %x\n", v, flow);
241 err = -EFAULT;
242 print_hex_dump(KERN_INFO, "TASK: ", DUMP_PREFIX_NONE, 16, 4,
243 cet, sizeof(struct ce_task), false);
244 }
245 if (v & CE_ERR_ALGO_NOTSUP)
246 dev_err(ce->dev, "CE ERROR: algorithm not supported\n");
247 if (v & CE_ERR_DATALEN)
248 dev_err(ce->dev, "CE ERROR: data length error\n");
249 if (v & CE_ERR_KEYSRAM)
250 dev_err(ce->dev, "CE ERROR: keysram access error for AES\n");
251 if (v & CE_ERR_ADDR_INVALID)
252 dev_err(ce->dev, "CE ERROR: address invalid\n");
253 if (v & CE_ERR_KEYLADDER)
254 dev_err(ce->dev, "CE ERROR: key ladder configuration error\n");
255 break;
256 }
257
258 return err;
259 }
260
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-06-18 13:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-16 22:07 [PATCH 0/4] crypto: sun8i-ce: add Allwinner H616 support Andre Przywara
2024-06-16 22:07 ` [PATCH 1/4] dt-bindings: crypto: sun8i-ce: Add compatible for H616 Andre Przywara
2024-06-17 6:51 ` Krzysztof Kozlowski
2024-06-21 14:37 ` Chen-Yu Tsai
2024-06-16 22:07 ` [PATCH 2/4] crypto: sun8i-ce - wrap accesses to descriptor address fields Andre Przywara
2024-06-18 7:39 ` kernel test robot
2024-06-24 16:34 ` Andre Przywara
2024-06-18 13:38 ` kernel test robot [this message]
2024-06-21 14:53 ` Chen-Yu Tsai
2024-06-24 16:32 ` Andre Przywara
2024-06-16 22:07 ` [PATCH 3/4] crypto: sun8i-ce - add Allwinner H616 support Andre Przywara
2024-06-21 14:45 ` Chen-Yu Tsai
2024-06-16 22:07 ` [PATCH 4/4] arm64: dts: allwinner: h616: add crypto engine node Andre Przywara
2024-06-22 23:37 ` [PATCH 0/4] crypto: sun8i-ce: add Allwinner H616 support Ryan Walklin
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=202406182149.eAIruF9N-lkp@intel.com \
--to=lkp@intel.com \
--cc=andre.przywara@arm.com \
--cc=clabbe.montjoie@gmail.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=jernej.skrabec@gmail.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@csie.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).