From: kernel test robot <lkp@intel.com>
To: Chris Morgan <macroalpha82@gmail.com>, linux-iio@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, andy@kernel.org,
nuno.sa@analog.com, dlechner@baylibre.com, jic23@kernel.org,
jean-baptiste.maneyrol@tdk.com,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
heiko@sntech.de, conor+dt@kernel.org, krzk+dt@kernel.org,
robh@kernel.org, Chris Morgan <macromorgan@hotmail.com>
Subject: Re: [PATCH 2/3] iio: imu: inv_icm42607: add new inv_icm42607 driver
Date: Wed, 25 Feb 2026 04:05:37 +0800 [thread overview]
Message-ID: <202602250331.RTQ00zxY-lkp@intel.com> (raw)
In-Reply-To: <20260224163109.370930-3-macroalpha82@gmail.com>
Hi Chris,
kernel test robot noticed the following build warnings:
[auto build test WARNING on rockchip/for-next]
[also build test WARNING on linus/master v7.0-rc1 next-20260224]
[cannot apply to jic23-iio/togreg]
[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/Chris-Morgan/dt-bindings-iio-imu-icm42607-Add-devicetree-binding/20260225-003610
base: https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git for-next
patch link: https://lore.kernel.org/r/20260224163109.370930-3-macroalpha82%40gmail.com
patch subject: [PATCH 2/3] iio: imu: inv_icm42607: add new inv_icm42607 driver
config: sh-allyesconfig (https://download.01.org/0day-ci/archive/20260225/202602250331.RTQ00zxY-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260225/202602250331.RTQ00zxY-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/202602250331.RTQ00zxY-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/iio/imu/inv_icm42607/inv_icm42607_core.c: In function 'inv_icm42607_suspend':
>> drivers/iio/imu/inv_icm42607/inv_icm42607_core.c:670:13: warning: variable 'accel_conf' set but not used [-Wunused-but-set-variable]
670 | int accel_conf;
| ^~~~~~~~~~
--
>> drivers/iio/imu/inv_icm42607/inv_icm42607_accel.c:200:36: warning: 'inv_icm42607_motion_events' defined but not used [-Wunused-const-variable=]
200 | static const struct iio_event_spec inv_icm42607_motion_events[] = {
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/accel_conf +670 drivers/iio/imu/inv_icm42607/inv_icm42607_core.c
660
661 /*
662 * Suspend saves sensors state and turns everything off.
663 * Check first if runtime suspend has not already done the job.
664 */
665 static int inv_icm42607_suspend(struct device *dev)
666 {
667 struct inv_icm42607_state *st = dev_get_drvdata(dev);
668 struct device *accel_dev;
669 bool wakeup;
> 670 int accel_conf;
671 int ret = 0;
672
673 guard(mutex)(&st->lock);
674
675 st->suspended.gyro = st->conf.gyro.mode;
676 st->suspended.accel = st->conf.accel.mode;
677 st->suspended.temp = st->conf.temp_en;
678 if (pm_runtime_suspended(dev))
679 return 0;
680
681 if (st->fifo.on) {
682 ret = regmap_write(st->map, INV_ICM42607_REG_FIFO_CONFIG1,
683 INV_ICM42607_FIFO_CONFIG1_BYPASS);
684 if (ret)
685 return ret;
686 }
687
688 /* keep chip on and wake-up capable if APEX and wakeup on */
689 accel_dev = &st->indio_accel->dev;
690 wakeup = st->apex.on && device_may_wakeup(accel_dev);
691 if (wakeup) {
692 /* keep accel on and setup irq for wakeup */
693 accel_conf = st->conf.accel.mode;
694 enable_irq_wake(st->irq);
695 disable_irq(st->irq);
696 } else {
697 /* disable APEX features and accel if wakeup disabled */
698 if (st->apex.wom.enable) {
699 ret = inv_icm42607_disable_wom(st);
700 if (ret)
701 return ret;
702 }
703 accel_conf = INV_ICM42607_SENSOR_MODE_OFF;
704 }
705
706 ret = inv_icm42607_set_pwr_mgmt0(st, INV_ICM42607_SENSOR_MODE_OFF,
707 INV_ICM42607_SENSOR_MODE_OFF, false,
708 NULL);
709 if (ret)
710 return ret;
711
712 if (!wakeup)
713 regulator_disable(st->vddio_supply);
714
715 return 0;
716 }
717
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Chris Morgan <macroalpha82@gmail.com>, linux-iio@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, andy@kernel.org,
nuno.sa@analog.com, dlechner@baylibre.com, jic23@kernel.org,
jean-baptiste.maneyrol@tdk.com,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
heiko@sntech.de, conor+dt@kernel.org, krzk+dt@kernel.org,
robh@kernel.org, Chris Morgan <macromorgan@hotmail.com>
Subject: Re: [PATCH 2/3] iio: imu: inv_icm42607: add new inv_icm42607 driver
Date: Wed, 25 Feb 2026 04:05:37 +0800 [thread overview]
Message-ID: <202602250331.RTQ00zxY-lkp@intel.com> (raw)
In-Reply-To: <20260224163109.370930-3-macroalpha82@gmail.com>
Hi Chris,
kernel test robot noticed the following build warnings:
[auto build test WARNING on rockchip/for-next]
[also build test WARNING on linus/master v7.0-rc1 next-20260224]
[cannot apply to jic23-iio/togreg]
[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/Chris-Morgan/dt-bindings-iio-imu-icm42607-Add-devicetree-binding/20260225-003610
base: https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git for-next
patch link: https://lore.kernel.org/r/20260224163109.370930-3-macroalpha82%40gmail.com
patch subject: [PATCH 2/3] iio: imu: inv_icm42607: add new inv_icm42607 driver
config: sh-allyesconfig (https://download.01.org/0day-ci/archive/20260225/202602250331.RTQ00zxY-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260225/202602250331.RTQ00zxY-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/202602250331.RTQ00zxY-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/iio/imu/inv_icm42607/inv_icm42607_core.c: In function 'inv_icm42607_suspend':
>> drivers/iio/imu/inv_icm42607/inv_icm42607_core.c:670:13: warning: variable 'accel_conf' set but not used [-Wunused-but-set-variable]
670 | int accel_conf;
| ^~~~~~~~~~
--
>> drivers/iio/imu/inv_icm42607/inv_icm42607_accel.c:200:36: warning: 'inv_icm42607_motion_events' defined but not used [-Wunused-const-variable=]
200 | static const struct iio_event_spec inv_icm42607_motion_events[] = {
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/accel_conf +670 drivers/iio/imu/inv_icm42607/inv_icm42607_core.c
660
661 /*
662 * Suspend saves sensors state and turns everything off.
663 * Check first if runtime suspend has not already done the job.
664 */
665 static int inv_icm42607_suspend(struct device *dev)
666 {
667 struct inv_icm42607_state *st = dev_get_drvdata(dev);
668 struct device *accel_dev;
669 bool wakeup;
> 670 int accel_conf;
671 int ret = 0;
672
673 guard(mutex)(&st->lock);
674
675 st->suspended.gyro = st->conf.gyro.mode;
676 st->suspended.accel = st->conf.accel.mode;
677 st->suspended.temp = st->conf.temp_en;
678 if (pm_runtime_suspended(dev))
679 return 0;
680
681 if (st->fifo.on) {
682 ret = regmap_write(st->map, INV_ICM42607_REG_FIFO_CONFIG1,
683 INV_ICM42607_FIFO_CONFIG1_BYPASS);
684 if (ret)
685 return ret;
686 }
687
688 /* keep chip on and wake-up capable if APEX and wakeup on */
689 accel_dev = &st->indio_accel->dev;
690 wakeup = st->apex.on && device_may_wakeup(accel_dev);
691 if (wakeup) {
692 /* keep accel on and setup irq for wakeup */
693 accel_conf = st->conf.accel.mode;
694 enable_irq_wake(st->irq);
695 disable_irq(st->irq);
696 } else {
697 /* disable APEX features and accel if wakeup disabled */
698 if (st->apex.wom.enable) {
699 ret = inv_icm42607_disable_wom(st);
700 if (ret)
701 return ret;
702 }
703 accel_conf = INV_ICM42607_SENSOR_MODE_OFF;
704 }
705
706 ret = inv_icm42607_set_pwr_mgmt0(st, INV_ICM42607_SENSOR_MODE_OFF,
707 INV_ICM42607_SENSOR_MODE_OFF, false,
708 NULL);
709 if (ret)
710 return ret;
711
712 if (!wakeup)
713 regulator_disable(st->vddio_supply);
714
715 return 0;
716 }
717
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2026-02-24 20:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 16:31 [PATCH 0/3] Add Invensense ICM42607 Chris Morgan
2026-02-24 16:31 ` Chris Morgan
2026-02-24 16:31 ` [PATCH 1/3] dt-bindings: iio: imu: icm42607: Add devicetree binding Chris Morgan
2026-02-24 16:31 ` Chris Morgan
2026-02-24 17:29 ` Rob Herring (Arm)
2026-02-24 17:29 ` Rob Herring (Arm)
2026-02-24 16:31 ` [PATCH 2/3] iio: imu: inv_icm42607: add new inv_icm42607 driver Chris Morgan
2026-02-24 16:31 ` Chris Morgan
2026-02-24 20:05 ` kernel test robot [this message]
2026-02-24 20:05 ` kernel test robot
2026-02-25 0:04 ` kernel test robot
2026-02-25 0:04 ` kernel test robot
2026-02-25 3:21 ` kernel test robot
2026-02-25 3:21 ` kernel test robot
2026-02-28 18:52 ` Jonathan Cameron
2026-02-28 18:52 ` Jonathan Cameron
2026-02-24 16:31 ` [PATCH 3/3] arm64: dts: rockchip: Add icm42607p IMU for RG-DS Chris Morgan
2026-02-24 16:31 ` Chris Morgan
2026-02-24 17:41 ` [PATCH 0/3] Add Invensense ICM42607 Andy Shevchenko
2026-02-24 17:41 ` Andy Shevchenko
2026-02-25 14:20 ` Chris Morgan
2026-02-25 14:20 ` Chris Morgan
2026-02-25 17:13 ` Andy Shevchenko
2026-02-25 17:13 ` Andy Shevchenko
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=202602250331.RTQ00zxY-lkp@intel.com \
--to=lkp@intel.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=heiko@sntech.de \
--cc=jean-baptiste.maneyrol@tdk.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=macroalpha82@gmail.com \
--cc=macromorgan@hotmail.com \
--cc=nuno.sa@analog.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 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.