From: sashiko-bot@kernel.org
To: "Fabrice Gasnier" <fabrice.gasnier@foss.st.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 09/15] iio: adc: stm32-adc: add support for stm32mp23
Date: Wed, 30 Sep 2026 14:31:37 +0000 [thread overview]
Message-ID: <20260930143138.601721F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260930-adc-stm32mp25-v1-v3-9-406834430d72@foss.st.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] iio: adc: missing const qualifier on trigger arrays
--
commit e6098517cec9404a97ce36281256eb9d77667464
Author: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
iio: adc: stm32-adc: add support for stm32mp23
Add support for ADC on the STM32MP23 SoC, which has 3 ADCs split into two
blocks. The STM32MP23 trigger list is handled with dedicated compatible data
due to differences from the STM32MP25.
> diff --git a/drivers/iio/adc/stm32-adc.c b/drivers/iio/adc/stm32-adc.c
> index 33e41505b2e99..210b76b21d13b 100644
> --- a/drivers/iio/adc/stm32-adc.c
> +++ b/drivers/iio/adc/stm32-adc.c
[ ... ]
> @@ -563,6 +563,64 @@ static const struct stm32_adc_regspec stm32h7_adc_regspec = {
> .smp_bits = stm32h7_smp_bits,
> };
>
> +/* STM32MP23 external trigger sources for ADC1 and ADC2 */
> +static struct stm32_adc_trig_info stm32mp23_adc1_adc2_trigs[] = {
[Severity: Low]
Should this array be declared as const? The trigs field in struct
stm32_adc_cfg expects a const struct stm32_adc_trig_info *.
> + { TIM1_TRGO, STM32_EXT0 },
> + { TIM1_TRGO2, STM32_EXT1 },
> + { TIM8_TRGO, STM32_EXT2 },
[ ... ]
> + { LPTIM4_CH1, STM32_EXT27 },
> + { LPTIM5_OUT, STM32_EXT28 },
> + { }
> +};
> +
> +/* STM32MP23 external trigger sources for ADC3 */
> +static struct stm32_adc_trig_info stm32mp23_adc3_trigs[] = {
[Severity: Low]
Does this array also need a const qualifier?
> + { TIM1_TRGO, STM32_EXT0 },
> + { TIM1_TRGO2, STM32_EXT1 },
> + { TIM8_TRGO, STM32_EXT2 },
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260930-adc-stm32mp25-v1-v3-0-406834430d72@foss.st.com?part=9
next prev parent reply other threads:[~2026-09-30 14:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 14:18 [PATCH v3 00/15] iio: adc: stm32: add support for stm32mp23 and stm32mp25 Fabrice Gasnier
2026-09-30 14:18 ` [PATCH v3 01/15] dt-bindings: iio: adc: stm32-adc: " Fabrice Gasnier
2026-09-30 14:29 ` sashiko-bot
2026-09-30 21:18 ` Conor Dooley
2026-09-30 14:18 ` [PATCH v3 02/15] iio: adc: stm32-adc: core: manage clock prescaler diversity Fabrice Gasnier
2026-09-30 14:18 ` [PATCH v3 03/15] iio: adc: stm32-adc: core: configurable number of interrupts Fabrice Gasnier
2026-09-30 14:18 ` [PATCH v3 04/15] iio: adc: stm32-adc: manage characterization voltage diversity Fabrice Gasnier
2026-09-30 14:54 ` Joshua Crofts
2026-09-30 14:18 ` [PATCH v3 05/15] iio: adc: stm32-adc: rework internal channels data Fabrice Gasnier
2026-09-30 14:18 ` [PATCH v3 06/15] iio: adc: stm32-adc: add vreg enable option to manage diversity Fabrice Gasnier
2026-09-30 15:01 ` Joshua Crofts
2026-09-30 14:18 ` [PATCH v3 07/15] iio: adc: stm32-adc: preferred style cleanup Fabrice Gasnier
2026-09-30 14:18 ` [PATCH v3 08/15] iio: adc: stm32-adc: add support for stm32mp25 Fabrice Gasnier
2026-09-30 14:38 ` sashiko-bot
2026-09-30 14:18 ` [PATCH v3 09/15] iio: adc: stm32-adc: add support for stm32mp23 Fabrice Gasnier
2026-09-30 14:31 ` sashiko-bot [this message]
2026-09-30 15:12 ` Joshua Crofts
2026-09-30 14:18 ` [PATCH v3 10/15] iio: adc: stm32-adc: add support for vddgpu on stm32mp23 and stm32mp25 Fabrice Gasnier
2026-09-30 14:18 ` [PATCH v3 11/15] arm64: dts: st: add vrefint calibration on stm32mp23 Fabrice Gasnier
2026-09-30 14:18 ` [PATCH v3 12/15] arm64: dts: st: add vrefint calibration on stm32mp25 Fabrice Gasnier
2026-09-30 14:18 ` [PATCH v3 13/15] arm64: dts: st: add ADC nodes on stm32mp231 Fabrice Gasnier
2026-09-30 14:18 ` [PATCH v3 14/15] arm64: dts: st: add ADC nodes on stm32mp251 Fabrice Gasnier
2026-09-30 14:18 ` [PATCH v3 15/15] arm64: dts: st: add ADC support on stm32mp257f-ev1 board 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=20260930143138.601721F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@foss.st.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@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