From: Dixit Parmar <dixitparmar19@gmail.com>
To: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Gerald Loacker" <gerald.loacker@wolfvision.net>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Dixit Parmar <dixitparmar19@gmail.com>
Subject: [PATCH 2/2] iio: magnetometer: tmag5273: remove unused IIO_CHAN_INFO_PROCESSED handling
Date: Wed, 10 Sep 2025 19:36:50 +0530 [thread overview]
Message-ID: <20250910-iio_chan_617_rc5-v1-2-924091d374be@gmail.com> (raw)
In-Reply-To: <20250910-iio_chan_617_rc5-v1-0-924091d374be@gmail.com>
The tmag5273 driver does not advertise IIO_CHAN_INFO_PROCESSED in its
info_mask_* fields, so the corresponding case in read_raw()/write_raw()
is never used.
Drop the dead code to reduce unnecessary branches and improve clarity.
Signed-off-by: Dixit Parmar <dixitparmar19@gmail.com>
---
drivers/iio/magnetometer/tmag5273.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/iio/magnetometer/tmag5273.c b/drivers/iio/magnetometer/tmag5273.c
index 2ca5c26f0091..ed023eae5e42 100644
--- a/drivers/iio/magnetometer/tmag5273.c
+++ b/drivers/iio/magnetometer/tmag5273.c
@@ -287,7 +287,6 @@ static int tmag5273_read_raw(struct iio_dev *indio_dev,
int ret;
switch (mask) {
- case IIO_CHAN_INFO_PROCESSED:
case IIO_CHAN_INFO_RAW:
ret = pm_runtime_resume_and_get(data->dev);
if (ret < 0)
--
2.43.0
next prev parent reply other threads:[~2025-09-10 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 14:06 [PATCH 0/2] iio: magnetometer: cleanup " Dixit Parmar
2025-09-10 14:06 ` [PATCH 1/2] iio: magnetometer: als31300: remove " Dixit Parmar
2025-09-10 14:06 ` Dixit Parmar [this message]
2025-09-10 16:32 ` [PATCH 0/2] iio: magnetometer: cleanup " Jonathan Cameron
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=20250910-iio_chan_617_rc5-v1-2-924091d374be@gmail.com \
--to=dixitparmar19@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=gerald.loacker@wolfvision.net \
--cc=jic23@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®