From: kernel test robot <lkp@intel.com>
To: Fabrice Gasnier <fabrice.gasnier@foss.st.com>,
lee@kernel.org, alexandre.torgue@foss.st.com,
daniel.lezcano@linaro.org, tglx@linutronix.de
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
ukleinek@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
jic23@kernel.org, robh@kernel.org, catalin.marinas@arm.com,
will@kernel.org, devicetree@vger.kernel.org, wbg@kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
linux-pwm@vger.kernel.org, olivier.moysan@foss.st.com,
fabrice.gasnier@foss.st.com
Subject: Re: [PATCH v5 3/7] clocksource: stm32-lptimer: add support for stm32mp25
Date: Sat, 26 Apr 2025 15:01:29 +0800 [thread overview]
Message-ID: <202504261456.aCATBoYN-lkp@intel.com> (raw)
In-Reply-To: <20250425124755.166193-4-fabrice.gasnier@foss.st.com>
Hi Fabrice,
kernel test robot noticed the following build warnings:
[auto build test WARNING on lee-mfd/for-mfd-next]
[also build test WARNING on lee-leds/for-leds-next linus/master v6.15-rc3 next-20250424]
[cannot apply to atorgue-stm32/stm32-next lee-mfd/for-mfd-fixes]
[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/Fabrice-Gasnier/dt-bindings-mfd-stm32-lptimer-add-support-for-stm32mp25/20250425-210409
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
patch link: https://lore.kernel.org/r/20250425124755.166193-4-fabrice.gasnier%40foss.st.com
patch subject: [PATCH v5 3/7] clocksource: stm32-lptimer: add support for stm32mp25
config: arm-randconfig-003-20250426 (https://download.01.org/0day-ci/archive/20250426/202504261456.aCATBoYN-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project f819f46284f2a79790038e1f6649172789734ae8)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250426/202504261456.aCATBoYN-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/202504261456.aCATBoYN-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/clocksource/timer-stm32-lp.c:57:6: warning: logical not is only applied to the left hand side of this bitwise operator [-Wlogical-not-parentheses]
57 | if (!val & STM32_LPTIM_ENABLE) {
| ^ ~
drivers/clocksource/timer-stm32-lp.c:57:6: note: add parentheses after the '!' to evaluate the bitwise operator first
57 | if (!val & STM32_LPTIM_ENABLE) {
| ^
| ( )
drivers/clocksource/timer-stm32-lp.c:57:6: note: add parentheses around left hand side expression to silence this warning
57 | if (!val & STM32_LPTIM_ENABLE) {
| ^
| ( )
1 warning generated.
vim +57 drivers/clocksource/timer-stm32-lp.c
50
51 static int stm32mp25_clkevent_lp_set_evt(struct stm32_lp_private *priv, unsigned long evt)
52 {
53 int ret;
54 u32 val;
55
56 regmap_read(priv->reg, STM32_LPTIM_CR, &val);
> 57 if (!val & STM32_LPTIM_ENABLE) {
58 /* Enable LPTIMER to be able to write into IER and ARR registers */
59 regmap_write(priv->reg, STM32_LPTIM_CR, STM32_LPTIM_ENABLE);
60 /*
61 * After setting the ENABLE bit, a delay of two counter clock cycles is needed
62 * before the LPTIM is actually enabled. For 32KHz rate, this makes approximately
63 * 62.5 micro-seconds, round it up.
64 */
65 udelay(63);
66 }
67 /* set next event counter */
68 regmap_write(priv->reg, STM32_LPTIM_ARR, evt);
69 /* enable ARR interrupt */
70 regmap_write(priv->reg, STM32_LPTIM_IER, STM32_LPTIM_ARRMIE);
71
72 /* Poll DIEROK and ARROK to ensure register access has completed */
73 ret = regmap_read_poll_timeout_atomic(priv->reg, STM32_LPTIM_ISR, val,
74 (val & STM32_LPTIM_DIEROK_ARROK) ==
75 STM32_LPTIM_DIEROK_ARROK,
76 10, 500);
77 if (ret) {
78 dev_err(priv->dev, "access to LPTIM timed out\n");
79 /* Disable LPTIMER */
80 regmap_write(priv->reg, STM32_LPTIM_CR, 0);
81 return ret;
82 }
83 /* Clear DIEROK and ARROK flags */
84 regmap_write(priv->reg, STM32_LPTIM_ICR, STM32_LPTIM_DIEROKCF_ARROKCF);
85
86 return 0;
87 }
88
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-04-26 7:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 12:47 [PATCH v5 0/7] Add STM32MP25 LPTIM support: MFD, PWM, IIO, counter, clocksource Fabrice Gasnier
2025-04-25 12:47 ` [PATCH v5 1/7] dt-bindings: mfd: stm32-lptimer: add support for stm32mp25 Fabrice Gasnier
2025-04-25 12:47 ` [PATCH v5 2/7] " Fabrice Gasnier
2025-04-25 12:47 ` [PATCH v5 3/7] clocksource: " Fabrice Gasnier
2025-04-26 7:01 ` kernel test robot [this message]
2025-04-25 12:47 ` [PATCH v5 4/7] pwm: stm32-lp: " Fabrice Gasnier
2025-04-25 12:47 ` [PATCH v5 5/7] arm64: defconfig: enable STM32 LP timer clockevent driver Fabrice Gasnier
2025-04-25 12:47 ` [PATCH v5 6/7] arm64: dts: st: add low-power timer nodes on stm32mp251 Fabrice Gasnier
2025-04-25 12:47 ` [PATCH v5 7/7] arm64: dts: st: use lptimer3 as tick broadcast source on stm32mp257f-ev1 Fabrice Gasnier
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=202504261456.aCATBoYN-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@foss.st.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=olivier.moysan@foss.st.com \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
--cc=ukleinek@kernel.org \
--cc=wbg@kernel.org \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).