From 06bab1f101337ae9469a7d2c6ac4de5db64e8160 Mon Sep 17 00:00:00 2001 From: Bartosz Golaszewski Date: Tue, 8 Apr 2025 09:36:28 +0200 Subject: [PATCH] regulator: rpi-panel-attiny: don't double-check GPIO range GPIO core already checks GPIO ranges, there's no need to check it again in the set() callback. Signed-off-by: Bartosz Golaszewski Link: https://patch.msgid.link/20250408-gpiochip-set-rv-regulator-v1-1-a18b6154b31a@linaro.org Signed-off-by: Mark Brown --- 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.50.1