From: kernel test robot <lkp@intel.com>
To: Joel Stanley <joel@jms.id.au>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [shenki:spb1-hacking 8176/9113] drivers/hwmon/pmbus/tda38640.c:117:14: error: 'CONFIG_SENSORS_TDA38640_REGULATOR' undeclared; did you mean 'CONFIG_SENSORS_LM25066_REGULATOR'?
Date: Tue, 29 Aug 2023 14:35:59 +0800 [thread overview]
Message-ID: <202308291406.wh0Eeucr-lkp@intel.com> (raw)
tree: https://github.com/shenki/linux spb1-hacking
head: b3de99e1aeeeae3e96ffc4c34afae3d2ef4c8175
commit: b2d16420d16568d3ae60f56b32ba0fe8df813f40 [8176/9113] hwmon: (pmbus/tda38640) Add workaround for bug in SVID mode
config: x86_64-randconfig-002-20230829 (https://download.01.org/0day-ci/archive/20230829/202308291406.wh0Eeucr-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230829/202308291406.wh0Eeucr-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/202308291406.wh0Eeucr-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/hwmon/pmbus/tda38640.c: In function 'tda38640_probe':
>> drivers/hwmon/pmbus/tda38640.c:117:14: error: 'CONFIG_SENSORS_TDA38640_REGULATOR' undeclared (first use in this function); did you mean 'CONFIG_SENSORS_LM25066_REGULATOR'?
117 | if (!CONFIG_SENSORS_TDA38640_REGULATOR || !np ||
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| CONFIG_SENSORS_LM25066_REGULATOR
drivers/hwmon/pmbus/tda38640.c:117:14: note: each undeclared identifier is reported only once for each function it appears in
vim +117 drivers/hwmon/pmbus/tda38640.c
105
106 static int tda38640_probe(struct i2c_client *client)
107 {
108 struct device *dev = &client->dev;
109 struct device_node *np = dev_of_node(dev);
110 struct tda38640_data *data;
111
112 data = devm_kzalloc(dev, sizeof(*data), GFP_KERNEL);
113 if (!data)
114 return -ENOMEM;
115 memcpy(&data->info, &tda38640_info, sizeof(tda38640_info));
116
> 117 if (!CONFIG_SENSORS_TDA38640_REGULATOR || !np ||
118 of_property_read_u32(np, "infineon,en-pin-fixed-level", &data->en_pin_lvl))
119 return pmbus_do_probe(client, &data->info);
120
121 /*
122 * Apply ON_OFF_CONFIG workaround as enabling the regulator using the
123 * OPERATION register doesn't work in SVID mode.
124 */
125 data->info.read_byte_data = tda38640_read_byte_data;
126 data->info.write_byte_data = tda38640_write_byte_data;
127 /*
128 * One should configure PMBUS_ON_OFF_CONFIG here, but
129 * PB_ON_OFF_CONFIG_POWERUP_CONTROL, PB_ON_OFF_CONFIG_EN_PIN_REQ and
130 * PB_ON_OFF_CONFIG_EN_PIN_REQ are ignored by the device.
131 * Only PB_ON_OFF_CONFIG_POLARITY_HIGH has an effect.
132 */
133
134 return pmbus_do_probe(client, &data->info);
135 }
136
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-08-29 6:36 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=202308291406.wh0Eeucr-lkp@intel.com \
--to=lkp@intel.com \
--cc=joel@jms.id.au \
--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.