From: kernel test robot <lkp@intel.com>
To: Thomas Bonnefille <thomas.bonnefille@bootlin.com>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Chen Wang <unicorn_wang@outlook.com>,
Inochi Amaoto <inochiama@outlook.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Miquèl Raynal" <miquel.raynal@bootlin.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
"Thomas Bonnefille" <thomas.bonnefille@bootlin.com>
Subject: Re: [PATCH v5 2/3] iio: adc: sophgo-saradc: Add driver for Sophgo CV1800B SARADC
Date: Sat, 31 Aug 2024 08:45:16 +0800 [thread overview]
Message-ID: <202408310817.GT3TMpnv-lkp@intel.com> (raw)
In-Reply-To: <20240829-sg2002-adc-v5-2-aacb381e869b@bootlin.com>
Hi Thomas,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 5be63fc19fcaa4c236b307420483578a56986a37]
url: https://github.com/intel-lab-lkp/linux/commits/Thomas-Bonnefille/dt-bindings-iio-adc-sophgo-cv1800b-saradc-Add-Sophgo-CV1800B-SARADC/20240829-203431
base: 5be63fc19fcaa4c236b307420483578a56986a37
patch link: https://lore.kernel.org/r/20240829-sg2002-adc-v5-2-aacb381e869b%40bootlin.com
patch subject: [PATCH v5 2/3] iio: adc: sophgo-saradc: Add driver for Sophgo CV1800B SARADC
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20240831/202408310817.GT3TMpnv-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/20240831/202408310817.GT3TMpnv-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/202408310817.GT3TMpnv-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/iio/adc/sophgo-cv1800b-adc.c:120:3: warning: label followed by a declaration is a C23 extension [-Wc23-extensions]
120 | u32 status_reg = readl(saradc->regs + CV1800B_ADC_CYC_SET_REG);
| ^
1 warning generated.
vim +120 drivers/iio/adc/sophgo-cv1800b-adc.c
88
89 static int cv1800b_adc_read_raw(struct iio_dev *indio_dev,
90 struct iio_chan_spec const *chan,
91 int *val, int *val2, long mask)
92 {
93 struct cv1800b_adc *saradc = iio_priv(indio_dev);
94
95 switch (mask) {
96 case IIO_CHAN_INFO_RAW:{
97 u32 sample;
98
99 scoped_guard(mutex, &saradc->lock) {
100 int ret;
101
102 cv1800b_adc_start_measurement(saradc, chan->scan_index);
103 ret = cv1800b_adc_wait(saradc);
104 if (ret < 0)
105 return ret;
106
107 sample = readl(saradc->regs + CV1800B_ADC_CH_RESULT_REG(chan->scan_index));
108 }
109 if (!(sample & CV1800B_ADC_CH_VALID))
110 return -ENODATA;
111
112 *val = sample & CV1800B_ADC_CH_RESULT;
113 return IIO_VAL_INT;
114 }
115 case IIO_CHAN_INFO_SCALE:
116 *val = 3300;
117 *val2 = 12;
118 return IIO_VAL_FRACTIONAL_LOG2;
119 case IIO_CHAN_INFO_SAMP_FREQ:
> 120 u32 status_reg = readl(saradc->regs + CV1800B_ADC_CYC_SET_REG);
121 int clk_div = (1 + FIELD_GET(CV1800B_MASK_CLKDIV, status_reg));
122 int freq = clk_get_rate(saradc->clk) / clk_div;
123 int nb_startup_cycle = 1 + FIELD_GET(CV1800B_MASK_STARTUP_CYCLE, status_reg);
124 int nb_sample_cycle = 1 + FIELD_GET(CV1800B_MASK_SAMPLE_WINDOW, status_reg);
125 int nb_compare_cycle = 1 + FIELD_GET(CV1800B_MASK_COMPARE_CYCLE, status_reg);
126
127 *val = freq / (nb_startup_cycle + nb_sample_cycle + nb_compare_cycle);
128 return IIO_VAL_INT;
129 default:
130 return -EINVAL;
131 }
132 }
133
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-08-31 0:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 12:31 [PATCH v5 0/3] Add SARADC support on Sophgo CV18XX series Thomas Bonnefille
2024-08-29 12:31 ` [PATCH v5 1/3] dt-bindings: iio: adc: sophgo,cv1800b-saradc: Add Sophgo CV1800B SARADC Thomas Bonnefille
2024-08-29 15:54 ` Conor Dooley
2024-08-29 12:31 ` [PATCH v5 2/3] iio: adc: sophgo-saradc: Add driver for " Thomas Bonnefille
2024-08-31 0:45 ` kernel test robot [this message]
2024-08-31 11:10 ` Jonathan Cameron
2024-09-02 20:36 ` Andy Shevchenko
2024-09-03 19:05 ` Jonathan Cameron
2024-09-04 20:38 ` Thomas Bonnefille
2024-08-29 12:31 ` [PATCH v5 3/3] riscv: dts: sophgo: Add SARADC description for Sophgo CV1800B Thomas Bonnefille
2024-08-31 12:49 ` Inochi Amaoto
2024-10-22 0:38 ` Inochi Amaoto
2024-08-31 11:14 ` [PATCH v5 0/3] Add SARADC support on Sophgo CV18XX series Jonathan Cameron
2024-10-22 0:48 ` (subset) " Inochi Amaoto
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=202408310817.GT3TMpnv-lkp@intel.com \
--to=lkp@intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@outlook.com \
--cc=jic23@kernel.org \
--cc=krzk@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=miquel.raynal@bootlin.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=thomas.bonnefille@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=unicorn_wang@outlook.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;
as well as URLs for NNTP newsgroup(s).