From: kernel test robot <lkp@intel.com>
To: Alexey Charkov <alchark@gmail.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>
Cc: oe-kbuild-all@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-watchdog@vger.kernel.org,
Alexey Charkov <alchark@gmail.com>
Subject: Re: [PATCH v3 3/4] clocksource/drivers/timer-vt8500: Prepare for watchdog functionality
Date: Sun, 18 May 2025 09:23:37 +0800 [thread overview]
Message-ID: <202505180911.hDevFA1N-lkp@intel.com> (raw)
In-Reply-To: <20250515-vt8500-timer-updates-v3-3-2197a1b062bd@gmail.com>
Hi Alexey,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 92a09c47464d040866cf2b4cd052bc60555185fb]
url: https://github.com/intel-lab-lkp/linux/commits/Alexey-Charkov/dt-bindings-timer-via-vt8500-timer-Convert-to-YAML/20250516-025729
base: 92a09c47464d040866cf2b4cd052bc60555185fb
patch link: https://lore.kernel.org/r/20250515-vt8500-timer-updates-v3-3-2197a1b062bd%40gmail.com
patch subject: [PATCH v3 3/4] clocksource/drivers/timer-vt8500: Prepare for watchdog functionality
config: loongarch-randconfig-r123-20250517 (https://download.01.org/0day-ci/archive/20250518/202505180911.hDevFA1N-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 14.2.0
reproduce: (https://download.01.org/0day-ci/archive/20250518/202505180911.hDevFA1N-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/202505180911.hDevFA1N-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/clocksource/timer-vt8500.c:201:51: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void *platform_data @@ got void [noderef] __iomem *static [assigned] [toplevel] regbase @@
drivers/clocksource/timer-vt8500.c:201:51: sparse: expected void *platform_data
drivers/clocksource/timer-vt8500.c:201:51: sparse: got void [noderef] __iomem *static [assigned] [toplevel] regbase
vim +201 drivers/clocksource/timer-vt8500.c
175
176 /*
177 * This probe gets called after the timer is already up and running. This will create
178 * the watchdog device as a child since the registers are shared.
179 */
180 static int vt8500_timer_probe(struct platform_device *pdev)
181 {
182 struct platform_device *vt8500_watchdog_device;
183 struct device *dev = &pdev->dev;
184 int ret;
185
186 if (!sys_timer_ch) {
187 dev_info(dev, "Not enabling watchdog: only one irq was given");
188 return 0;
189 }
190
191 if (!regbase)
192 return dev_err_probe(dev, -ENOMEM,
193 "Timer not initialized, cannot create watchdog");
194
195 vt8500_watchdog_device = platform_device_alloc("vt8500-wdt", -1);
196 if (!vt8500_watchdog_device)
197 return dev_err_probe(dev, -ENOMEM,
198 "Failed to allocate vt8500-wdt");
199
200 /* Pass the base address as platform data and nothing else */
> 201 vt8500_watchdog_device->dev.platform_data = regbase;
202 vt8500_watchdog_device->dev.parent = dev;
203
204 ret = platform_device_add(vt8500_watchdog_device);
205 if (ret)
206 platform_device_put(vt8500_watchdog_device);
207
208 return ret;
209 }
210
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-05-18 1:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 18:55 [PATCH v3 0/4] clocksource/drivers/timer-vt8500: clean up and add watchdog function Alexey Charkov
2025-05-15 18:55 ` [PATCH v3 1/4] dt-bindings: timer: via,vt8500-timer: Convert to YAML Alexey Charkov
2025-05-15 18:55 ` [PATCH v3 2/4] clocksource/drivers/timer-vt8500: Add defines for magic constants Alexey Charkov
2025-05-15 18:55 ` [PATCH v3 3/4] clocksource/drivers/timer-vt8500: Prepare for watchdog functionality Alexey Charkov
2025-05-18 1:23 ` kernel test robot [this message]
2025-05-19 11:34 ` Alexey Charkov
2025-05-19 13:34 ` Guenter Roeck
2025-05-20 17:39 ` Alexey Charkov
2025-05-15 18:55 ` [PATCH v3 4/4] watchdog: Add support for VIA/WonderMedia SoC " Alexey Charkov
2025-05-16 6:55 ` kernel test robot
2025-05-16 13:02 ` Alexey Charkov
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=202505180911.hDevFA1N-lkp@intel.com \
--to=lkp@intel.com \
--cc=alchark@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
--cc=wim@linux-watchdog.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.