From: kernel test robot <lkp@intel.com>
To: Carl Lee via B4 Relay <devnull+carl.lee.amd.com@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
krzk@kernel.org, carl.lee@amd.com, peter.shen@amd.com,
colin.huang2@amd.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] nfc: nxp-nci: i2c: restore IRQ trigger fallback
Date: Thu, 12 Mar 2026 07:46:48 +0800 [thread overview]
Message-ID: <202603120758.LA4Bjngo-lkp@intel.com> (raw)
In-Reply-To: <20260311-nfc-nxp-nci-i2c-restore-irq-trigger-fallback-v1-1-9e20714411d7@amd.com>
Hi Carl,
kernel test robot noticed the following build errors:
[auto build test ERROR on 7109a2155340cc7b21f27e832ece6df03592f2e8]
url: https://github.com/intel-lab-lkp/linux/commits/Carl-Lee-via-B4-Relay/nfc-nxp-nci-i2c-restore-IRQ-trigger-fallback/20260311-174025
base: 7109a2155340cc7b21f27e832ece6df03592f2e8
patch link: https://lore.kernel.org/r/20260311-nfc-nxp-nci-i2c-restore-irq-trigger-fallback-v1-1-9e20714411d7%40amd.com
patch subject: [PATCH] nfc: nxp-nci: i2c: restore IRQ trigger fallback
config: i386-buildonly-randconfig-001-20260312 (https://download.01.org/0day-ci/archive/20260312/202603120758.LA4Bjngo-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.4.0-5) 12.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260312/202603120758.LA4Bjngo-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/202603120758.LA4Bjngo-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/nfc/nxp-nci/i2c.c: In function 'nxp_nci_i2c_probe':
>> drivers/nfc/nxp-nci/i2c.c:311:20: error: implicit declaration of function 'irq_get_trigger_type' [-Werror=implicit-function-declaration]
311 | irqflags = irq_get_trigger_type(client->irq);
| ^~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/irq_get_trigger_type +311 drivers/nfc/nxp-nci/i2c.c
265
266 static int nxp_nci_i2c_probe(struct i2c_client *client)
267 {
268 struct device *dev = &client->dev;
269 struct nxp_nci_i2c_phy *phy;
270 int r;
271 unsigned long irqflags;
272
273 if (!i2c_check_functionality(client->adapter, I2C_FUNC_I2C)) {
274 nfc_err(&client->dev, "Need I2C_FUNC_I2C\n");
275 return -ENODEV;
276 }
277
278 phy = devm_kzalloc(&client->dev, sizeof(struct nxp_nci_i2c_phy),
279 GFP_KERNEL);
280 if (!phy)
281 return -ENOMEM;
282
283 phy->i2c_dev = client;
284 i2c_set_clientdata(client, phy);
285
286 r = devm_acpi_dev_add_driver_gpios(dev, acpi_nxp_nci_gpios);
287 if (r)
288 dev_dbg(dev, "Unable to add GPIO mapping table\n");
289
290 phy->gpiod_en = devm_gpiod_get(dev, "enable", GPIOD_OUT_LOW);
291 if (IS_ERR(phy->gpiod_en)) {
292 nfc_err(dev, "Failed to get EN gpio\n");
293 return PTR_ERR(phy->gpiod_en);
294 }
295
296 phy->gpiod_fw = devm_gpiod_get_optional(dev, "firmware", GPIOD_OUT_LOW);
297 if (IS_ERR(phy->gpiod_fw)) {
298 nfc_err(dev, "Failed to get FW gpio\n");
299 return PTR_ERR(phy->gpiod_fw);
300 }
301
302 r = nxp_nci_probe(phy, &client->dev, &i2c_phy_ops,
303 NXP_NCI_I2C_MAX_PAYLOAD, &phy->ndev);
304 if (r < 0)
305 return r;
306
307 /* Prefer the trigger type configured by firmware.
308 * Some platforms do not provide it, so fall back to the
309 * historically used rising-edge trigger.
310 */
> 311 irqflags = irq_get_trigger_type(client->irq);
312 if (!irqflags)
313 irqflags = IRQF_TRIGGER_RISING;
314
315 r = request_threaded_irq(client->irq, NULL,
316 nxp_nci_i2c_irq_thread_fn,
317 irqflags | IRQF_ONESHOT,
318 NXP_NCI_I2C_DRIVER_NAME, phy);
319 if (r < 0)
320 nfc_err(&client->dev, "Unable to register IRQ handler\n");
321
322 return r;
323 }
324
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-03-11 23:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 9:26 [PATCH] nfc: nxp-nci: i2c: restore IRQ trigger fallback Carl Lee via B4 Relay
2026-03-11 11:08 ` Luca Stefani
2026-03-11 23:46 ` kernel test robot [this message]
2026-03-12 2:43 ` kernel test robot
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=202603120758.LA4Bjngo-lkp@intel.com \
--to=lkp@intel.com \
--cc=carl.lee@amd.com \
--cc=colin.huang2@amd.com \
--cc=devnull+carl.lee.amd.com@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peter.shen@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox