There is no need to require non-sleeping GPIO access. Silence the
WARN_ON() if GPIO is using e.g. I2C expanders.

Signed-off-by: Alexander Stein <alexander.st...@ew.tq-group.com>
---
Change in v2:
* None

 drivers/gpu/drm/bridge/ti-sn65dsi83.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/gpu/drm/bridge/ti-sn65dsi83.c 
b/drivers/gpu/drm/bridge/ti-sn65dsi83.c
index a306150a8027..dc26640e7d9b 100644
--- a/drivers/gpu/drm/bridge/ti-sn65dsi83.c
+++ b/drivers/gpu/drm/bridge/ti-sn65dsi83.c
@@ -344,7 +344,7 @@ static void sn65dsi83_atomic_enable(struct drm_bridge 
*bridge,
        }
 
        /* Deassert reset */
-       gpiod_set_value(ctx->enable_gpio, 1);
+       gpiod_set_value_cansleep(ctx->enable_gpio, 1);
        usleep_range(1000, 1100);
 
        /* Get the LVDS format from the bridge state. */
@@ -500,7 +500,7 @@ static void sn65dsi83_atomic_disable(struct drm_bridge 
*bridge,
        int ret;
 
        /* Put the chip in reset, pull EN line low, and assure 10ms reset low 
timing. */
-       gpiod_set_value(ctx->enable_gpio, 0);
+       gpiod_set_value_cansleep(ctx->enable_gpio, 0);
        usleep_range(10000, 11000);
 
        ret = regulator_disable(ctx->vcc);
-- 
2.25.1

Reply via email to