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

Groups > linux.kernel > #1298056 > unrolled thread

[PATCH v2 0/5] watchdog: Do not use 'dev' from watchdog_device in watchdog drivers

Started byGuenter Roeck <linux@roeck-us.net>
First post2015-12-24 23:30 +0100
Last post2015-12-29 01:10 +0100
Articles 8 — 2 participants

Back to article view | Back to linux.kernel

Contents

  [PATCH v2 0/5] watchdog: Do not use 'dev' from watchdog_device in watchdog drivers Guenter Roeck <linux@roeck-us.net> - 2015-12-24 23:30 +0100
    [PATCH v2 5/5] watchdog: qcom-wdt: Do not set 'dev' in struct watchdog_device Guenter Roeck <linux@roeck-us.net> - 2015-12-24 23:30 +0100
    [PATCH v2 3/5] watchdog: gpio: Do not use device pointer from struct watchdog_device Guenter Roeck <linux@roeck-us.net> - 2015-12-24 23:30 +0100
    [PATCH v2 4/5] watchdog: mena21: Do not use device pointer from struct watchdog_device Guenter Roeck <linux@roeck-us.net> - 2015-12-24 23:30 +0100
    [PATCH v2 1/5] watchdog: bcm2835_wdt: Drop log message if watchdog is stopped Guenter Roeck <linux@roeck-us.net> - 2015-12-24 23:30 +0100
    [PATCH v2 2/5] watchdog: tangox: Print info message using pointer to platform device Guenter Roeck <linux@roeck-us.net> - 2015-12-24 23:30 +0100
    Re: [PATCH v2 0/5] watchdog: Do not use 'dev' from watchdog_device in watchdog drivers Wim Van Sebroeck <wim@iguana.be> - 2015-12-28 23:20 +0100
      Re: [PATCH v2 0/5] watchdog: Do not use 'dev' from watchdog_device  in watchdog drivers Guenter Roeck <linux@roeck-us.net> - 2015-12-29 01:10 +0100

#1298056 — [PATCH v2 0/5] watchdog: Do not use 'dev' from watchdog_device in watchdog drivers

FromGuenter Roeck <linux@roeck-us.net>
Date2015-12-24 23:30 +0100
Subject[PATCH v2 0/5] watchdog: Do not use 'dev' from watchdog_device in watchdog drivers
Message-ID<qJmyt-3WH-1@gated-at.bofh.it>
The 'dev' variable in watchdog drivers has a different lifetime than the
watchdog character device and should therefore not be used by watchdog
drivers.

Some of the drivers use the variable to print kernel messages. Those
messages are either dropped or changed to use the parent device.
One driver sets the variable during initialization to the watchdog
driver's parent device, which is wrong and was removed.

v2: Use parent device for dev_XXX messages instead of pr_XXX.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1298058 — [PATCH v2 5/5] watchdog: qcom-wdt: Do not set 'dev' in struct watchdog_device

FromGuenter Roeck <linux@roeck-us.net>
Date2015-12-24 23:30 +0100
Subject[PATCH v2 5/5] watchdog: qcom-wdt: Do not set 'dev' in struct watchdog_device
Message-ID<qJmyt-3WH-11@gated-at.bofh.it>
In reply to#1298056
The 'dev' pointer in struct watchdog_device is set by the watchdog core
when registering the watchdog device and not by the driver. It points to
the watchdog device, not its parent.

Signed-off-by: Guenter Roeck <linux@roeck-us.net>
---
v2: No change

 drivers/watchdog/qcom-wdt.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/watchdog/qcom-wdt.c b/drivers/watchdog/qcom-wdt.c
index aa7105d32c02..424f9a952fee 100644
--- a/drivers/watchdog/qcom-wdt.c
+++ b/drivers/watchdog/qcom-wdt.c
@@ -164,7 +164,6 @@ static int qcom_wdt_probe(struct platform_device *pdev)
 		goto err_clk_unprepare;
 	}
 
-	wdt->wdd.dev = &pdev->dev;
 	wdt->wdd.info = &qcom_wdt_info;
 	wdt->wdd.ops = &qcom_wdt_ops;
 	wdt->wdd.min_timeout = 1;
-- 
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1298059 — [PATCH v2 3/5] watchdog: gpio: Do not use device pointer from struct watchdog_device

FromGuenter Roeck <linux@roeck-us.net>
Date2015-12-24 23:30 +0100
Subject[PATCH v2 3/5] watchdog: gpio: Do not use device pointer from struct watchdog_device
Message-ID<qJmyt-3WH-15@gated-at.bofh.it>
In reply to#1298056
The device pointer in struct watchdog_device has a different lifetime
than the driver code and should not be used in drivers. Use the pointer
to the parent device instead.

Signed-off-by: Guenter Roeck <linux@roeck-us.net>
---
v2: Print messages using parent device

 drivers/watchdog/gpio_wdt.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/watchdog/gpio_wdt.c b/drivers/watchdog/gpio_wdt.c
index 035c2387b846..ba066e4a707b 100644
--- a/drivers/watchdog/gpio_wdt.c
+++ b/drivers/watchdog/gpio_wdt.c
@@ -54,7 +54,8 @@ static void gpio_wdt_hwping(unsigned long data)
 
 	if (priv->armed && time_after(jiffies, priv->last_jiffies +
 				      msecs_to_jiffies(wdd->timeout * 1000))) {
-		dev_crit(wdd->dev, "Timer expired. System will reboot soon!\n");
+		dev_crit(wdd->parent,
+			 "Timer expired. System will reboot soon!\n");
 		return;
 	}
 
-- 
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1298060 — [PATCH v2 4/5] watchdog: mena21: Do not use device pointer from struct watchdog_device

FromGuenter Roeck <linux@roeck-us.net>
Date2015-12-24 23:30 +0100
Subject[PATCH v2 4/5] watchdog: mena21: Do not use device pointer from struct watchdog_device
Message-ID<qJmyu-3WH-19@gated-at.bofh.it>
In reply to#1298056
The device pointer in struct watchdog_device has a different lifetime
than the driver code and should not be used in drivers. Use the pointer
to the parent device instead.

Signed-off-by: Guenter Roeck <linux@roeck-us.net>
---
v2: Print messages using parent device

 drivers/watchdog/mena21_wdt.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/watchdog/mena21_wdt.c b/drivers/watchdog/mena21_wdt.c
index 098fa9c34d6d..af6a7c489f08 100644
--- a/drivers/watchdog/mena21_wdt.c
+++ b/drivers/watchdog/mena21_wdt.c
@@ -100,12 +100,12 @@ static int a21_wdt_set_timeout(struct watchdog_device *wdt,
 	struct a21_wdt_drv *drv = watchdog_get_drvdata(wdt);
 
 	if (timeout != 1 && timeout != 30) {
-		dev_err(wdt->dev, "Only 1 and 30 allowed as timeout\n");
+		dev_err(wdt->parent, "Only 1 and 30 allowed as timeout\n");
 		return -EINVAL;
 	}
 
 	if (timeout == 30 && wdt->timeout == 1) {
-		dev_err(wdt->dev,
+		dev_err(wdt->parent,
 			"Transition from fast to slow mode not allowed\n");
 		return -EINVAL;
 	}
-- 
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1298061 — [PATCH v2 1/5] watchdog: bcm2835_wdt: Drop log message if watchdog is stopped

FromGuenter Roeck <linux@roeck-us.net>
Date2015-12-24 23:30 +0100
Subject[PATCH v2 1/5] watchdog: bcm2835_wdt: Drop log message if watchdog is stopped
Message-ID<qJmyu-3WH-23@gated-at.bofh.it>
In reply to#1298056
Stopping a watchdog is a normal operation and does not warrant a log
message.

Signed-off-by: Guenter Roeck <linux@roeck-us.net>
---
v2: No change

 drivers/watchdog/bcm2835_wdt.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/watchdog/bcm2835_wdt.c b/drivers/watchdog/bcm2835_wdt.c
index 8a5ce5b5a0b6..2e6164c4abc0 100644
--- a/drivers/watchdog/bcm2835_wdt.c
+++ b/drivers/watchdog/bcm2835_wdt.c
@@ -79,7 +79,6 @@ static int bcm2835_wdt_stop(struct watchdog_device *wdog)
 	struct bcm2835_wdt *wdt = watchdog_get_drvdata(wdog);
 
 	writel_relaxed(PM_PASSWORD | PM_RSTC_RESET, wdt->base + PM_RSTC);
-	dev_info(wdog->dev, "Watchdog timer stopped");
 	return 0;
 }
 
-- 
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1298062 — [PATCH v2 2/5] watchdog: tangox: Print info message using pointer to platform device

FromGuenter Roeck <linux@roeck-us.net>
Date2015-12-24 23:30 +0100
Subject[PATCH v2 2/5] watchdog: tangox: Print info message using pointer to platform device
Message-ID<qJmyu-3WH-27@gated-at.bofh.it>
In reply to#1298056
The device pointer in struct watchdog_device should not be used by drivers
and may be removed in the near future. Use the platform device pointer for
info messages instead.

Signed-off-by: Guenter Roeck <linux@roeck-us.net>
---
v2: No change

 drivers/watchdog/tangox_wdt.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/watchdog/tangox_wdt.c b/drivers/watchdog/tangox_wdt.c
index b9ee6246e7c2..709c1ed6fd79 100644
--- a/drivers/watchdog/tangox_wdt.c
+++ b/drivers/watchdog/tangox_wdt.c
@@ -184,7 +184,7 @@ static int tangox_wdt_probe(struct platform_device *pdev)
 	if (err)
 		dev_warn(&pdev->dev, "failed to register restart handler\n");
 
-	dev_info(dev->wdt.dev, "SMP86xx/SMP87xx watchdog registered\n");
+	dev_info(&pdev->dev, "SMP86xx/SMP87xx watchdog registered\n");
 
 	return 0;
 }
-- 
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1298772

FromWim Van Sebroeck <wim@iguana.be>
Date2015-12-28 23:20 +0100
Message-ID<qKOiZ-8ic-3@gated-at.bofh.it>
In reply to#1298056
Hi Guenter,

> The 'dev' variable in watchdog drivers has a different lifetime than the
> watchdog character device and should therefore not be used by watchdog
> drivers.
> 
> Some of the drivers use the variable to print kernel messages. Those
> messages are either dropped or changed to use the parent device.
> One driver sets the variable during initialization to the watchdog
> driver's parent device, which is wrong and was removed.
> 
> v2: Use parent device for dev_XXX messages instead of pr_XXX.

This patchset has been added to linux-watchdog-next.

Kind regards,
Wim.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1298806 — Re: [PATCH v2 0/5] watchdog: Do not use 'dev' from watchdog_device in watchdog drivers

FromGuenter Roeck <linux@roeck-us.net>
Date2015-12-29 01:10 +0100
SubjectRe: [PATCH v2 0/5] watchdog: Do not use 'dev' from watchdog_device in watchdog drivers
Message-ID<qKQ1t-10i-39@gated-at.bofh.it>
In reply to#1298772
On Mon, Dec 28, 2015 at 11:15:10PM +0100, Wim Van Sebroeck wrote:
> Hi Guenter,
> 
> > The 'dev' variable in watchdog drivers has a different lifetime than the
> > watchdog character device and should therefore not be used by watchdog
> > drivers.
> > 
> > Some of the drivers use the variable to print kernel messages. Those
> > messages are either dropped or changed to use the parent device.
> > One driver sets the variable during initialization to the watchdog
> > driver's parent device, which is wrong and was removed.
> > 
> > v2: Use parent device for dev_XXX messages instead of pr_XXX.
> 
> This patchset has been added to linux-watchdog-next.
> 

Thanks!

Guenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web