[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200519115735.GL20066@paasikivi.fi.intel.com>
Date: Tue, 19 May 2020 14:57:35 +0300
From: Sakari Ailus <sakari.ailus@...ux.intel.com>
To: Roman Kovalivskyi <roman.kovalivskyi@...ballogic.com>
Cc: linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
linux-renesas-soc@...r.kernel.org,
Luis Oliveira <lolivei@...opsys.com>,
Niklas Söderlund
<niklas.soderlund@...natech.se>, Jacopo Mondi <jacopo@...ndi.org>,
Michael Rodin <mrodin@...adit-jv.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Hugues Fruchet <hugues.fruchet@...com>,
Maxime Ripard <mripard@...nel.org>,
Adam Ford <aford173@...il.com>,
Todor Tomov <todor.tomov@...aro.org>,
Suresh Udipi <sudipi@...adit-jv.com>,
Andrew Gabbasov <andrew_gabbasov@...tor.com>,
Eugeniu Rosca <erosca@...adit-jv.com>,
Dave Stevenson <dave.stevenson@...pberrypi.org>
Subject: Re: [PATCH v2 4/6] media: ov5647: Use gpiod_set_value_cansleep
On Tue, May 19, 2020 at 04:16:19AM +0300, Roman Kovalivskyi wrote:
> From: Dave Stevenson <dave.stevenson@...pberrypi.org>
>
> All calls to the gpio library are in contexts that can sleep,
> therefore there is no issue with having those GPIOs controlled
> by controllers which require sleeping (eg I2C GPIO expanders).
>
> Switch to using gpiod_set_value_cansleep instead of gpiod_set_value
> to avoid triggering the warning in gpiolib should the GPIO
> controller need to sleep.
>
> Signed-off-by: Dave Stevenson <dave.stevenson@...pberrypi.org>
> Signed-off-by: Roman Kovalivskyi <roman.kovalivskyi@...ballogic.com>
This needs to be merged with the 2nd patch.
--
Sakari Ailus
Powered by blists - more mailing lists