public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Alex Lanzano <lanzano.alex@gmail.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>,
	Jagath Jog J <jagathjog1996@gmail.com>,
	Ramona Gradinariu <ramona.bolboaca13@gmail.com>,
	Nuno Sa <nuno.sa@analog.com>
Cc: oe-kbuild-all@lists.linux.dev, skhan@linuxfoundation.org,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] iio: imu: Add i2c driver for bmi270 imu
Date: Tue, 10 Sep 2024 01:03:04 +0800	[thread overview]
Message-ID: <202409100026.17N3K11W-lkp@intel.com> (raw)
In-Reply-To: <20240909043254.611589-3-lanzano.alex@gmail.com>

Hi Alex,

kernel test robot noticed the following build errors:

[auto build test ERROR on jic23-iio/togreg]
[also build test ERROR on robh/for-next linus/master v6.11-rc7 next-20240909]
[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/Alex-Lanzano/dt-bindings-iio-imu-add-bmi270-bindings/20240909-123509
base:   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
patch link:    https://lore.kernel.org/r/20240909043254.611589-3-lanzano.alex%40gmail.com
patch subject: [PATCH v3 2/2] iio: imu: Add i2c driver for bmi270 imu
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20240910/202409100026.17N3K11W-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240910/202409100026.17N3K11W-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/202409100026.17N3K11W-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/iio/imu/bmi270/bmi270_core.c: In function 'bmi270_configure_imu':
>> drivers/iio/imu/bmi270/bmi270_core.c:180:31: error: implicit declaration of function 'FIELD_PREP' [-Wimplicit-function-declaration]
     180 |                               FIELD_PREP(BMI270_ACC_CONF_ODR_MSK,
         |                               ^~~~~~~~~~


vim +/FIELD_PREP +180 drivers/iio/imu/bmi270/bmi270_core.c

   165	
   166	static int bmi270_configure_imu(struct bmi270_data *bmi270_device)
   167	{
   168		int ret;
   169		struct device *dev = bmi270_device->dev;
   170		struct regmap *regmap = bmi270_device->regmap;
   171	
   172		ret = regmap_set_bits(regmap, BMI270_PWR_CTRL_REG,
   173				      BMI270_PWR_CTRL_AUX_EN_MSK |
   174				      BMI270_PWR_CTRL_GYR_EN_MSK |
   175				      BMI270_PWR_CTRL_ACCEL_EN_MSK);
   176		if (ret)
   177			return dev_err_probe(dev, ret, "Failed to enable accelerometer and gyroscope");
   178	
   179		ret = regmap_set_bits(regmap, BMI270_ACC_CONF_REG,
 > 180				      FIELD_PREP(BMI270_ACC_CONF_ODR_MSK,
   181						 BMI270_ACC_CONF_ODR_100HZ) |
   182				      FIELD_PREP(BMI270_ACC_CONF_BWP_MSK,
   183						 BMI270_ACC_CONF_BWP_NORMAL_MODE) |
   184				      BMI270_PWR_CONF_ADV_PWR_SAVE_MSK);
   185		if (ret)
   186			return dev_err_probe(dev, ret, "Failed to configure accelerometer");
   187	
   188		ret = regmap_set_bits(regmap, BMI270_GYR_CONF_REG,
   189				      FIELD_PREP(BMI270_GYR_CONF_ODR_MSK,
   190						 BMI270_GYR_CONF_ODR_200HZ) |
   191				      FIELD_PREP(BMI270_GYR_CONF_BWP_MSK,
   192						 BMI270_GYR_CONF_BWP_NORMAL_MODE) |
   193				      BMI270_PWR_CONF_ADV_PWR_SAVE_MSK);
   194		if (ret)
   195			return dev_err_probe(dev, ret, "Failed to configure gyroscope");
   196	
   197		/* Enable FIFO_WKUP, Disable ADV_PWR_SAVE and FUP_EN */
   198		ret = regmap_write(regmap, BMI270_PWR_CONF_REG,
   199				   BMI270_PWR_CONF_FIFO_WKUP_MSK);
   200		if (ret)
   201			return dev_err_probe(dev, ret, "Failed to set power configuration");
   202	
   203		return 0;
   204	}
   205	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2024-09-09 17:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-09  4:32 [PATCH v3 0/2] Add I2C driver for Bosch BMI270 IMU Alex Lanzano
2024-09-09  4:32 ` [PATCH v3 1/2] dt-bindings: iio: imu: add bmi270 bindings Alex Lanzano
2024-09-09  4:32 ` [PATCH v3 2/2] iio: imu: Add i2c driver for bmi270 imu Alex Lanzano
2024-09-09 17:03   ` kernel test robot [this message]
2024-09-10  3:21     ` Alex Lanzano
2024-09-14 11:51       ` Jonathan Cameron
2024-09-09 22:13   ` kernel test robot
2024-09-10  3:24     ` Alex Lanzano
2024-09-10 22:22 ` [PATCH v3 0/2] Add I2C driver for Bosch BMI270 IMU Vasileios Amoiridis
2024-09-11 12:38   ` Alex Lanzano

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=202409100026.17N3K11W-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jagathjog1996@gmail.com \
    --cc=jic23@kernel.org \
    --cc=krzk@kernel.org \
    --cc=lanzano.alex@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ramona.bolboaca13@gmail.com \
    --cc=robh@kernel.org \
    --cc=skhan@linuxfoundation.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