[PATCH 1/4] regulator: rpi-panel-attiny: don't double-check GPIO range
From: Bartosz Golaszewski
Date: Tue Apr 08 2025 - 03:39:02 EST
From: Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxx>
GPIO core already checks GPIO ranges, there's no need to check it again
in the set() callback.
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxx>
---
drivers/regulator/rpi-panel-attiny-regulator.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/regulator/rpi-panel-attiny-regulator.c b/drivers/regulator/rpi-panel-attiny-regulator.c
index 6c3b6bfac961..f5ce50ced294 100644
--- a/drivers/regulator/rpi-panel-attiny-regulator.c
+++ b/drivers/regulator/rpi-panel-attiny-regulator.c
@@ -216,9 +216,6 @@ static void attiny_gpio_set(struct gpio_chip *gc, unsigned int off, int val)
struct attiny_lcd *state = gpiochip_get_data(gc);
u8 last_val;
- if (off >= NUM_GPIO)
- return;
-
mutex_lock(&state->lock);
last_val = attiny_get_port_state(state, mappings[off].reg);
--
2.45.2