From: kernel test robot <lkp@intel.com>
To: Bjorn Andersson <andersson@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: drivers/tty/serial/qcom_geni_serial.c:921:13: warning: 'qcom_geni_serial_poll_rx_fifo_locked' defined but not used
Date: Sat, 05 Sep 2026 02:07:40 +0800 [thread overview]
Message-ID: <202609050203.u7Y5yPkc-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 986c24e0fe44f844b44d365b71ce831947f50298
commit: 8200871327d1bd4c08daf248a8693a3093982fa4 serial: qcom-geni: Keep FIFO RX active during console TX
date: 5 weeks ago
config: sh-randconfig-r133-20260904 (https://download.01.org/0day-ci/archive/20260905/202609050203.u7Y5yPkc-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 14.3.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260905/202609050203.u7Y5yPkc-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
| Fixes: 8200871327d1 ("serial: qcom-geni: Keep FIFO RX active during console TX")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202609050203.u7Y5yPkc-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/tty/serial/qcom_geni_serial.c:921:13: warning: 'qcom_geni_serial_poll_rx_fifo_locked' defined but not used [-Wunused-function]
921 | static void qcom_geni_serial_poll_rx_fifo_locked(struct uart_port *uport)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/qcom_geni_serial_poll_rx_fifo_locked +921 drivers/tty/serial/qcom_geni_serial.c
919
920 /* Caller holds the UART port lock. */
> 921 static void qcom_geni_serial_poll_rx_fifo_locked(struct uart_port *uport)
922 {
923 struct qcom_geni_serial_port *port = to_dev_port(uport);
924 struct tty_port *tport = &uport->state->port;
925 u32 s_irq_status;
926 bool drop_rx = false;
927
928 s_irq_status = readl(uport->membase + SE_GENI_S_IRQ_STATUS);
929 writel(s_irq_status, uport->membase + SE_GENI_S_IRQ_CLEAR);
930
931 if (s_irq_status & S_RX_FIFO_WR_ERR_EN) {
932 uport->icount.overrun++;
933 tty_insert_flip_char(tport, 0, TTY_OVERRUN);
934 }
935
936 if (s_irq_status & (S_GP_IRQ_0_EN | S_GP_IRQ_1_EN)) {
937 if (s_irq_status & S_GP_IRQ_0_EN)
938 uport->icount.parity++;
939 drop_rx = true;
940 } else if (s_irq_status & (S_GP_IRQ_2_EN | S_GP_IRQ_3_EN)) {
941 uport->icount.brk++;
942 port->brk = true;
943 }
944
945 qcom_geni_serial_handle_rx_fifo(uport, drop_rx);
946 }
947
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-04 18:07 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=202609050203.u7Y5yPkc-lkp@intel.com \
--to=lkp@intel.com \
--cc=andersson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®