All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Andrew Davis <afd@ti.com>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>
Subject: drivers/i2c/busses/i2c-omap.c:608:24: error: implicit declaration of function 'FIELD_PREP'
Date: Tue, 08 Sep 2026 00:41:57 +0200	[thread overview]
Message-ID: <202609080003.dbREhhYS-lkp@intel.com> (raw)

tree:   https://github.com/intel-lab-lkp/linux/commits/Andrew-Davis/i2c-omap-Drop-bit-shift-for-I2C-register-addresses/20260904-081245
head:   80bb64593f6862ec848394a6fc7e7946dcb93fe1
commit: 80bb64593f6862ec848394a6fc7e7946dcb93fe1 i2c: omap: Add OMAP_I2C_BUF_{TX,RX}TRSH definitions
date:   24 hours ago
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20260908/202609080003.dbREhhYS-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260908/202609080003.dbREhhYS-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/202609080003.dbREhhYS-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/i2c/busses/i2c-omap.c: In function 'omap_i2c_resize_fifo':
>> drivers/i2c/busses/i2c-omap.c:608:24: error: implicit declaration of function 'FIELD_PREP' [-Wimplicit-function-declaration]
     608 |                 buf |= FIELD_PREP(OMAP_I2C_BUF_RXTRSH, (omap->threshold - 1));
         |                        ^~~~~~~~~~


vim +/FIELD_PREP +608 drivers/i2c/busses/i2c-omap.c

   586	
   587	static void omap_i2c_resize_fifo(struct omap_i2c_dev *omap, u8 size, bool is_rx)
   588	{
   589		u16		buf;
   590	
   591		if (omap->flags & OMAP_I2C_FLAG_NO_FIFO)
   592			return;
   593	
   594		/*
   595		 * Set up notification threshold based on message size. We're doing
   596		 * this to try and avoid draining feature as much as possible. Whenever
   597		 * we have big messages to transfer (bigger than our total fifo size)
   598		 * then we might use draining feature to transfer the remaining bytes.
   599		 */
   600	
   601		omap->threshold = clamp(size, (u8) 1, omap->fifo_size);
   602	
   603		buf = omap_i2c_read_reg(omap, OMAP_I2C_BUF_REG);
   604	
   605		if (is_rx) {
   606			/* Clear RX Threshold */
   607			buf &= ~OMAP_I2C_BUF_RXTRSH;
 > 608			buf |= FIELD_PREP(OMAP_I2C_BUF_RXTRSH, (omap->threshold - 1));
   609			buf |= OMAP_I2C_BUF_RXFIF_CLR;
   610		} else {
   611			/* Clear TX Threshold */
   612			buf &= ~OMAP_I2C_BUF_TXTRSH;
   613			buf |= FIELD_PREP(OMAP_I2C_BUF_TXTRSH, (omap->threshold - 1));
   614			buf |= OMAP_I2C_BUF_TXFIF_CLR;
   615		}
   616	
   617		omap_i2c_write_reg(omap, OMAP_I2C_BUF_REG, buf);
   618	
   619		if (omap->rev < OMAP_I2C_REV_ON_3630)
   620			omap->b_hw = true; /* Enable hardware fixes */
   621	
   622		/* calculate wakeup latency constraint for MPU */
   623		if (omap->set_mpu_wkup_lat != NULL)
   624			omap->latency = (1000000 * omap->threshold) /
   625				(1000 * omap->speed / 8);
   626	}
   627	

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

                 reply	other threads:[~2026-09-07 22:43 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=202609080003.dbREhhYS-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=afd@ti.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.