From: kernel test robot <lkp@intel.com>
To: Shenwei Wang <shenwei.wang@nxp.com>,
Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Shenwei Wang <shenwei.wang@nxp.com>, Peng Fan <peng.fan@nxp.com>,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-imx@nxp.com
Subject: Re: [PATCH 3/4] gpio: imx-rpmsg: add imx-rpmsg GPIO driver
Date: Thu, 21 Aug 2025 22:11:18 +0800 [thread overview]
Message-ID: <202508212119.gamkDcXG-lkp@intel.com> (raw)
In-Reply-To: <20250818204420.794554-4-shenwei.wang@nxp.com>
Hi Shenwei,
kernel test robot noticed the following build warnings:
[auto build test WARNING on remoteproc/rproc-next]
[also build test WARNING on brgl/gpio/for-next shawnguo/for-next linus/master v6.17-rc2 next-20250820]
[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/Shenwei-Wang/dt-bindings-remoteproc-imx_rproc-Add-rpmsg-subnode-support/20250819-044803
base: https://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git rproc-next
patch link: https://lore.kernel.org/r/20250818204420.794554-4-shenwei.wang%40nxp.com
patch subject: [PATCH 3/4] gpio: imx-rpmsg: add imx-rpmsg GPIO driver
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20250821/202508212119.gamkDcXG-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250821/202508212119.gamkDcXG-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/202508212119.gamkDcXG-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpio/gpio-imx-rpmsg.c:419:6: warning: variable 'port' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]
419 | if (msg)
| ^~~
drivers/gpio/gpio-imx-rpmsg.c:421:7: note: uninitialized use occurs here
421 | if (!port)
| ^~~~
drivers/gpio/gpio-imx-rpmsg.c:419:2: note: remove the 'if' if its condition is always true
419 | if (msg)
| ^~~~~~~~
420 | port = drvdata->channel_devices[msg->port_idx];
drivers/gpio/gpio-imx-rpmsg.c:415:34: note: initialize the variable 'port' to silence this warning
415 | struct imx_rpmsg_gpio_port *port;
| ^
| = NULL
drivers/gpio/gpio-imx-rpmsg.c:503:10: error: incompatible function pointer types assigning to 'void (*)(struct gpio_chip *, unsigned int, int)' from 'int (struct gpio_chip *, unsigned int, int)' [-Wincompatible-function-pointer-types]
503 | gc->set = imx_rpmsg_gpio_set;
| ^ ~~~~~~~~~~~~~~~~~~
1 warning and 1 error generated.
vim +419 drivers/gpio/gpio-imx-rpmsg.c
409
410 static int imx_rpmsg_gpio_callback(struct rpmsg_device *rpdev,
411 void *data, int len, void *priv, u32 src)
412 {
413 struct gpio_rpmsg_data *msg = (struct gpio_rpmsg_data *)data;
414 unsigned long flags;
415 struct imx_rpmsg_gpio_port *port;
416 struct imx_rpmsg_driver_data *drvdata;
417
418 drvdata = dev_get_drvdata(&rpdev->dev);
> 419 if (msg)
420 port = drvdata->channel_devices[msg->port_idx];
421 if (!port)
422 return -ENODEV;
423
424 if (msg->header.type == GPIO_RPMSG_REPLY) {
425 port->info.reply_msg = msg;
426 complete(&port->info.cmd_complete);
427 } else if (msg->header.type == GPIO_RPMSG_NOTIFY) {
428 port->info.notify_msg = msg;
429 local_irq_save(flags);
430 generic_handle_domain_irq(port->domain, msg->pin_idx);
431 local_irq_restore(flags);
432 } else
433 dev_err(&rpdev->dev, "wrong command type!\n");
434
435 return 0;
436 }
437
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-08-21 14:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 20:44 [PATCH 0/4] Enable Remote GPIO over RPMSG on i.MX Platform Shenwei Wang
2025-08-18 20:44 ` [PATCH 1/4] dt-bindings: remoteproc: imx_rproc: Add "rpmsg" subnode support Shenwei Wang
2025-08-26 14:50 ` Frank Li
2025-08-26 20:09 ` Rob Herring
2025-08-27 14:49 ` Shenwei Wang
2025-08-29 15:06 ` Rob Herring
2025-08-30 17:44 ` Shenwei Wang
2025-08-18 20:44 ` [PATCH 2/4] remoteproc: imx_rproc: Populate devices under "rpmsg" subnode Shenwei Wang
2025-08-21 11:02 ` Peng Fan
2025-08-21 18:51 ` Shenwei Wang
2025-08-18 20:44 ` [PATCH 3/4] gpio: imx-rpmsg: add imx-rpmsg GPIO driver Shenwei Wang
2025-08-21 9:01 ` Linus Walleij
2025-09-01 7:26 ` Arnaud POULIQUEN
2025-09-01 17:22 ` Shenwei Wang
2025-09-02 12:34 ` Arnaud POULIQUEN
2025-08-21 14:11 ` kernel test robot [this message]
2025-08-18 20:44 ` [PATCH 4/4] arm64: dts: imx8ulp: Add rpmsg node under imx_rproc Shenwei Wang
2025-08-20 20:49 ` [PATCH 0/4] Enable Remote GPIO over RPMSG on i.MX Platform Mathieu Poirier
2025-08-20 22:29 ` Shenwei Wang
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=202508212119.gamkDcXG-lkp@intel.com \
--to=lkp@intel.com \
--cc=andersson@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mathieu.poirier@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=shenwei.wang@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
all inboxes | Powered by JetHome®