From: kernel test robot <lkp@intel.com>
To: Liviu Stan <liviu.stan@analog.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Jonathan Cameron <jic23@kernel.org>
Subject: drivers/iio/temperature/ltc2983.c:1895:1: warning: the frame size of 1136 bytes is larger than 1024 bytes
Date: Sat, 26 Sep 2026 00:16:49 +0200 [thread overview]
Message-ID: <202609260048.kjlkLMOK-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 165768bb70265b5c38cf0b73fafd75be235f8b14
commit: 3dd0c048409e335320418c632966f149be628fd4 iio: temperature: ltc2983: Add support for ADT7604
date: 4 months ago
config: sparc-allyesconfig (https://download.01.org/0day-ci/archive/20260926/202609260048.kjlkLMOK-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260926/202609260048.kjlkLMOK-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
| Fixes: 3dd0c048409e ("iio: temperature: ltc2983: Add support for ADT7604")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202609260048.kjlkLMOK-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/iio/temperature/ltc2983.c: In function 'ltc2983_setup':
>> drivers/iio/temperature/ltc2983.c:1895:1: warning: the frame size of 1136 bytes is larger than 1024 bytes [-Wframe-larger-than=]
1895 | }
| ^
vim +1895 drivers/iio/temperature/ltc2983.c
6f7cadcf664b04 Cosmin Tanislav 2022-11-03 1805
f110f3188e5639 Nuno Sá 2019-10-11 1806 static int ltc2983_setup(struct ltc2983_data *st, bool assign_iio)
f110f3188e5639 Nuno Sá 2019-10-11 1807 {
6b047d099703c9 Liviu Stan 2026-05-25 1808 struct device *dev = &st->spi->dev;
3dd0c048409e33 Liviu Stan 2026-05-25 1809 u32 iio_chan_t = 0, iio_chan_v = 0, iio_chan_r = 0, iio_chan_c = 0;
3dd0c048409e33 Liviu Stan 2026-05-25 1810 u32 chan, iio_idx = 0, status;
f110f3188e5639 Nuno Sá 2019-10-11 1811 int ret;
f110f3188e5639 Nuno Sá 2019-10-11 1812
b76d26d69ecc97 Nuno Sá 2021-08-11 1813 /* make sure the device is up: start bit (7) is 0 and done bit (6) is 1 */
b76d26d69ecc97 Nuno Sá 2021-08-11 1814 ret = regmap_read_poll_timeout(st->regmap, LTC2983_STATUS_REG, status,
b76d26d69ecc97 Nuno Sá 2021-08-11 1815 LTC2983_STATUS_UP(status) == 1, 25000,
b76d26d69ecc97 Nuno Sá 2021-08-11 1816 25000 * 10);
a00838cae079b9 Nuno Sa 2024-06-06 1817 if (ret)
6b047d099703c9 Liviu Stan 2026-05-25 1818 return dev_err_probe(dev, ret, "Device startup timed out\n");
f110f3188e5639 Nuno Sá 2019-10-11 1819
f110f3188e5639 Nuno Sá 2019-10-11 1820 ret = regmap_update_bits(st->regmap, LTC2983_GLOBAL_CONFIG_REG,
f110f3188e5639 Nuno Sá 2019-10-11 1821 LTC2983_NOTCH_FREQ_MASK,
f110f3188e5639 Nuno Sá 2019-10-11 1822 LTC2983_NOTCH_FREQ(st->filter_notch_freq));
f110f3188e5639 Nuno Sá 2019-10-11 1823 if (ret)
f110f3188e5639 Nuno Sá 2019-10-11 1824 return ret;
f110f3188e5639 Nuno Sá 2019-10-11 1825
f110f3188e5639 Nuno Sá 2019-10-11 1826 ret = regmap_write(st->regmap, LTC2983_MUX_CONFIG_REG,
f110f3188e5639 Nuno Sá 2019-10-11 1827 st->mux_delay_config);
f110f3188e5639 Nuno Sá 2019-10-11 1828 if (ret)
f110f3188e5639 Nuno Sá 2019-10-11 1829 return ret;
f110f3188e5639 Nuno Sá 2019-10-11 1830
6f7cadcf664b04 Cosmin Tanislav 2022-11-03 1831 if (st->info->has_eeprom && !assign_iio) {
6f7cadcf664b04 Cosmin Tanislav 2022-11-03 1832 ret = ltc2983_eeprom_cmd(st, LTC2983_EEPROM_READ_CMD,
6f7cadcf664b04 Cosmin Tanislav 2022-11-03 1833 LTC2983_EEPROM_READ_TIME_MS,
6f7cadcf664b04 Cosmin Tanislav 2022-11-03 1834 LTC2983_EEPROM_READ_STATUS_REG,
6f7cadcf664b04 Cosmin Tanislav 2022-11-03 1835 LTC2983_EEPROM_READ_FAILURE_MASK);
6f7cadcf664b04 Cosmin Tanislav 2022-11-03 1836 if (!ret)
6f7cadcf664b04 Cosmin Tanislav 2022-11-03 1837 return 0;
6f7cadcf664b04 Cosmin Tanislav 2022-11-03 1838 }
6f7cadcf664b04 Cosmin Tanislav 2022-11-03 1839
f110f3188e5639 Nuno Sá 2019-10-11 1840 for (chan = 0; chan < st->num_channels; chan++) {
f110f3188e5639 Nuno Sá 2019-10-11 1841 u32 chan_type = 0, *iio_chan;
f110f3188e5639 Nuno Sá 2019-10-11 1842
f110f3188e5639 Nuno Sá 2019-10-11 1843 ret = st->sensors[chan]->assign_chan(st, st->sensors[chan]);
f110f3188e5639 Nuno Sá 2019-10-11 1844 if (ret)
f110f3188e5639 Nuno Sá 2019-10-11 1845 return ret;
f110f3188e5639 Nuno Sá 2019-10-11 1846 /*
f110f3188e5639 Nuno Sá 2019-10-11 1847 * The assign_iio flag is necessary for when the device is
f110f3188e5639 Nuno Sá 2019-10-11 1848 * coming out of sleep. In that case, we just need to
f110f3188e5639 Nuno Sá 2019-10-11 1849 * re-configure the device channels.
f110f3188e5639 Nuno Sá 2019-10-11 1850 * We also don't assign iio channels for rsense.
f110f3188e5639 Nuno Sá 2019-10-11 1851 */
f110f3188e5639 Nuno Sá 2019-10-11 1852 if (st->sensors[chan]->type == LTC2983_SENSOR_SENSE_RESISTOR ||
f110f3188e5639 Nuno Sá 2019-10-11 1853 !assign_iio)
f110f3188e5639 Nuno Sá 2019-10-11 1854 continue;
f110f3188e5639 Nuno Sá 2019-10-11 1855
f110f3188e5639 Nuno Sá 2019-10-11 1856 /* assign iio channel */
3dd0c048409e33 Liviu Stan 2026-05-25 1857 switch (st->sensors[chan]->type) {
3dd0c048409e33 Liviu Stan 2026-05-25 1858 case LTC2983_SENSOR_COPPER_TRACE:
3dd0c048409e33 Liviu Stan 2026-05-25 1859 if (st->sensors[chan]->n_iio_chan == 1) {
3dd0c048409e33 Liviu Stan 2026-05-25 1860 /* sub-ohm copper traces produce only a resistance result */
3dd0c048409e33 Liviu Stan 2026-05-25 1861 st->iio_chan[iio_idx++] =
3dd0c048409e33 Liviu Stan 2026-05-25 1862 LTC2983_CHAN(IIO_RESISTANCE, iio_chan_r++, chan);
f110f3188e5639 Nuno Sá 2019-10-11 1863 } else {
3dd0c048409e33 Liviu Stan 2026-05-25 1864 st->iio_chan[iio_idx++] =
3dd0c048409e33 Liviu Stan 2026-05-25 1865 LTC2983_CHAN(IIO_TEMP, iio_chan_t++, chan);
3dd0c048409e33 Liviu Stan 2026-05-25 1866 st->iio_chan[iio_idx++] =
3dd0c048409e33 Liviu Stan 2026-05-25 1867 LTC2983_CHAN(IIO_RESISTANCE, iio_chan_r++, chan);
3dd0c048409e33 Liviu Stan 2026-05-25 1868 }
3dd0c048409e33 Liviu Stan 2026-05-25 1869 continue;
3dd0c048409e33 Liviu Stan 2026-05-25 1870 case LTC2983_SENSOR_LEAK_DETECTOR:
3dd0c048409e33 Liviu Stan 2026-05-25 1871 st->iio_chan[iio_idx++] =
3dd0c048409e33 Liviu Stan 2026-05-25 1872 LTC2983_CHAN(IIO_COVERAGE, iio_chan_c++, chan);
3dd0c048409e33 Liviu Stan 2026-05-25 1873 st->iio_chan[iio_idx++] =
3dd0c048409e33 Liviu Stan 2026-05-25 1874 LTC2983_CHAN(IIO_RESISTANCE, iio_chan_r++, chan);
3dd0c048409e33 Liviu Stan 2026-05-25 1875 continue;
3dd0c048409e33 Liviu Stan 2026-05-25 1876 case LTC2983_SENSOR_DIRECT_ADC:
f110f3188e5639 Nuno Sá 2019-10-11 1877 chan_type = IIO_VOLTAGE;
f110f3188e5639 Nuno Sá 2019-10-11 1878 iio_chan = &iio_chan_v;
3dd0c048409e33 Liviu Stan 2026-05-25 1879 break;
3dd0c048409e33 Liviu Stan 2026-05-25 1880 default:
3dd0c048409e33 Liviu Stan 2026-05-25 1881 chan_type = IIO_TEMP;
3dd0c048409e33 Liviu Stan 2026-05-25 1882 iio_chan = &iio_chan_t;
3dd0c048409e33 Liviu Stan 2026-05-25 1883 break;
f110f3188e5639 Nuno Sá 2019-10-11 1884 }
f110f3188e5639 Nuno Sá 2019-10-11 1885
f110f3188e5639 Nuno Sá 2019-10-11 1886 /*
f110f3188e5639 Nuno Sá 2019-10-11 1887 * add chan as the iio .address so that, we can directly
f110f3188e5639 Nuno Sá 2019-10-11 1888 * reference the sensor given the iio_chan_spec
f110f3188e5639 Nuno Sá 2019-10-11 1889 */
f110f3188e5639 Nuno Sá 2019-10-11 1890 st->iio_chan[iio_idx++] = LTC2983_CHAN(chan_type, (*iio_chan)++,
f110f3188e5639 Nuno Sá 2019-10-11 1891 chan);
f110f3188e5639 Nuno Sá 2019-10-11 1892 }
f110f3188e5639 Nuno Sá 2019-10-11 1893
f110f3188e5639 Nuno Sá 2019-10-11 1894 return 0;
f110f3188e5639 Nuno Sá 2019-10-11 @1895 }
f110f3188e5639 Nuno Sá 2019-10-11 1896
:::::: The code at line 1895 was first introduced by commit
:::::: f110f3188e5639c81c457b2b831d40dfe3891bdb iio: temperature: Add support for LTC2983
:::::: TO: Nuno Sá <nuno.sa@analog.com>
:::::: CC: Jonathan Cameron <Jonathan.Cameron@huawei.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-25 22:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202609260048.kjlkLMOK-lkp@intel.com \
--to=lkp@intel.com \
--cc=jic23@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.stan@analog.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.