From: kernel test robot <lkp@intel.com>
To: Pavitrakumar M <pavitrakumarm@vayavyalabs.com>,
herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Ruud.Derwig@synopsys.com,
manjunath.hadli@vayavyalabs.com, bhoomikak@vayavyalabs.com,
Pavitrakumar M <pavitrakumarm@vayavyalabs.com>
Subject: Re: [PATCH v1 4/4] Enable Driver compilation in crypto Kconfig and Makefile file
Date: Sat, 30 Mar 2024 08:40:37 +0800 [thread overview]
Message-ID: <202403300840.vE1pjy9E-lkp@intel.com> (raw)
In-Reply-To: <20240328182652.3587727-5-pavitrakumarm@vayavyalabs.com>
Hi Pavitrakumar,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 6a8dbd71a70620c42d4fa82509204ba18231f28d]
url: https://github.com/intel-lab-lkp/linux/commits/Pavitrakumar-M/Add-SPAcc-driver-to-Linux-kernel/20240329-023010
base: 6a8dbd71a70620c42d4fa82509204ba18231f28d
patch link: https://lore.kernel.org/r/20240328182652.3587727-5-pavitrakumarm%40vayavyalabs.com
patch subject: [PATCH v1 4/4] Enable Driver compilation in crypto Kconfig and Makefile file
config: mips-randconfig-r122-20240330 (https://download.01.org/0day-ci/archive/20240330/202403300840.vE1pjy9E-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 79ba323bdd0843275019e16b6e9b35133677c514)
reproduce: (https://download.01.org/0day-ci/archive/20240330/202403300840.vE1pjy9E-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/202403300840.vE1pjy9E-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/crypto/dwc-spacc/spacc_manager.c:135:46: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void volatile [noderef] __iomem *mem @@ got void * @@
drivers/crypto/dwc-spacc/spacc_manager.c:135:46: sparse: expected void volatile [noderef] __iomem *mem
drivers/crypto/dwc-spacc/spacc_manager.c:135:46: sparse: got void *
vim +135 drivers/crypto/dwc-spacc/spacc_manager.c
b37587c90bca57 Pavitrakumar M 2024-03-28 107
b37587c90bca57 Pavitrakumar M 2024-03-28 108 static int spacc_ctx_release(struct spacc_device *spacc, int ctx_id)
b37587c90bca57 Pavitrakumar M 2024-03-28 109 {
b37587c90bca57 Pavitrakumar M 2024-03-28 110 unsigned long lock_flag;
b37587c90bca57 Pavitrakumar M 2024-03-28 111 int ncontig;
b37587c90bca57 Pavitrakumar M 2024-03-28 112 int y;
b37587c90bca57 Pavitrakumar M 2024-03-28 113
b37587c90bca57 Pavitrakumar M 2024-03-28 114
b37587c90bca57 Pavitrakumar M 2024-03-28 115 if (ctx_id < 0 || ctx_id > spacc->config.num_ctx)
b37587c90bca57 Pavitrakumar M 2024-03-28 116 return -EINVAL;
b37587c90bca57 Pavitrakumar M 2024-03-28 117
b37587c90bca57 Pavitrakumar M 2024-03-28 118 spin_lock_irqsave(&spacc->ctx_lock, lock_flag);
b37587c90bca57 Pavitrakumar M 2024-03-28 119 /* release the base context and contiguous block */
b37587c90bca57 Pavitrakumar M 2024-03-28 120 ncontig = (&spacc->ctx[ctx_id])->ncontig;
b37587c90bca57 Pavitrakumar M 2024-03-28 121 for (y = 0; y <= ncontig; y++) {
b37587c90bca57 Pavitrakumar M 2024-03-28 122 if ((&spacc->ctx[ctx_id + y])->ref_cnt > 0)
b37587c90bca57 Pavitrakumar M 2024-03-28 123 (&spacc->ctx[ctx_id + y])->ref_cnt--;
b37587c90bca57 Pavitrakumar M 2024-03-28 124 }
b37587c90bca57 Pavitrakumar M 2024-03-28 125
b37587c90bca57 Pavitrakumar M 2024-03-28 126 if ((&spacc->ctx[ctx_id])->ref_cnt == 0) {
b37587c90bca57 Pavitrakumar M 2024-03-28 127 (&spacc->ctx[ctx_id])->ncontig = 0;
b37587c90bca57 Pavitrakumar M 2024-03-28 128 #ifdef CONFIG_CRYPTO_DEV_SPACC_SECURE_MODE
b37587c90bca57 Pavitrakumar M 2024-03-28 129 /* TODO: This driver works in harmony with "normal" kernel
b37587c90bca57 Pavitrakumar M 2024-03-28 130 * processes so we release the context all the time
b37587c90bca57 Pavitrakumar M 2024-03-28 131 * normally this would be done from a "secure" kernel process
b37587c90bca57 Pavitrakumar M 2024-03-28 132 * (trustzone/etc). This hack is so that SPACC.0
b37587c90bca57 Pavitrakumar M 2024-03-28 133 * cores can both use the same context space.
b37587c90bca57 Pavitrakumar M 2024-03-28 134 */
b37587c90bca57 Pavitrakumar M 2024-03-28 @135 writel(ctx_id, spacc->regmap + SPACC_REG_SECURE_RELEASE);
b37587c90bca57 Pavitrakumar M 2024-03-28 136 #endif
b37587c90bca57 Pavitrakumar M 2024-03-28 137 }
b37587c90bca57 Pavitrakumar M 2024-03-28 138
b37587c90bca57 Pavitrakumar M 2024-03-28 139 spin_unlock_irqrestore(&spacc->ctx_lock, lock_flag);
b37587c90bca57 Pavitrakumar M 2024-03-28 140
b37587c90bca57 Pavitrakumar M 2024-03-28 141 return CRYPTO_OK;
b37587c90bca57 Pavitrakumar M 2024-03-28 142 }
b37587c90bca57 Pavitrakumar M 2024-03-28 143
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-03-30 0:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 18:26 [PATCH v1 0/4] Add spacc crypto driver support Pavitrakumar M
2024-03-28 18:26 ` [PATCH v1 1/4] Add SPAcc driver to Linux kernel Pavitrakumar M
2024-03-29 17:56 ` Easwar Hariharan
2024-04-01 7:21 ` Pavitrakumar Managutte
2024-04-01 16:34 ` Easwar Hariharan
2024-04-02 5:02 ` Pavitrakumar Managutte
2024-03-28 18:26 ` [PATCH v1 2/4] Add SPACC Kconfig and Makefile Pavitrakumar M
2024-03-29 18:01 ` Easwar Hariharan
2024-03-28 18:26 ` [PATCH v1 3/4] Add SPAcc dts overlay Pavitrakumar M
2024-03-28 18:26 ` [PATCH v1 4/4] Enable Driver compilation in crypto Kconfig and Makefile file Pavitrakumar M
2024-03-30 0:40 ` kernel test robot [this message]
2024-04-05 7:08 ` [PATCH v1 0/4] Add spacc crypto driver support Herbert Xu
2024-04-11 5:31 ` Pavitrakumar Managutte
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=202403300840.vE1pjy9E-lkp@intel.com \
--to=lkp@intel.com \
--cc=Ruud.Derwig@synopsys.com \
--cc=bhoomikak@vayavyalabs.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=manjunath.hadli@vayavyalabs.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pavitrakumarm@vayavyalabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox