From: Sasha Levin <sashal@kernel.org>
To: patches@lists.linux.dev, stable@vger.kernel.org
Cc: Pei Xiao <xiaopei01@kylinos.cn>,
kernel test robot <lkp@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Sasha Levin <sashal@kernel.org>,
dixitparmar19@gmail.com
Subject: [PATCH AUTOSEL 6.18-6.1] iio: adc: ti_am335x_adc: Limit step_avg to valid range for gcc complains
Date: Wed, 10 Dec 2025 01:34:33 -0500 [thread overview]
Message-ID: <20251210063446.2513466-4-sashal@kernel.org> (raw)
In-Reply-To: <20251210063446.2513466-1-sashal@kernel.org>
From: Pei Xiao <xiaopei01@kylinos.cn>
[ Upstream commit c9fb952360d0c78bbe98239bd6b702f05c2dbb31 ]
FIELD_PREP() checks that a value fits into the available bitfield, add a
check for step_avg to fix gcc complains.
which gcc complains about:
drivers/iio/adc/ti_am335x_adc.c: In function 'tiadc_step_config':
include/linux/compiler_types.h:572:38: error: call to
'__compiletime_assert_491' declared with attribute error: FIELD_PREP: value
too large for the field include/linux/mfd/ti_am335x_tscadc.h:58:29: note:
in expansion of macro 'FIELD_PREP'
#define STEPCONFIG_AVG(val) FIELD_PREP(GENMASK(4, 2), (val))
^~~~~~~~~~
drivers/iio/adc/ti_am335x_adc.c:127:17: note: in expansion of macro 'STEPCONFIG_AVG'
stepconfig = STEPCONFIG_AVG(ffs(adc_dev->step_avg[i]) - 1)
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202510102117.Jqxrw1vF-lkp@intel.com/
Signed-off-by: Pei Xiao <xiaopei01@kylinos.cn>
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
LLM Generated explanations, may be completely bogus:
Now I understand the full context:
**Key findings:**
- `STEPCONFIG_AVG(val)` uses `FIELD_PREP(GENMASK(4, 2), (val))` - a
3-bit field
- `STEPCONFIG_AVG_16` = `STEPCONFIG_AVG(4)` = 16 (the register value)
- `step_avg[i]` stores the number of samples (1, 2, 4, 8, 16)
- The comparison `step_avg[i] <= STEPCONFIG_AVG_16` bounds step_avg to ≤
16
### SUMMARY
| Criterion | Assessment |
|-----------|------------|
| **Type of fix** | BUILD FIX - compile error |
| **Size** | 1 line change |
| **Risk** | Very Low |
| **User impact** | Prevents kernel compilation failure |
| **Subsystem** | TI AM335x ADC (BeagleBone, embedded systems) |
| **Cc: stable** | No |
| **Fixes: tag** | No |
| **Reported-by** | Yes (kernel test robot) |
### ASSESSMENT
**Why this should be backported:**
1. **Build Fix Category**: This explicitly fixes a GCC compilation
error. Build fixes are one of the allowed exception categories for
stable trees because they prevent users from being able to compile
the kernel at all.
2. **The Error is a Hard Failure**: The gcc error `error: call to
'__compiletime_assert_491' declared with attribute error: FIELD_PREP:
value too large for the field` is a hard compilation failure, not
just a warning. Users with certain GCC versions/configurations cannot
build the kernel with this driver enabled.
3. **Minimal Risk**: The fix simply adds a bounds check (`&&
adc_dev->step_avg[i] <= STEPCONFIG_AVG_16`) to an existing condition.
Invalid values now fall through to the else branch (default
behavior), which is safe.
4. **No Functional Change for Valid Inputs**: For valid step_avg values
(1, 2, 4, 8, 16), the behavior is identical. Only theoretically
invalid values are now handled differently.
5. **Driver Exists in All Stable Trees**: The TI AM335x ADC driver has
been in the kernel for years and exists in all active stable
branches.
**Concerns:**
- No explicit `Cc: stable` tag
- No `Fixes:` tag
- The maintainer didn't specifically request backporting
However, the absence of these tags doesn't disqualify a build fix. Build
fixes are essential for kernel buildability and are routinely
backported.
The fix is obviously correct, small, contained, and addresses a real
build failure reported by the kernel test robot infrastructure. It meets
the stable kernel criteria for a build fix.
**YES**
drivers/iio/adc/ti_am335x_adc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iio/adc/ti_am335x_adc.c b/drivers/iio/adc/ti_am335x_adc.c
index 99f274adc870d..a1a28584de930 100644
--- a/drivers/iio/adc/ti_am335x_adc.c
+++ b/drivers/iio/adc/ti_am335x_adc.c
@@ -123,7 +123,7 @@ static void tiadc_step_config(struct iio_dev *indio_dev)
chan = adc_dev->channel_line[i];
- if (adc_dev->step_avg[i])
+ if (adc_dev->step_avg[i] && adc_dev->step_avg[i] <= STEPCONFIG_AVG_16)
stepconfig = STEPCONFIG_AVG(ffs(adc_dev->step_avg[i]) - 1) |
STEPCONFIG_FIFO1;
else
--
2.51.0
next prev parent reply other threads:[~2025-12-10 6:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 6:34 [PATCH AUTOSEL 6.18-5.10] serial: sprd: Return -EPROBE_DEFER when uart clock is not ready Sasha Levin
2025-12-10 6:34 ` [PATCH AUTOSEL 6.18-5.10] usb: xhci: limit run_graceperiod for only usb 3.0 devices Sasha Levin
2025-12-10 6:34 ` [PATCH AUTOSEL 6.18-5.10] usb: typec: ucsi: Handle incorrect num_connectors capability Sasha Levin
2025-12-10 6:34 ` Sasha Levin [this message]
2025-12-10 6:34 ` [PATCH AUTOSEL 6.18-5.10] usbip: Fix locking bug in RT-enabled kernels Sasha Levin
2025-12-10 6:34 ` [PATCH AUTOSEL 6.18-6.17] usb: xhci: Don't unchain link TRBs on quirky HCs Sasha Levin
2025-12-10 6:34 ` [PATCH AUTOSEL 6.18-6.6] libperf cpumap: Fix perf_cpu_map__max for an empty/NULL map Sasha Levin
2025-12-10 6:34 ` [PATCH AUTOSEL 6.18-5.10] usb: usb-storage: No additional quirks need to be added to the EL-R12 optical drive Sasha Levin
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=20251210063446.2513466-4-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=dixitparmar19@gmail.com \
--cc=lkp@intel.com \
--cc=patches@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=xiaopei01@kylinos.cn \
/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