From: "Colin King (gmail)" <colin.i.king@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>,
David Lechner <dlechner@baylibre.com>,
nuno.sa@analog.com, Andy Shevchenko <andy@kernel.org>,
Gustavo Bastos <gustavobastos@usp.br>,
Andrew Ijano <andrew.ijano@gmail.com>,
Julien Stephan <jstephan@baylibre.com>
Cc: linux-iio@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: iio: accel: sca3000: dead code issue
Date: Wed, 2 Jul 2025 10:00:55 +0100 [thread overview]
Message-ID: <1c1e39cb-5fe0-46b3-898e-c65bbb3beb30@gmail.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1884 bytes --]
Hi,
Static analysis on drivers/iio/accel/sca3000.c on linux-next has
detected an issue in the function sca3000_ring_int_process. The
issue is described as follows (prefixed by >>>)
static void sca3000_ring_int_process(u8 val, struct iio_dev *indio_dev)
{
struct sca3000_state *st = iio_priv(indio_dev);
int ret, i, num_available;
mutex_lock(&st->lock);
if (val & SCA3000_REG_INT_STATUS_HALF) {
ret = spi_w8r8(st->us,
SCA3000_READ_REG(SCA3000_REG_BUF_COUNT_ADDR));
>>>
>>> the call to spi_w8r8 returns 0 on success or -ve on an error
>>>
if (ret)
goto error_ret;
>>>
>>> ret is always zero, at this point, so num_available is zero too
>>>
num_available = ret;
/*
* num_available is the total number of samples available
* i.e. number of time points * number of channels.
*/
ret = sca3000_read_data(st, SCA3000_REG_RING_OUT_ADDR,
num_available * 2);
if (ret)
goto error_ret;
>>>
>>> num_available is zero, so for-loop is never executed.
>>>
for (i = 0; i < num_available / 3; i++) {
/*
* Dirty hack to cover for 11 bit in fifo, 13 bit
* direct reading.
*
* In theory the bottom two bits are undefined.
* In reality they appear to always be 0.
*/
iio_push_to_buffers(indio_dev, st->rx + i * 3 * 2);
}
}
I'm not sure what the logic should be to fix this, so I'm reporting this
as an issue.
Regards,
Colin
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 4901 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next reply other threads:[~2025-07-02 9:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 9:00 Colin King (gmail) [this message]
2025-07-02 12:11 ` iio: accel: sca3000: dead code issue Andy Shevchenko
2025-07-02 15:40 ` Jonathan Cameron
2025-07-03 2:52 ` Andrew Ijano
2025-07-03 10:27 ` Jonathan Cameron
2025-07-03 8:00 ` Andy Shevchenko
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=1c1e39cb-5fe0-46b3-898e-c65bbb3beb30@gmail.com \
--to=colin.i.king@gmail.com \
--cc=andrew.ijano@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=gustavobastos@usp.br \
--cc=jic23@kernel.org \
--cc=jstephan@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
/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.