From: kernel test robot <lkp@intel.com>
To: Naresh Solanki <naresh.solanki@9elements.com>,
Guenter Roeck <linux@roeck-us.net>,
Jean Delvare <jdelvare@suse.com>,
krzysztof.kozlowski+dt@linaro.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-hwmon@vger.kernel.org,
Patrick Rudolph <patrick.rudolph@9elements.com>,
Naresh Solanki <Naresh.Solanki@9elements.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] hwmon: (pmbus/tda38640) Add workaround for bug in SVID mode
Date: Wed, 26 Jul 2023 02:54:04 +0800 [thread overview]
Message-ID: <202307260241.BetLbnxd-lkp@intel.com> (raw)
In-Reply-To: <20230725114030.1860571-3-Naresh.Solanki@9elements.com>
Hi Naresh,
kernel test robot noticed the following build errors:
[auto build test ERROR on 55612007f16b5d7b1fb83a7b0f5bb686829db7c7]
url: https://github.com/intel-lab-lkp/linux/commits/Naresh-Solanki/hwmon-pmbus-Add-ON_OFF_CONFIG-register-bits/20230725-194318
base: 55612007f16b5d7b1fb83a7b0f5bb686829db7c7
patch link: https://lore.kernel.org/r/20230725114030.1860571-3-Naresh.Solanki%409elements.com
patch subject: [PATCH 3/3] hwmon: (pmbus/tda38640) Add workaround for bug in SVID mode
config: x86_64-randconfig-x014-20230725 (https://download.01.org/0day-ci/archive/20230726/202307260241.BetLbnxd-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce: (https://download.01.org/0day-ci/archive/20230726/202307260241.BetLbnxd-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/202307260241.BetLbnxd-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/hwmon/pmbus/tda38640.c:118:7: error: use of undeclared identifier 'CONFIG_SENSORS_TDA38640_REGULATOR'
if (!CONFIG_SENSORS_TDA38640_REGULATOR || !np ||
^
1 error generated.
vim +/CONFIG_SENSORS_TDA38640_REGULATOR +118 drivers/hwmon/pmbus/tda38640.c
106
107 static int tda38640_probe(struct i2c_client *client)
108 {
109 struct device *dev = &client->dev;
110 struct device_node *np = dev_of_node(dev);
111 struct tda38640_data *data;
112
113 data = devm_kzalloc(dev, sizeof(*data), GFP_KERNEL);
114 if (!data)
115 return -ENOMEM;
116 memcpy(&data->info, &tda38640_info, sizeof(tda38640_info));
117
> 118 if (!CONFIG_SENSORS_TDA38640_REGULATOR || !np ||
119 of_property_read_u32(np, "infineon,en-pin-fixed-level", &data->en_pin_lvl))
120 return pmbus_do_probe(client, &data->info);
121
122 /*
123 * Apply ON_OFF_CONFIG workaround as enabling the regulator using the
124 * OPERATION register doesn't work in SVID mode.
125 */
126 data->info.read_byte_data = tda38640_read_byte_data;
127 data->info.write_byte_data = tda38640_write_byte_data;
128 /*
129 * One should configure PMBUS_ON_OFF_CONFIG here, but
130 * PB_ON_OFF_CONFIG_POWERUP_CONTROL, PB_ON_OFF_CONFIG_EN_PIN_REQ and
131 * PB_ON_OFF_CONFIG_EN_PIN_REQ are ignored by the device.
132 * Only PB_ON_OFF_CONFIG_POLARITY_HIGH has an effect.
133 */
134
135 return pmbus_do_probe(client, &data->info);
136 }
137
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-07-25 18:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 11:40 [PATCH 1/3] dt-bindings: hwmon: Add Infineon TDA38640 Naresh Solanki
2023-07-25 11:40 ` [PATCH 2/3] hwmon: (pmbus) Add ON_OFF_CONFIG register bits Naresh Solanki
2023-07-25 11:40 ` [PATCH 3/3] hwmon: (pmbus/tda38640) Add workaround for bug in SVID mode Naresh Solanki
2023-07-25 14:21 ` Guenter Roeck
2023-07-26 12:22 ` Naresh Solanki
2023-07-26 14:19 ` Guenter Roeck
2023-07-27 8:30 ` Naresh Solanki
2023-07-25 16:19 ` kernel test robot
2023-07-25 18:54 ` kernel test robot [this message]
2023-07-25 12:28 ` [PATCH 1/3] dt-bindings: hwmon: Add Infineon TDA38640 Rob Herring
2023-07-25 13:10 ` Rob Herring
2023-07-25 14:17 ` Naresh Solanki
2023-07-25 14:28 ` Guenter Roeck
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=202307260241.BetLbnxd-lkp@intel.com \
--to=lkp@intel.com \
--cc=jdelvare@suse.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=llvm@lists.linux.dev \
--cc=naresh.solanki@9elements.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=patrick.rudolph@9elements.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 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.