From: Philipp Zabel Date: Wed, 19 Jul 2017 15:25:31 +0000 (+0200) Subject: i2c: mv64xxx: explicitly request exclusive reset control X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=9024ca12ed1067d1d35e4a431cb8f03dcaff0987;p=GitHub%2Fmoto-9609%2Fandroid_kernel_motorola_exynos9610.git i2c: mv64xxx: 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: Wolfram Sang Cc: linux-i2c@vger.kernel.org Signed-off-by: Philipp Zabel Signed-off-by: Wolfram Sang --- diff --git a/drivers/i2c/busses/i2c-mv64xxx.c b/drivers/i2c/busses/i2c-mv64xxx.c index b2ef32b188e1..a832c45276a4 100644 --- a/drivers/i2c/busses/i2c-mv64xxx.c +++ b/drivers/i2c/busses/i2c-mv64xxx.c @@ -820,7 +820,7 @@ mv64xxx_of_config(struct mv64xxx_i2c_data *drv_data, goto out; } - drv_data->rstc = devm_reset_control_get_optional(dev, NULL); + drv_data->rstc = devm_reset_control_get_optional_exclusive(dev, NULL); if (IS_ERR(drv_data->rstc)) { rc = PTR_ERR(drv_data->rstc); goto out;