From: Joshua Crofts via B4 Relay <devnull+joshua.crofts1.gmail.com@kernel.org>
To: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Jean-Francois Dagenais" <jeff.dagenais@gmail.com>,
"Maxime Roussin-Bélanger" <maxime.roussinbelanger@gmail.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Joshua Crofts <joshua.crofts1@gmail.com>,
Jonathan Cameron <jic23@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v5 3/8] iio: light: si1133: remove unused macros
Date: Tue, 05 May 2026 09:31:28 +0200 [thread overview]
Message-ID: <20260505-si1133-checkup-v5-3-5df86a9024ed@gmail.com> (raw)
In-Reply-To: <20260505-si1133-checkup-v5-0-5df86a9024ed@gmail.com>
From: Joshua Crofts <joshua.crofts1@gmail.com>
Remove unused macros unrelated to hardware definition.
No functional change.
Suggested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Signed-off-by: Joshua Crofts <joshua.crofts1@gmail.com>
---
drivers/iio/light/si1133.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/drivers/iio/light/si1133.c b/drivers/iio/light/si1133.c
index bf7bf0f1631d49a1d04b89f172646e4afaf46438..ed9b3e0a12d66d749f09f570de1ccdda2174b6ba 100644
--- a/drivers/iio/light/si1133.c
+++ b/drivers/iio/light/si1133.c
@@ -86,13 +86,9 @@
#define SI1133_CMD_MINSLEEP_US_LOW 5000
#define SI1133_CMD_MINSLEEP_US_HIGH 7500
#define SI1133_CMD_TIMEOUT_MS 25
-#define SI1133_CMD_LUX_TIMEOUT_MS 5000
-#define SI1133_CMD_TIMEOUT_US SI1133_CMD_TIMEOUT_MS * 1000
#define SI1133_REG_HOSTOUT(x) (x) + 0x13
-#define SI1133_MEASUREMENT_FREQUENCY 1250
-
#define SI1133_X_ORDER_MASK 0x0070
#define SI1133_Y_ORDER_MASK 0x0007
#define si1133_get_x_order(m) ((m) & SI1133_X_ORDER_MASK) >> 4
--
2.47.3
next prev parent reply other threads:[~2026-05-05 7:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 7:31 [PATCH v5 0/8] iio: light: si1133: driver cleanup Joshua Crofts via B4 Relay
2026-05-05 7:31 ` [PATCH v5 1/8] iio: light: si1133: reset counter to prevent race condition Joshua Crofts via B4 Relay
2026-05-05 7:31 ` [PATCH v5 2/8] iio: light: si1133: prevent race condition on timeout Joshua Crofts via B4 Relay
2026-05-05 7:31 ` Joshua Crofts via B4 Relay [this message]
2026-05-05 7:31 ` [PATCH v5 4/8] iio: light: si1133: prefer complex macros enclosed in parenthesis Joshua Crofts via B4 Relay
2026-05-05 7:31 ` [PATCH v5 5/8] iio: light: si1133: add missing include headers Joshua Crofts via B4 Relay
2026-05-05 7:31 ` [PATCH v5 6/8] iio: light: si1133: group generic <linux/*> headers Joshua Crofts via B4 Relay
2026-05-05 7:31 ` [PATCH v5 7/8] iio: light: si1133: add local variable for timeout Joshua Crofts via B4 Relay
2026-05-05 12:30 ` Jonathan Cameron
2026-05-05 7:31 ` [PATCH v5 8/8] iio: light: si1133: use guard(mutex)() macro Joshua Crofts via B4 Relay
2026-05-05 12:34 ` [PATCH v5 0/8] iio: light: si1133: driver cleanup Jonathan Cameron
2026-05-05 14:05 ` Joshua Crofts
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=20260505-si1133-checkup-v5-3-5df86a9024ed@gmail.com \
--to=devnull+joshua.crofts1.gmail.com@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jeff.dagenais@gmail.com \
--cc=jic23@kernel.org \
--cc=joshua.crofts1@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.roussinbelanger@gmail.com \
--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