From: kernel test robot <lkp@intel.com>
To: Jianping.Shen@de.bosch.com, jic23@kernel.org, lars@metafoo.de,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
dima.fedrau@gmail.com, marcelo.schmitt1@gmail.com,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Christian.Lorenz3@de.bosch.com,
Ulrike.Frauendorf@de.bosch.com, Kai.Dolde@de.bosch.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v3 2/2] iio: imu: smi240: imu driver
Date: Sat, 17 Aug 2024 09:56:07 +0800 [thread overview]
Message-ID: <202408170910.aR1gYef3-lkp@intel.com> (raw)
In-Reply-To: <20240815152545.7705-3-Jianping.Shen@de.bosch.com>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on jic23-iio/togreg]
[also build test WARNING on linus/master v6.11-rc3 next-20240816]
[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/Jianping-Shen-de-bosch-com/dt-bindings-iio-imu-smi240-devicetree-binding/20240815-234739
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
patch link: https://lore.kernel.org/r/20240815152545.7705-3-Jianping.Shen%40de.bosch.com
patch subject: [PATCH v3 2/2] iio: imu: smi240: imu driver
config: x86_64-randconfig-123-20240817 (https://download.01.org/0day-ci/archive/20240817/202408170910.aR1gYef3-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240817/202408170910.aR1gYef3-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/202408170910.aR1gYef3-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/iio/imu/smi240/smi240_core.c:207:9: sparse: sparse: dereference of noderef expression
>> drivers/iio/imu/smi240/smi240_core.c:207:9: sparse: sparse: dereference of noderef expression
>> drivers/iio/imu/smi240/smi240_core.c:207:9: sparse: sparse: dereference of noderef expression
--
>> drivers/iio/imu/smi240/smi240_spi.c:69:17: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __be32 [usertype] request @@ got int @@
drivers/iio/imu/smi240/smi240_spi.c:69:17: sparse: expected restricted __be32 [usertype] request
drivers/iio/imu/smi240/smi240_spi.c:69:17: sparse: got int
>> drivers/iio/imu/smi240/smi240_spi.c:70:17: sparse: sparse: invalid assignment: |=
drivers/iio/imu/smi240/smi240_spi.c:70:17: sparse: left side has type restricted __be32
drivers/iio/imu/smi240/smi240_spi.c:70:17: sparse: right side has type int
drivers/iio/imu/smi240/smi240_spi.c:71:17: sparse: sparse: invalid assignment: |=
drivers/iio/imu/smi240/smi240_spi.c:71:17: sparse: left side has type restricted __be32
drivers/iio/imu/smi240/smi240_spi.c:71:17: sparse: right side has type unsigned long
>> drivers/iio/imu/smi240/smi240_spi.c:72:32: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected unsigned int [usertype] data @@ got restricted __be32 [usertype] request @@
drivers/iio/imu/smi240/smi240_spi.c:72:32: sparse: expected unsigned int [usertype] data
drivers/iio/imu/smi240/smi240_spi.c:72:32: sparse: got restricted __be32 [usertype] request
drivers/iio/imu/smi240/smi240_spi.c:72:17: sparse: sparse: invalid assignment: |=
drivers/iio/imu/smi240/smi240_spi.c:72:17: sparse: left side has type restricted __be32
drivers/iio/imu/smi240/smi240_spi.c:72:17: sparse: right side has type unsigned char
>> drivers/iio/imu/smi240/smi240_spi.c:73:19: sparse: sparse: cast from restricted __be32
>> drivers/iio/imu/smi240/smi240_spi.c:89:18: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __be32 [addressable] [usertype] response @@ got unsigned int [usertype] @@
drivers/iio/imu/smi240/smi240_spi.c:89:18: sparse: expected restricted __be32 [addressable] [usertype] response
drivers/iio/imu/smi240/smi240_spi.c:89:18: sparse: got unsigned int [usertype]
>> drivers/iio/imu/smi240/smi240_spi.c:91:42: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected unsigned int [usertype] data @@ got restricted __be32 [addressable] [usertype] response @@
drivers/iio/imu/smi240/smi240_spi.c:91:42: sparse: expected unsigned int [usertype] data
drivers/iio/imu/smi240/smi240_spi.c:91:42: sparse: got restricted __be32 [addressable] [usertype] response
>> drivers/iio/imu/smi240/smi240_spi.c:94:20: sparse: sparse: cast to restricted __be32
>> drivers/iio/imu/smi240/smi240_spi.c:94:20: sparse: sparse: restricted __be32 degrades to integer
>> drivers/iio/imu/smi240/smi240_spi.c:94:20: sparse: sparse: restricted __be32 degrades to integer
>> drivers/iio/imu/smi240/smi240_spi.c:94:18: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __be32 [addressable] [usertype] response @@ got unsigned long @@
drivers/iio/imu/smi240/smi240_spi.c:94:18: sparse: expected restricted __be32 [addressable] [usertype] response
drivers/iio/imu/smi240/smi240_spi.c:94:18: sparse: got unsigned long
drivers/iio/imu/smi240/smi240_spi.c:108:17: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __be32 [usertype] request @@ got int @@
drivers/iio/imu/smi240/smi240_spi.c:108:17: sparse: expected restricted __be32 [usertype] request
drivers/iio/imu/smi240/smi240_spi.c:108:17: sparse: got int
drivers/iio/imu/smi240/smi240_spi.c:109:17: sparse: sparse: invalid assignment: |=
drivers/iio/imu/smi240/smi240_spi.c:109:17: sparse: left side has type restricted __be32
drivers/iio/imu/smi240/smi240_spi.c:109:17: sparse: right side has type int
drivers/iio/imu/smi240/smi240_spi.c:110:17: sparse: sparse: invalid assignment: |=
drivers/iio/imu/smi240/smi240_spi.c:110:17: sparse: left side has type restricted __be32
drivers/iio/imu/smi240/smi240_spi.c:110:17: sparse: right side has type unsigned long
drivers/iio/imu/smi240/smi240_spi.c:111:17: sparse: sparse: invalid assignment: |=
drivers/iio/imu/smi240/smi240_spi.c:111:17: sparse: left side has type restricted __be32
drivers/iio/imu/smi240/smi240_spi.c:111:17: sparse: right side has type unsigned long
drivers/iio/imu/smi240/smi240_spi.c:112:32: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected unsigned int [usertype] data @@ got restricted __be32 [usertype] request @@
drivers/iio/imu/smi240/smi240_spi.c:112:32: sparse: expected unsigned int [usertype] data
drivers/iio/imu/smi240/smi240_spi.c:112:32: sparse: got restricted __be32 [usertype] request
drivers/iio/imu/smi240/smi240_spi.c:112:17: sparse: sparse: invalid assignment: |=
drivers/iio/imu/smi240/smi240_spi.c:112:17: sparse: left side has type restricted __be32
drivers/iio/imu/smi240/smi240_spi.c:112:17: sparse: right side has type unsigned char
drivers/iio/imu/smi240/smi240_spi.c:113:19: sparse: sparse: cast from restricted __be32
vim +207 drivers/iio/imu/smi240/smi240_core.c
197
198 static irqreturn_t smi240_trigger_handler(int irq, void *p)
199 {
200 struct iio_poll_func *pf = p;
201 struct iio_dev *indio_dev = pf->indio_dev;
202 struct smi240_data *data = iio_priv(indio_dev);
203 int ret, sample, chan, i = 0;
204
205 data->capture = SMI240_CAPTURE_ON;
206
> 207 for_each_set_bit(chan, indio_dev->active_scan_mask,
208 indio_dev->masklength) {
209 ret = regmap_read(data->regmap,
210 SMI240_DATA_CAP_FIRST_REG + chan, &sample);
211 data->capture = SMI240_CAPTURE_OFF;
212 if (ret)
213 break;
214 data->buf[i++] = sample;
215 }
216
217 if (ret == 0)
218 iio_push_to_buffers_with_timestamp(indio_dev, data->buf,
219 pf->timestamp);
220
221 iio_trigger_notify_done(indio_dev->trig);
222 return IRQ_HANDLED;
223 }
224
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-08-17 1:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 15:25 [PATCH v3 0/2] iio: imu: smi240: cover-letter Jianping.Shen
2024-08-15 15:25 ` [PATCH v3 1/2] dt-bindings: iio: imu: smi240: devicetree binding Jianping.Shen
2024-08-15 15:34 ` Conor Dooley
2024-08-15 15:38 ` Conor Dooley
2024-08-16 7:26 ` Krzysztof Kozlowski
2024-08-15 15:25 ` [PATCH v3 2/2] iio: imu: smi240: imu driver Jianping.Shen
2024-08-17 1:56 ` kernel test robot [this message]
2024-08-17 16:13 ` kernel test robot
2024-08-17 16:17 ` Jonathan Cameron
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=202408170910.aR1gYef3-lkp@intel.com \
--to=lkp@intel.com \
--cc=Christian.Lorenz3@de.bosch.com \
--cc=Jianping.Shen@de.bosch.com \
--cc=Kai.Dolde@de.bosch.com \
--cc=Ulrike.Frauendorf@de.bosch.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dima.fedrau@gmail.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@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