From: kbuild test robot <lkp@intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: drivers/acpi/pmic/intel_pmic_xpower.c:183: undefined reference to `iosf_mbi_block_punit_i2c_access'
Date: Sat, 3 Nov 2018 01:28:44 +0800 [thread overview]
Message-ID: <201811030142.IIRPWNE6%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1903 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: d81f50bd34646d8373b989e55180c0fc9af94e0b
commit: 3c670dba864d9ab0a23612a93b7d98700734bd44 ACPI / PMIC: xpower: Block P-Unit I2C access during read-modify-write
date: 8 days ago
config: x86_64-randconfig-s3-11022323 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
git checkout 3c670dba864d9ab0a23612a93b7d98700734bd44
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/acpi/pmic/intel_pmic_xpower.o: In function `intel_xpower_pmic_update_power':
>> drivers/acpi/pmic/intel_pmic_xpower.c:183: undefined reference to `iosf_mbi_block_punit_i2c_access'
>> drivers/acpi/pmic/intel_pmic_xpower.c:200: undefined reference to `iosf_mbi_unblock_punit_i2c_access'
vim +183 drivers/acpi/pmic/intel_pmic_xpower.c
172
173 static int intel_xpower_pmic_update_power(struct regmap *regmap, int reg,
174 int bit, bool on)
175 {
176 int data, ret;
177
178 /* GPIO1 LDO regulator needs special handling */
179 if (reg == XPOWER_GPI1_CTRL)
180 return regmap_update_bits(regmap, reg, GPI1_LDO_MASK,
181 on ? GPI1_LDO_ON : GPI1_LDO_OFF);
182
> 183 ret = iosf_mbi_block_punit_i2c_access();
184 if (ret)
185 return ret;
186
187 if (regmap_read(regmap, reg, &data)) {
188 ret = -EIO;
189 goto out;
190 }
191
192 if (on)
193 data |= BIT(bit);
194 else
195 data &= ~BIT(bit);
196
197 if (regmap_write(regmap, reg, data))
198 ret = -EIO;
199 out:
> 200 iosf_mbi_unblock_punit_i2c_access();
201
202 return ret;
203 }
204
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 30237 bytes --]
next reply other threads:[~2018-11-02 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 17:28 kbuild test robot [this message]
2018-11-09 1:57 ` drivers/acpi/pmic/intel_pmic_xpower.c:183: undefined reference to `iosf_mbi_block_punit_i2c_access' Randy Dunlap
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=201811030142.IIRPWNE6%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=hdegoede@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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).