From: kernel test robot <lkp@intel.com>
To: Lukas Timmermann <linux@timmermann.space>,
lee@kernel.org, pavel@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@timmermann.space
Subject: Re: [PATCH v4 2/2] leds: as3668: Driver for the ams Osram 4-channel i2c LED driver
Date: Sun, 8 Jun 2025 17:47:24 +0800 [thread overview]
Message-ID: <202506081754.yXYFC7WL-lkp@intel.com> (raw)
In-Reply-To: <20250607215049.29259-3-linux@timmermann.space>
Hi Lukas,
kernel test robot noticed the following build errors:
[auto build test ERROR on lee-leds/for-leds-next]
[also build test ERROR on linus/master v6.15 next-20250606]
[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/Lukas-Timmermann/dt-bindings-leds-Add-new-as3668-support/20250608-055330
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git for-leds-next
patch link: https://lore.kernel.org/r/20250607215049.29259-3-linux%40timmermann.space
patch subject: [PATCH v4 2/2] leds: as3668: Driver for the ams Osram 4-channel i2c LED driver
config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20250608/202506081754.yXYFC7WL-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250608/202506081754.yXYFC7WL-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/202506081754.yXYFC7WL-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/leds/leds-as3668.c:137:16: error: call to undeclared function 'FIELD_GET'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
137 | chip_serial = FIELD_GET(AS3668_CHIP_ID2_SERIAL_MASK, chip_id2);
| ^
1 error generated.
vim +/FIELD_GET +137 drivers/leds/leds-as3668.c
117
118 static int as3668_probe(struct i2c_client *client)
119 {
120 u8 chip_id1, chip_id2, chip_serial, chip_rev;
121 struct as3668 *as3668;
122
123 /* Check for sensible i2c address */
124 if (client->addr != 0x42)
125 return dev_err_probe(&client->dev, -EFAULT,
126 "unexpected address for as3668 device\n");
127
128 /* Read identifier from chip */
129 chip_id1 = as3668_read_value(client, AS3668_CHIP_ID1);
130
131 if (chip_id1 != AS3668_CHIP_IDENT)
132 return dev_err_probe(&client->dev, -ENODEV,
133 "chip reported wrong id: 0x%tx\n", chip_id1);
134
135 /* Check the revision*/
136 chip_id2 = as3668_read_value(client, AS3668_CHIP_ID2);
> 137 chip_serial = FIELD_GET(AS3668_CHIP_ID2_SERIAL_MASK, chip_id2);
138 chip_rev = FIELD_GET(AS3668_CHIP_ID2_REV_MASK, chip_id2);
139
140 if (chip_rev != AS3668_CHIP_REV1)
141 dev_warn(&client->dev, "unexpected chip revision\n");
142
143 /* Print out information about the chip */
144 dev_dbg(&client->dev,
145 "chip_id: 0x%tx | chip_id2: 0x%tx | chip_serial: 0x%tx | chip_rev: 0x%tx\n",
146 chip_id1, chip_id2, chip_serial, chip_rev);
147
148 as3668 = devm_kzalloc(&client->dev, struct_size(as3668, leds, AS3668_MAX_LEDS), GFP_KERNEL);
149 as3668->client = client;
150
151 as3668_dt_init(as3668);
152
153 /* Initialize the chip */
154 as3668_write_value(client, AS3668_CURRX_CONTROL, 0x55);
155 as3668_write_value(client, AS3668_CURR1, 0x00);
156 as3668_write_value(client, AS3668_CURR2, 0x00);
157 as3668_write_value(client, AS3668_CURR3, 0x00);
158 as3668_write_value(client, AS3668_CURR4, 0x00);
159
160 return 0;
161 }
162
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-06-08 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-07 21:50 [PATCH v4 0/2] Support for Osram as3668 LED driver Lukas Timmermann
2025-06-07 21:50 ` [PATCH v4 1/2] dt-bindings: leds: Add new as3668 support Lukas Timmermann
2025-06-08 14:41 ` Krzysztof Kozlowski
2025-06-07 21:50 ` [PATCH v4 2/2] leds: as3668: Driver for the ams Osram 4-channel i2c LED driver Lukas Timmermann
2025-06-08 8:24 ` kernel test robot
2025-06-08 9:47 ` kernel test robot [this message]
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=202506081754.yXYFC7WL-lkp@intel.com \
--to=lkp@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux@timmermann.space \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pavel@kernel.org \
--cc=robh@kernel.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.