Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1691890 > unrolled thread

[PATCH 096/102] watchdog: zx2967: explicitly request exclusive reset control

Started byPhilipp Zabel <p.zabel@pengutronix.de>
First post2017-07-19 17:40 +0200
Last post2017-07-19 19:40 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  [PATCH 096/102] watchdog: zx2967: explicitly request exclusive reset control Philipp Zabel <p.zabel@pengutronix.de> - 2017-07-19 17:40 +0200
    Re: [PATCH 096/102] watchdog: zx2967: explicitly request exclusive  reset control Guenter Roeck <linux@roeck-us.net> - 2017-07-19 19:40 +0200

#1691890 — [PATCH 096/102] watchdog: zx2967: explicitly request exclusive reset control

FromPhilipp Zabel <p.zabel@pengutronix.de>
Date2017-07-19 17:40 +0200
Subject[PATCH 096/102] watchdog: zx2967: explicitly request exclusive reset control
Message-ID<u4ZeY-222-51@gated-at.bofh.it>
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: Wim Van Sebroeck <wim@iguana.be>
Cc: Guenter Roeck <linux@roeck-us.net>
Cc: linux-watchdog@vger.kernel.org
Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
---
 drivers/watchdog/zx2967_wdt.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/watchdog/zx2967_wdt.c b/drivers/watchdog/zx2967_wdt.c
index 69ec5855584b1..9261f7c77f6de 100644
--- a/drivers/watchdog/zx2967_wdt.c
+++ b/drivers/watchdog/zx2967_wdt.c
@@ -229,7 +229,7 @@ static int zx2967_wdt_probe(struct platform_device *pdev)
 	}
 	clk_set_rate(wdt->clock, ZX2967_WDT_CLK_FREQ);
 
-	rstc = devm_reset_control_get(dev, NULL);
+	rstc = devm_reset_control_get_exclusive(dev, NULL);
 	if (IS_ERR(rstc)) {
 		dev_err(dev, "failed to get rstc");
 		ret = PTR_ERR(rstc);
-- 
2.11.0

[toc] | [next] | [standalone]


#1692056 — Re: [PATCH 096/102] watchdog: zx2967: explicitly request exclusive reset control

FromGuenter Roeck <linux@roeck-us.net>
Date2017-07-19 19:40 +0200
SubjectRe: [PATCH 096/102] watchdog: zx2967: explicitly request exclusive reset control
Message-ID<u5175-3pP-17@gated-at.bofh.it>
In reply to#1691890
On Wed, Jul 19, 2017 at 05:26:40PM +0200, Philipp Zabel wrote:
> 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: Wim Van Sebroeck <wim@iguana.be>
> Cc: Guenter Roeck <linux@roeck-us.net>
> Cc: linux-watchdog@vger.kernel.org
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>

Reviewed-by: Guenter Roeck <linux@roeck-us.net>

> ---
>  drivers/watchdog/zx2967_wdt.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/watchdog/zx2967_wdt.c b/drivers/watchdog/zx2967_wdt.c
> index 69ec5855584b1..9261f7c77f6de 100644
> --- a/drivers/watchdog/zx2967_wdt.c
> +++ b/drivers/watchdog/zx2967_wdt.c
> @@ -229,7 +229,7 @@ static int zx2967_wdt_probe(struct platform_device *pdev)
>  	}
>  	clk_set_rate(wdt->clock, ZX2967_WDT_CLK_FREQ);
>  
> -	rstc = devm_reset_control_get(dev, NULL);
> +	rstc = devm_reset_control_get_exclusive(dev, NULL);
>  	if (IS_ERR(rstc)) {
>  		dev_err(dev, "failed to get rstc");
>  		ret = PTR_ERR(rstc);
> -- 
> 2.11.0
> 

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web