summaryrefslogtreecommitdiff
path: root/tools/lib/python
diff options
context:
space:
mode:
authorSalah Triki <salah.triki@gmail.com>2026-08-19 18:51:19 +0100
committerJonathan Cameron <jonathan.cameron@oss.qualcomm.com>2026-08-31 00:52:42 +0100
commit2093236e886ad9446ec3285ba520e024dd1464e1 (patch)
tree50102328f3e494068ed06ae1724c7da9578386d6 /tools/lib/python
parentd380bf5f94a892e546d9a94e8557ad866b043a2a (diff)
downloadlinux-next-2093236e886ad9446ec3285ba520e024dd1464e1.tar.gz
linux-next-2093236e886ad9446ec3285ba520e024dd1464e1.zip
iio: frequency: admv1013: fix wrong channel field used in admv1013_read_raw()
admv1013_read_raw() switches on chan->channel instead of chan->channel2 when handling IIO_CHAN_INFO_CALIBBIAS. The channel field only ever holds 0 or 1 (see ADMV1013_CHAN_CALIB()), while the IIO_MOD_I / IIO_MOD_Q modifiers are stored in channel2. As a result, the switch always falls through to the default case and calibbias reads always fail with -EINVAL, even though the corresponding admv1013_write_raw() path correctly uses channel2 and works as expected. Fix the read path to switch on chan->channel2, matching the write path and the actual channel_spec definition. Fixes: da35a7b526d9 ("iio: frequency: admv1013: add support for ADMV1013") Signed-off-by: Salah Triki <salah.triki@gmail.com> Cc: stable@vger.kernel.org Signed-off-by: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions