linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Vaibhav Gupta <vaibhavgupta40@gmail.com>, Michael Buesch <m@bues.ch>
Cc: oe-kbuild-all@lists.linux.dev,
	Vaibhav Gupta <vaibhavgupta40@gmail.com>,
	Bjorn Helgaas <helgaas@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] driver: gpio-bt8xx: use generic PCI PM
Date: Sat, 11 Oct 2025 09:43:54 +0800	[thread overview]
Message-ID: <202510110924.dUQeeRV6-lkp@intel.com> (raw)
In-Reply-To: <20251010105338.664564-1-vaibhavgupta40@gmail.com>

Hi Vaibhav,

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.17 next-20251010]
[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/Vaibhav-Gupta/driver-gpio-bt8xx-use-generic-PCI-PM/20251010-185625
base:   https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio/for-next
patch link:    https://lore.kernel.org/r/20251010105338.664564-1-vaibhavgupta40%40gmail.com
patch subject: [PATCH v1] driver: gpio-bt8xx: use generic PCI PM
config: loongarch-randconfig-002-20251011 (https://download.01.org/0day-ci/archive/20251011/202510110924.dUQeeRV6-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 12.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251011/202510110924.dUQeeRV6-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/202510110924.dUQeeRV6-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/gpio/gpio-bt8xx.c: In function 'bt8xxgpio_suspend':
>> drivers/gpio/gpio-bt8xx.c:233:19: error: 'struct bt8xxgpio' has no member named 'saved_outen'
     233 |                 bg->saved_outen = bgread(BT848_GPIO_OUT_EN);
         |                   ^~
>> drivers/gpio/gpio-bt8xx.c:234:19: error: 'struct bt8xxgpio' has no member named 'saved_data'
     234 |                 bg->saved_data = bgread(BT848_GPIO_DATA);
         |                   ^~
   drivers/gpio/gpio-bt8xx.c: In function 'bt8xxgpio_resume':
   drivers/gpio/gpio-bt8xx.c:254:19: error: 'struct bt8xxgpio' has no member named 'saved_outen'
     254 |         bgwrite(bg->saved_outen, BT848_GPIO_OUT_EN);
         |                   ^~
   drivers/gpio/gpio-bt8xx.c:61:41: note: in definition of macro 'bgwrite'
      61 | #define bgwrite(dat, adr)       writel((dat), bg->mmio+(adr))
         |                                         ^~~
   drivers/gpio/gpio-bt8xx.c:255:19: error: 'struct bt8xxgpio' has no member named 'saved_data'
     255 |         bgwrite(bg->saved_data & bg->saved_outen,
         |                   ^~
   drivers/gpio/gpio-bt8xx.c:61:41: note: in definition of macro 'bgwrite'
      61 | #define bgwrite(dat, adr)       writel((dat), bg->mmio+(adr))
         |                                         ^~~
   drivers/gpio/gpio-bt8xx.c:255:36: error: 'struct bt8xxgpio' has no member named 'saved_outen'
     255 |         bgwrite(bg->saved_data & bg->saved_outen,
         |                                    ^~
   drivers/gpio/gpio-bt8xx.c:61:41: note: in definition of macro 'bgwrite'
      61 | #define bgwrite(dat, adr)       writel((dat), bg->mmio+(adr))
         |                                         ^~~


vim +233 drivers/gpio/gpio-bt8xx.c

ff1d5c2f0268f4 drivers/gpio/bt8xxgpio.c  Michael Buesch      2008-07-25  226  
2213c7a2cb81b2 drivers/gpio/gpio-bt8xx.c Vaibhav Gupta       2025-10-10  227  static int __maybe_unused bt8xxgpio_suspend(struct device *dev)
ff1d5c2f0268f4 drivers/gpio/bt8xxgpio.c  Michael Buesch      2008-07-25  228  {
2213c7a2cb81b2 drivers/gpio/gpio-bt8xx.c Vaibhav Gupta       2025-10-10  229  	struct pci_dev *pdev = to_pci_dev(dev);
ff1d5c2f0268f4 drivers/gpio/bt8xxgpio.c  Michael Buesch      2008-07-25  230  	struct bt8xxgpio *bg = pci_get_drvdata(pdev);
ff1d5c2f0268f4 drivers/gpio/bt8xxgpio.c  Michael Buesch      2008-07-25  231  
b9a557d05a7dde drivers/gpio/gpio-bt8xx.c Bartosz Golaszewski 2025-03-10  232  	scoped_guard(spinlock_irqsave, &bg->lock) {
ff1d5c2f0268f4 drivers/gpio/bt8xxgpio.c  Michael Buesch      2008-07-25 @233  		bg->saved_outen = bgread(BT848_GPIO_OUT_EN);
ff1d5c2f0268f4 drivers/gpio/bt8xxgpio.c  Michael Buesch      2008-07-25 @234  		bg->saved_data = bgread(BT848_GPIO_DATA);
ff1d5c2f0268f4 drivers/gpio/bt8xxgpio.c  Michael Buesch      2008-07-25  235  
ff1d5c2f0268f4 drivers/gpio/bt8xxgpio.c  Michael Buesch      2008-07-25  236  		bgwrite(0, BT848_INT_MASK);
ff1d5c2f0268f4 drivers/gpio/bt8xxgpio.c  Michael Buesch      2008-07-25  237  		bgwrite(~0x0, BT848_INT_STAT);
ff1d5c2f0268f4 drivers/gpio/bt8xxgpio.c  Michael Buesch      2008-07-25  238  		bgwrite(0x0, BT848_GPIO_OUT_EN);
b9a557d05a7dde drivers/gpio/gpio-bt8xx.c Bartosz Golaszewski 2025-03-10  239  	}
ff1d5c2f0268f4 drivers/gpio/bt8xxgpio.c  Michael Buesch      2008-07-25  240  
ff1d5c2f0268f4 drivers/gpio/bt8xxgpio.c  Michael Buesch      2008-07-25  241  	return 0;
ff1d5c2f0268f4 drivers/gpio/bt8xxgpio.c  Michael Buesch      2008-07-25  242  }
ff1d5c2f0268f4 drivers/gpio/bt8xxgpio.c  Michael Buesch      2008-07-25  243  

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

  reply	other threads:[~2025-10-11  1:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-10 10:53 [PATCH v1] driver: gpio-bt8xx: use generic PCI PM Vaibhav Gupta
2025-10-11  1:43 ` kernel test robot [this message]
2025-10-11 10:26   ` Michael Büsch
2025-10-11 11:32     ` Vaibhav Gupta
2025-10-11 12:31       ` Michael Büsch
2025-10-11 12:37         ` Vaibhav Gupta
2025-10-11 12:57         ` [PATCH v3] " Vaibhav Gupta
2025-10-13 11:04           ` [PATCH v4] driver: gpio: bt8xx: " Vaibhav Gupta
2025-10-11 12:32       ` [PATCH v2] driver: gpio-bt8xx: " Vaibhav Gupta
2025-10-13  9:41       ` [PATCH v1] " Bartosz Golaszewski
2025-10-13 11:03         ` Vaibhav Gupta
2025-10-13 15:36           ` Bartosz Golaszewski
2025-10-13 15:51             ` Vaibhav Gupta
2025-10-13 15:52               ` [PATCH v5] gpio: bt8xx: " Vaibhav Gupta
2025-10-13 17:43                 ` Bjorn Helgaas
2025-10-16 16:36                   ` [PATCH v6] gpio: bt8xx: use generic power management Vaibhav Gupta
2025-10-21  8:48                     ` Bartosz Golaszewski
2025-10-22 19:29                       ` Bjorn Helgaas
2025-10-23  7:49                         ` Vaibhav Gupta
2025-10-23  7:55                           ` Bartosz Golaszewski
2025-10-23  7:58                             ` Vaibhav Gupta
2025-10-23  7:59                     ` Bartosz Golaszewski
2025-10-16 16:37                   ` [PATCH v5] gpio: bt8xx: use generic PCI PM Vaibhav Gupta

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=202510110924.dUQeeRV6-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=brgl@bgdev.pl \
    --cc=helgaas@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m@bues.ch \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=vaibhavgupta40@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).