From: Philipp Zabel Date: Wed, 19 Jul 2017 15:25:36 +0000 (+0200) Subject: iio: dac: stm32-dac-core: explicitly request exclusive reset control X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=a1b509dfc163b39327da3ac021fe41f8757307fa;p=GitHub%2Fmoto-9609%2Fandroid_kernel_motorola_exynos9610.git iio: dac: stm32-dac-core: explicitly request exclusive reset control Commit a53e35db70d1 ("reset: Ensure drivers are explicit when requesting reset lines") started to transition the reset control request API calls to explicitly state whether the driver needs exclusive or shared reset control behavior. Convert all drivers requesting exclusive resets to the explicit API call so the temporary transition helpers can be removed. No functional changes. Cc: Jonathan Cameron Cc: Hartmut Knaack Cc: Lars-Peter Clausen Cc: Peter Meerwald-Stadler Cc: Maxime Coquelin Cc: Alexandre Torgue Cc: linux-iio@vger.kernel.org Signed-off-by: Philipp Zabel Signed-off-by: Jonathan Cameron --- diff --git a/drivers/iio/dac/stm32-dac-core.c b/drivers/iio/dac/stm32-dac-core.c index 32701be71cf7..55026fe1c610 100644 --- a/drivers/iio/dac/stm32-dac-core.c +++ b/drivers/iio/dac/stm32-dac-core.c @@ -125,7 +125,7 @@ static int stm32_dac_probe(struct platform_device *pdev) goto err_vref; } - priv->rst = devm_reset_control_get(dev, NULL); + priv->rst = devm_reset_control_get_exclusive(dev, NULL); if (!IS_ERR(priv->rst)) { reset_control_assert(priv->rst); udelay(2);