From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [chrome-os:chromeos-5.4 10/50] drivers/misc/cardreader/rtsx_pcr.c:1108:13: error: 'rtsx_base_force_power_down' defined but not used
Date: Fri, 21 May 2021 08:05:09 +0800 [thread overview]
Message-ID: <202105210807.2ARrt18k-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3245 bytes --]
tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-5.4
head: 81dc15c630b5fc7ceda25a74b4a06400e0b73727
commit: 343835bda63b3072f3025a7b1870990c8a790d54 [10/50] UPSTREAM: misc: rtsx: Fix power down flow
config: powerpc64-randconfig-r021-20210521 (attached as .config)
compiler: powerpc64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git remote add chrome-os https://chromium.googlesource.com/chromiumos/third_party/kernel
git fetch --no-tags chrome-os chromeos-5.4
git checkout 343835bda63b3072f3025a7b1870990c8a790d54
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=powerpc64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/misc/cardreader/rtsx_pcr.c: In function 'rtsx_pci_init_hw':
drivers/misc/cardreader/rtsx_pcr.c:1370:2: error: implicit declaration of function 'rtsx_pci_write_config_byte'; did you mean 'pci_write_config_byte'? [-Werror=implicit-function-declaration]
1370 | rtsx_pci_write_config_byte(pcr, pcr->pcie_cap + PCI_EXP_LNKCTL + 1, 1);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
| pci_write_config_byte
drivers/misc/cardreader/rtsx_pcr.c:1370:37: error: 'struct rtsx_pcr' has no member named 'pcie_cap'
1370 | rtsx_pci_write_config_byte(pcr, pcr->pcie_cap + PCI_EXP_LNKCTL + 1, 1);
| ^~
drivers/misc/cardreader/rtsx_pcr.c:1372:24: error: 'pdev' undeclared (first use in this function); did you mean 'cdev'?
1372 | pci_write_config_byte(pdev, 0x70F, 0x5B);
| ^~~~
| cdev
drivers/misc/cardreader/rtsx_pcr.c:1372:24: note: each undeclared identifier is reported only once for each function it appears in
At top level:
>> drivers/misc/cardreader/rtsx_pcr.c:1108:13: error: 'rtsx_base_force_power_down' defined but not used [-Werror=unused-function]
1108 | static void rtsx_base_force_power_down(struct rtsx_pcr *pcr, u8 pm_state)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
vim +/rtsx_base_force_power_down +1108 drivers/misc/cardreader/rtsx_pcr.c
1107
> 1108 static void rtsx_base_force_power_down(struct rtsx_pcr *pcr, u8 pm_state)
1109 {
1110 /* Set relink_time to 0 */
1111 rtsx_pci_write_register(pcr, AUTOLOAD_CFG_BASE + 1, MASK_8_BIT_DEF, 0);
1112 rtsx_pci_write_register(pcr, AUTOLOAD_CFG_BASE + 2, MASK_8_BIT_DEF, 0);
1113 rtsx_pci_write_register(pcr, AUTOLOAD_CFG_BASE + 3,
1114 RELINK_TIME_MASK, 0);
1115
1116 rtsx_pci_write_register(pcr, pcr->reg_pm_ctrl3,
1117 D3_DELINK_MODE_EN, D3_DELINK_MODE_EN);
1118
1119 rtsx_pci_write_register(pcr, FPDCTL, ALL_POWER_DOWN, ALL_POWER_DOWN);
1120 }
1121
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 19713 bytes --]
reply other threads:[~2021-05-21 0:05 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=202105210807.2ARrt18k-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.