From: kernel test robot <lkp@intel.com>
To: Sherry Sun <sherry.sun@nxp.com>,
gregkh@linuxfoundation.org, jirislaby@kernel.org,
shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, shenwei.wang@nxp.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev
Subject: Re: [PATCH 2/2] tty: serial: imx: Add missing wakeup event reporting
Date: Wed, 24 Sep 2025 01:35:11 +0800 [thread overview]
Message-ID: <202509240146.aj950Liu-lkp@intel.com> (raw)
In-Reply-To: <20250923031613.2448073-3-sherry.sun@nxp.com>
Hi Sherry,
kernel test robot noticed the following build errors:
[auto build test ERROR on shawnguo/for-next]
[also build test ERROR on usb/usb-testing usb/usb-next usb/usb-linus linus/master v6.17-rc7 next-20250922]
[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/Sherry-Sun/tty-serial-imx-Only-configure-the-wake-register-when-device-is-set-as-wakeup-source/20250923-111951
base: https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git for-next
patch link: https://lore.kernel.org/r/20250923031613.2448073-3-sherry.sun%40nxp.com
patch subject: [PATCH 2/2] tty: serial: imx: Add missing wakeup event reporting
config: x86_64-buildonly-randconfig-004-20250923 (https://download.01.org/0day-ci/archive/20250924/202509240146.aj950Liu-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250924/202509240146.aj950Liu-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/202509240146.aj950Liu-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/tty/serial/imx.c:2742:21: error: call to undeclared function 'irqd_is_wakeup_set'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
2742 | if (wake_active && irqd_is_wakeup_set(irq_get_irq_data(sport->port.irq)))
| ^
>> drivers/tty/serial/imx.c:2742:40: error: call to undeclared function 'irq_get_irq_data'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
2742 | if (wake_active && irqd_is_wakeup_set(irq_get_irq_data(sport->port.irq)))
| ^
drivers/tty/serial/imx.c:2742:40: note: did you mean 'irq_set_irq_wake'?
include/linux/interrupt.h:481:12: note: 'irq_set_irq_wake' declared here
481 | extern int irq_set_irq_wake(unsigned int irq, unsigned int on);
| ^
2 errors generated.
vim +/irqd_is_wakeup_set +2742 drivers/tty/serial/imx.c
2696
2697 /* called with irq off */
2698 static void imx_uart_enable_wakeup(struct imx_port *sport, bool on)
2699 {
2700 struct tty_port *port = &sport->port.state->port;
2701 struct tty_struct *tty;
2702 struct device *tty_dev;
2703 u32 ucr3, usr1;
2704 bool may_wake, wake_active;
2705
2706 tty = tty_port_tty_get(port);
2707 if (tty) {
2708 tty_dev = tty->dev;
2709 may_wake = tty_dev && device_may_wakeup(tty_dev);
2710 tty_kref_put(tty);
2711 }
2712
2713 /* only configure the wake register when device set as wakeup source */
2714 if (!may_wake)
2715 return;
2716
2717 uart_port_lock_irq(&sport->port);
2718
2719 usr1 = imx_uart_readl(sport, USR1);
2720 ucr3 = imx_uart_readl(sport, UCR3);
2721 if (on) {
2722 imx_uart_writel(sport, USR1_AWAKE, USR1);
2723 ucr3 |= UCR3_AWAKEN;
2724 } else {
2725 ucr3 &= ~UCR3_AWAKEN;
2726 wake_active = usr1 & USR1_AWAKE;
2727 }
2728 imx_uart_writel(sport, ucr3, UCR3);
2729
2730 if (sport->have_rtscts) {
2731 u32 ucr1 = imx_uart_readl(sport, UCR1);
2732 if (on) {
2733 imx_uart_writel(sport, USR1_RTSD, USR1);
2734 ucr1 |= UCR1_RTSDEN;
2735 } else {
2736 ucr1 &= ~UCR1_RTSDEN;
2737 wake_active |= usr1 & USR1_RTSD;
2738 }
2739 imx_uart_writel(sport, ucr1, UCR1);
2740 }
2741
> 2742 if (wake_active && irqd_is_wakeup_set(irq_get_irq_data(sport->port.irq)))
2743 pm_wakeup_event(tty_port_tty_get(port)->dev, 0);
2744
2745 uart_port_unlock_irq(&sport->port);
2746 }
2747
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-09-23 17:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 3:16 [PATCH 0/2] tty: serial: imx: improve the imx uart wakeup function Sherry Sun
2025-09-23 3:16 ` [PATCH 1/2] tty: serial: imx: Only configure the wake register when device is set as wakeup source Sherry Sun
2025-09-23 8:32 ` Peng Fan
2025-09-23 7:36 ` Sherry Sun
2025-09-23 16:42 ` kernel test robot
2025-09-23 3:16 ` [PATCH 2/2] tty: serial: imx: Add missing wakeup event reporting Sherry Sun
2025-09-23 17:35 ` kernel test robot [this message]
2025-09-23 18:27 ` 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=202509240146.aj950Liu-lkp@intel.com \
--to=lkp@intel.com \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=jirislaby@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=shenwei.wang@nxp.com \
--cc=sherry.sun@nxp.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