public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jisheng Zhang <jszhang@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>
Cc: oe-kbuild-all@lists.linux.dev, linux-gpio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] gpio: fxl6408: Add optional reset gpio control
Date: Tue, 18 Nov 2025 17:50:11 +0800	[thread overview]
Message-ID: <202511181705.QWVZhvN1-lkp@intel.com> (raw)
In-Reply-To: <20251117001502.12618-2-jszhang@kernel.org>

Hi Jisheng,

kernel test robot noticed the following build errors:

[auto build test ERROR on brgl/gpio/for-next]
[also build test ERROR on linus/master v6.18-rc6 next-20251118]
[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/Jisheng-Zhang/gpio-fxl6408-Add-optional-reset-gpio-control/20251117-083516
base:   https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio/for-next
patch link:    https://lore.kernel.org/r/20251117001502.12618-2-jszhang%40kernel.org
patch subject: [PATCH v2 1/2] gpio: fxl6408: Add optional reset gpio control
config: riscv-randconfig-001-20251118 (https://download.01.org/0day-ci/archive/20251118/202511181705.QWVZhvN1-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 10.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251118/202511181705.QWVZhvN1-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/202511181705.QWVZhvN1-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/gpio/gpio-fxl6408.c: In function 'fxl6408_probe':
>> drivers/gpio/gpio-fxl6408.c:119:15: error: implicit declaration of function 'devm_gpiod_get_optional'; did you mean 'devm_regulator_get_optional'? [-Werror=implicit-function-declaration]
     119 |  reset_gpio = devm_gpiod_get_optional(dev, "reset", GPIOD_OUT_LOW);
         |               ^~~~~~~~~~~~~~~~~~~~~~~
         |               devm_regulator_get_optional
>> drivers/gpio/gpio-fxl6408.c:119:53: error: 'GPIOD_OUT_LOW' undeclared (first use in this function)
     119 |  reset_gpio = devm_gpiod_get_optional(dev, "reset", GPIOD_OUT_LOW);
         |                                                     ^~~~~~~~~~~~~
   drivers/gpio/gpio-fxl6408.c:119:53: note: each undeclared identifier is reported only once for each function it appears in
   cc1: some warnings being treated as errors


vim +119 drivers/gpio/gpio-fxl6408.c

   104	
   105	static int fxl6408_probe(struct i2c_client *client)
   106	{
   107		struct device *dev = &client->dev;
   108		struct gpio_desc *reset_gpio;
   109		int ret;
   110		struct gpio_regmap_config gpio_config = {
   111			.parent = dev,
   112			.ngpio = FXL6408_NGPIO,
   113			.reg_dat_base = GPIO_REGMAP_ADDR(FXL6408_REG_INPUT_STATUS),
   114			.reg_set_base = GPIO_REGMAP_ADDR(FXL6408_REG_OUTPUT),
   115			.reg_dir_out_base = GPIO_REGMAP_ADDR(FXL6408_REG_IO_DIR),
   116			.ngpio_per_reg = FXL6408_NGPIO,
   117		};
   118	
 > 119		reset_gpio = devm_gpiod_get_optional(dev, "reset", GPIOD_OUT_LOW);
   120		if (IS_ERR(reset_gpio))
   121			return dev_err_probe(dev, PTR_ERR(reset_gpio), "Failed to get reset gpio\n");
   122	
   123		gpio_config.regmap = devm_regmap_init_i2c(client, &regmap);
   124		if (IS_ERR(gpio_config.regmap))
   125			return dev_err_probe(dev, PTR_ERR(gpio_config.regmap),
   126					     "failed to allocate register map\n");
   127	
   128		ret = fxl6408_identify(dev, gpio_config.regmap);
   129		if (ret)
   130			return ret;
   131	
   132		/* Disable High-Z of outputs, so that our OUTPUT updates actually take effect. */
   133		ret = regmap_write(gpio_config.regmap, FXL6408_REG_OUTPUT_HIGH_Z, 0);
   134		if (ret)
   135			return dev_err_probe(dev, ret, "failed to write 'output high Z' register\n");
   136	
   137		return PTR_ERR_OR_ZERO(devm_gpio_regmap_register(dev, &gpio_config));
   138	}
   139	

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

  parent reply	other threads:[~2025-11-18  9:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17  0:15 [PATCH v2 0/2] gpio: fxl6408: add optional reset and suspend/resume Jisheng Zhang
2025-11-17  0:15 ` [PATCH v2 1/2] gpio: fxl6408: Add optional reset gpio control Jisheng Zhang
2025-11-17 10:01   ` Bartosz Golaszewski
2025-11-19 12:13     ` Jisheng Zhang
2025-11-18  9:50   ` kernel test robot [this message]
2025-11-17  0:15 ` [PATCH v2 2/2] gpio: fxl6408: Add suspend/resume support Jisheng Zhang

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=202511181705.QWVZhvN1-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=brgl@bgdev.pl \
    --cc=jszhang@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox