From: kernel test robot <lkp@intel.com>
To: Jorge Marques <jorge.marques@analog.com>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
David Lechner <dlechner@baylibre.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org,
Jorge Marques <jorge.marques@analog.com>
Subject: Re: [PATCH 4/4] iio: adc: add support for ad4052
Date: Fri, 7 Mar 2025 20:39:32 +0800 [thread overview]
Message-ID: <202503072008.ysqhEBaX-lkp@intel.com> (raw)
In-Reply-To: <20250306-iio-driver-ad4052-v1-4-2badad30116c@analog.com>
Hi Jorge,
kernel test robot noticed the following build warnings:
[auto build test WARNING on aac287ec80d71a7ab7e44c936a434625417c3e30]
url: https://github.com/intel-lab-lkp/linux/commits/Jorge-Marques/iio-code-mark-iio_dev-as-const-in-iio_buffer_enabled/20250306-220719
base: aac287ec80d71a7ab7e44c936a434625417c3e30
patch link: https://lore.kernel.org/r/20250306-iio-driver-ad4052-v1-4-2badad30116c%40analog.com
patch subject: [PATCH 4/4] iio: adc: add support for ad4052
config: powerpc-randconfig-r132-20250307 (https://download.01.org/0day-ci/archive/20250307/202503072008.ysqhEBaX-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 14.2.0
reproduce: (https://download.01.org/0day-ci/archive/20250307/202503072008.ysqhEBaX-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/202503072008.ysqhEBaX-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/iio/adc/ad4052.c:357:31: sparse: sparse: symbol 'ad4050_chip_info' was not declared. Should it be static?
>> drivers/iio/adc/ad4052.c:366:31: sparse: sparse: symbol 'ad4052_chip_info' was not declared. Should it be static?
>> drivers/iio/adc/ad4052.c:375:31: sparse: sparse: symbol 'ad4056_chip_info' was not declared. Should it be static?
>> drivers/iio/adc/ad4052.c:384:31: sparse: sparse: symbol 'ad4058_chip_info' was not declared. Should it be static?
>> drivers/iio/adc/ad4052.c:711:22: sparse: sparse: incorrect type in assignment (different base types) @@ expected int @@ got restricted __be16 [usertype] d16 @@
drivers/iio/adc/ad4052.c:711:22: sparse: expected int
drivers/iio/adc/ad4052.c:711:22: sparse: got restricted __be16 [usertype] d16
>> drivers/iio/adc/ad4052.c:715:22: sparse: sparse: incorrect type in assignment (different base types) @@ expected int @@ got restricted __be32 [usertype] d32 @@
drivers/iio/adc/ad4052.c:715:22: sparse: expected int
drivers/iio/adc/ad4052.c:715:22: sparse: got restricted __be32 [usertype] d32
drivers/iio/adc/ad4052.c:912:22: sparse: sparse: incorrect type in assignment (different base types) @@ expected int @@ got restricted __be32 [usertype] d32 @@
drivers/iio/adc/ad4052.c:912:22: sparse: expected int
drivers/iio/adc/ad4052.c:912:22: sparse: got restricted __be32 [usertype] d32
>> drivers/iio/adc/ad4052.c:958:33: sparse: sparse: bad assignment (>>=) to restricted __be16
drivers/iio/adc/ad4052.c:251:12: sparse: sparse: context imbalance in 'ad4052_iio_device_claim_direct' - different lock contexts for basic block
drivers/iio/adc/ad4052.c:277:9: sparse: sparse: context imbalance in 'ad4052_sample_rate_get' - unexpected unlock
drivers/iio/adc/ad4052.c:294:9: sparse: sparse: context imbalance in 'ad4052_sample_rate_set' - unexpected unlock
drivers/iio/adc/ad4052.c:780:34: sparse: sparse: context imbalance in 'ad4052_read_raw' - unexpected unlock
drivers/iio/adc/ad4052.c:805:34: sparse: sparse: context imbalance in 'ad4052_write_raw' - unexpected unlock
drivers/iio/adc/ad4052.c:820:9: sparse: sparse: context imbalance in 'ad4052_read_event_config' - unexpected unlock
drivers/iio/adc/ad4052.c:903:42: sparse: sparse: context imbalance in 'ad4052_read_event_value' - unexpected unlock
drivers/iio/adc/ad4052.c:971:34: sparse: sparse: context imbalance in 'ad4052_write_event_value' - unexpected unlock
drivers/iio/adc/ad4052.c:1055:34: sparse: sparse: context imbalance in 'ad4052_debugfs_reg_access' - unexpected unlock
vim +/ad4050_chip_info +357 drivers/iio/adc/ad4052.c
356
> 357 const struct ad4052_chip_info ad4050_chip_info = {
358 .name = "ad4050",
359 .channels = { AD4052_CHAN(12, AD4052_2MSPS) },
360 .offload_channels = { AD4052_OFFLOAD_CHAN(12, AD4052_2MSPS) },
361 .prod_id = 0x70,
362 .max_avg = AD4050_MAX_AVG,
363 .grade = AD4052_2MSPS,
364 };
365
> 366 const struct ad4052_chip_info ad4052_chip_info = {
367 .name = "ad4052",
368 .channels = { AD4052_CHAN(16, AD4052_2MSPS) },
369 .offload_channels = { AD4052_OFFLOAD_CHAN(16, AD4052_2MSPS) },
370 .prod_id = 0x72,
371 .max_avg = AD4052_MAX_AVG,
372 .grade = AD4052_2MSPS,
373 };
374
> 375 const struct ad4052_chip_info ad4056_chip_info = {
376 .name = "ad4056",
377 .channels = { AD4052_CHAN(12, AD4052_500KSPS) },
378 .offload_channels = { AD4052_OFFLOAD_CHAN(12, AD4052_500KSPS) },
379 .prod_id = 0x70,
380 .max_avg = AD4050_MAX_AVG,
381 .grade = AD4052_500KSPS,
382 };
383
> 384 const struct ad4052_chip_info ad4058_chip_info = {
385 .name = "ad4058",
386 .channels = { AD4052_CHAN(16, AD4052_500KSPS) },
387 .offload_channels = { AD4052_OFFLOAD_CHAN(16, AD4052_500KSPS) },
388 .prod_id = 0x72,
389 .max_avg = AD4052_MAX_AVG,
390 .grade = AD4052_500KSPS,
391 };
392
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-03-07 12:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 14:03 [PATCH 0/4] Add support for AD4052 device family Jorge Marques
2025-03-06 14:03 ` [PATCH 1/4] iio: code: mark iio_dev as const in iio_buffer_enabled Jorge Marques
2025-03-06 14:03 ` [PATCH 2/4] dt-bindings: iio: adc: Add adi,ad4052 Jorge Marques
2025-03-06 16:31 ` Conor Dooley
2025-03-08 15:05 ` Jonathan Cameron
2025-03-09 19:43 ` Jorge Marques
2025-03-10 19:35 ` Jonathan Cameron
2025-03-07 10:51 ` David Lechner
2025-03-09 20:11 ` Jorge Marques
2025-03-08 15:10 ` Jonathan Cameron
2025-03-09 20:25 ` Jorge Marques
2025-03-06 14:03 ` [PATCH 3/4] docs: iio: new docs for ad4052 driver Jorge Marques
2025-03-07 10:52 ` David Lechner
2025-03-09 20:49 ` Jorge Marques
2025-03-10 14:31 ` David Lechner
2025-03-10 19:56 ` Jonathan Cameron
2025-03-14 17:34 ` Jorge Marques
2025-03-15 18:24 ` Jonathan Cameron
2025-03-10 19:54 ` Jonathan Cameron
2025-03-14 18:13 ` Jorge Marques
2025-03-14 18:56 ` David Lechner
2025-03-19 16:59 ` Jorge Marques
2025-03-06 14:03 ` [PATCH 4/4] iio: adc: add support for ad4052 Jorge Marques
2025-03-07 12:06 ` kernel test robot
2025-03-07 12:39 ` kernel test robot [this message]
2025-03-07 14:22 ` kernel test robot
2025-03-08 16:02 ` Jonathan Cameron
2025-03-10 11:36 ` Jorge Marques
2025-03-08 16:12 ` Christophe JAILLET
2025-03-10 11:37 ` Jorge Marques
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=202503072008.ysqhEBaX-lkp@intel.com \
--to=lkp@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=jorge.marques@analog.com \
--cc=krzk@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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