From: Guenter Roeck <linux@roeck-us.net>
To: "ivan.khoronzhuk" <ivan.khoronzhuk@ti.com>
Cc: Sekhar Nori <nsekhar@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com,
wim@iguana.be, linux-watchdog@vger.kernel.org,
devicetree@vger.kernel.org, Pawel.Moll@arm.com,
swarren@wwwdotorg.org, ijc+devicetree@hellion.org.uk,
galak@kernel.crashing.org, rob.herring@calxeda.com,
linux-kernel@vger.kernel.org, grant.likely@linaro.org,
grygorii.strashko@ti.com
Subject: Re: [PATCH v4 1/5] watchdog: davinci: change driver to use WDT core
Date: Wed, 4 Dec 2013 10:58:37 -0800 [thread overview]
Message-ID: <20131204185837.GA16166@roeck-us.net> (raw)
In-Reply-To: <529F7797.4080100@ti.com>
On Wed, Dec 04, 2013 at 08:42:31PM +0200, ivan.khoronzhuk wrote:
> On 12/04/2013 08:28 PM, Guenter Roeck wrote:
> > On Wed, Dec 04, 2013 at 11:34:46PM +0530, Sekhar Nori wrote:
> >> On 11/27/2013 6:18 PM, Ivan Khoronzhuk wrote:
> >>> To reduce code duplicate and increase code readability use WDT core
> >>> code to handle WDT interface.
> >>>
> >>> Remove io_lock as the WDT core uses mutex to lock each wdt device.
> >>> Remove wdt_state as the WDT core tracks state with its own variable.
> >>>
> >>> The watchdog_init_timeout() can read timeout value from timeout-sec
> >>> property if the passed value is out of bounds. The heartbeat is
> >>> initialized in next way. If heartbeat is not set thought module
> >>> parameter, try to read it's value from WDT node timeout-sec property.
> >>> If node has no one, use default value.
> >>>
> >>> The heartbeat is hold in wdd->timeout by WDT core, so use it in
> >>> order to set timeout period.
> >>>
> >>> Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> >>> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> >>> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
> >>> ---
> >>> drivers/watchdog/Kconfig | 2 +
> >>> drivers/watchdog/davinci_wdt.c | 147 ++++++++++------------------------------
> >>> 2 files changed, 37 insertions(+), 112 deletions(-)
> >>>
> >>> diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> >>> index 5be6e91..eb8c89d 100644
> >>> --- a/drivers/watchdog/Kconfig
> >>> +++ b/drivers/watchdog/Kconfig
> >>> @@ -271,6 +271,8 @@ config IOP_WATCHDOG
> >>> config DAVINCI_WATCHDOG
> >>> tristate "DaVinci watchdog"
> >>> depends on ARCH_DAVINCI
> >>> + select WATCHDOG_CORE
> >>> + select WATCHDOG_NOWAYOUT
> >>
> >> Its not clear for change log why NOWAYOUT needs to be forced on all the
> >> time for all users of DaVinci watchdog.
>
> ... you are right
>
> >>
> > Actually, thinking about it, it is not necessary and can be replaced with
> >
> > watchdog_set_nowayout(wdd, 1);
>
> Good idea, I'll replace watchdog_set_nowayout(wdd, WATCHDOG_NOWAYOUT) on it.
> And delete "select WATCHDOG_NOWAYOUT"
>
> >
> > In other words, there is no need to force NOWAYOUT on _other_ watchdogs which
> > may be present in the system. Still, you are right, it would be nice to explain
> > in the changelog (or maybe even better as comment in the code) why it is
> > enforced.
> >
> > Guenter
> >
>
> Only question, should I repost only this patch or whole series?
>
Reposting only this patch should be sufficient if the others did not change.
Thanks,
Guenter
WARNING: multiple messages have this Message-ID (diff)
From: linux@roeck-us.net (Guenter Roeck)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/5] watchdog: davinci: change driver to use WDT core
Date: Wed, 4 Dec 2013 10:58:37 -0800 [thread overview]
Message-ID: <20131204185837.GA16166@roeck-us.net> (raw)
In-Reply-To: <529F7797.4080100@ti.com>
On Wed, Dec 04, 2013 at 08:42:31PM +0200, ivan.khoronzhuk wrote:
> On 12/04/2013 08:28 PM, Guenter Roeck wrote:
> > On Wed, Dec 04, 2013 at 11:34:46PM +0530, Sekhar Nori wrote:
> >> On 11/27/2013 6:18 PM, Ivan Khoronzhuk wrote:
> >>> To reduce code duplicate and increase code readability use WDT core
> >>> code to handle WDT interface.
> >>>
> >>> Remove io_lock as the WDT core uses mutex to lock each wdt device.
> >>> Remove wdt_state as the WDT core tracks state with its own variable.
> >>>
> >>> The watchdog_init_timeout() can read timeout value from timeout-sec
> >>> property if the passed value is out of bounds. The heartbeat is
> >>> initialized in next way. If heartbeat is not set thought module
> >>> parameter, try to read it's value from WDT node timeout-sec property.
> >>> If node has no one, use default value.
> >>>
> >>> The heartbeat is hold in wdd->timeout by WDT core, so use it in
> >>> order to set timeout period.
> >>>
> >>> Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> >>> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> >>> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
> >>> ---
> >>> drivers/watchdog/Kconfig | 2 +
> >>> drivers/watchdog/davinci_wdt.c | 147 ++++++++++------------------------------
> >>> 2 files changed, 37 insertions(+), 112 deletions(-)
> >>>
> >>> diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> >>> index 5be6e91..eb8c89d 100644
> >>> --- a/drivers/watchdog/Kconfig
> >>> +++ b/drivers/watchdog/Kconfig
> >>> @@ -271,6 +271,8 @@ config IOP_WATCHDOG
> >>> config DAVINCI_WATCHDOG
> >>> tristate "DaVinci watchdog"
> >>> depends on ARCH_DAVINCI
> >>> + select WATCHDOG_CORE
> >>> + select WATCHDOG_NOWAYOUT
> >>
> >> Its not clear for change log why NOWAYOUT needs to be forced on all the
> >> time for all users of DaVinci watchdog.
>
> ... you are right
>
> >>
> > Actually, thinking about it, it is not necessary and can be replaced with
> >
> > watchdog_set_nowayout(wdd, 1);
>
> Good idea, I'll replace watchdog_set_nowayout(wdd, WATCHDOG_NOWAYOUT) on it.
> And delete "select WATCHDOG_NOWAYOUT"
>
> >
> > In other words, there is no need to force NOWAYOUT on _other_ watchdogs which
> > may be present in the system. Still, you are right, it would be nice to explain
> > in the changelog (or maybe even better as comment in the code) why it is
> > enforced.
> >
> > Guenter
> >
>
> Only question, should I repost only this patch or whole series?
>
Reposting only this patch should be sufficient if the others did not change.
Thanks,
Guenter
WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
To: "ivan.khoronzhuk" <ivan.khoronzhuk-l0cyMroinI0@public.gmane.org>
Cc: Sekhar Nori <nsekhar-l0cyMroinI0@public.gmane.org>,
Santosh Shilimkar
<santosh.shilimkar-l0cyMroinI0@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
wim-IQzOog9fTRqzQB+pC5nmwQ@public.gmane.org,
linux-watchdog-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Pawel.Moll-5wv7dgnIgG8@public.gmane.org,
swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org,
ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org,
galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org,
rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
grygorii.strashko-l0cyMroinI0@public.gmane.org
Subject: Re: [PATCH v4 1/5] watchdog: davinci: change driver to use WDT core
Date: Wed, 4 Dec 2013 10:58:37 -0800 [thread overview]
Message-ID: <20131204185837.GA16166@roeck-us.net> (raw)
In-Reply-To: <529F7797.4080100-l0cyMroinI0@public.gmane.org>
On Wed, Dec 04, 2013 at 08:42:31PM +0200, ivan.khoronzhuk wrote:
> On 12/04/2013 08:28 PM, Guenter Roeck wrote:
> > On Wed, Dec 04, 2013 at 11:34:46PM +0530, Sekhar Nori wrote:
> >> On 11/27/2013 6:18 PM, Ivan Khoronzhuk wrote:
> >>> To reduce code duplicate and increase code readability use WDT core
> >>> code to handle WDT interface.
> >>>
> >>> Remove io_lock as the WDT core uses mutex to lock each wdt device.
> >>> Remove wdt_state as the WDT core tracks state with its own variable.
> >>>
> >>> The watchdog_init_timeout() can read timeout value from timeout-sec
> >>> property if the passed value is out of bounds. The heartbeat is
> >>> initialized in next way. If heartbeat is not set thought module
> >>> parameter, try to read it's value from WDT node timeout-sec property.
> >>> If node has no one, use default value.
> >>>
> >>> The heartbeat is hold in wdd->timeout by WDT core, so use it in
> >>> order to set timeout period.
> >>>
> >>> Acked-by: Santosh Shilimkar <santosh.shilimkar-l0cyMroinI0@public.gmane.org>
> >>> Reviewed-by: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
> >>> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk-l0cyMroinI0@public.gmane.org>
> >>> ---
> >>> drivers/watchdog/Kconfig | 2 +
> >>> drivers/watchdog/davinci_wdt.c | 147 ++++++++++------------------------------
> >>> 2 files changed, 37 insertions(+), 112 deletions(-)
> >>>
> >>> diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> >>> index 5be6e91..eb8c89d 100644
> >>> --- a/drivers/watchdog/Kconfig
> >>> +++ b/drivers/watchdog/Kconfig
> >>> @@ -271,6 +271,8 @@ config IOP_WATCHDOG
> >>> config DAVINCI_WATCHDOG
> >>> tristate "DaVinci watchdog"
> >>> depends on ARCH_DAVINCI
> >>> + select WATCHDOG_CORE
> >>> + select WATCHDOG_NOWAYOUT
> >>
> >> Its not clear for change log why NOWAYOUT needs to be forced on all the
> >> time for all users of DaVinci watchdog.
>
> ... you are right
>
> >>
> > Actually, thinking about it, it is not necessary and can be replaced with
> >
> > watchdog_set_nowayout(wdd, 1);
>
> Good idea, I'll replace watchdog_set_nowayout(wdd, WATCHDOG_NOWAYOUT) on it.
> And delete "select WATCHDOG_NOWAYOUT"
>
> >
> > In other words, there is no need to force NOWAYOUT on _other_ watchdogs which
> > may be present in the system. Still, you are right, it would be nice to explain
> > in the changelog (or maybe even better as comment in the code) why it is
> > enforced.
> >
> > Guenter
> >
>
> Only question, should I repost only this patch or whole series?
>
Reposting only this patch should be sufficient if the others did not change.
Thanks,
Guenter
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-12-04 18:58 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 12:48 [PATCH v4 0/5] Update Davinci watchdog driver Ivan Khoronzhuk
2013-11-27 12:48 ` Ivan Khoronzhuk
2013-11-27 12:48 ` Ivan Khoronzhuk
2013-11-27 12:48 ` [PATCH v4 1/5] watchdog: davinci: change driver to use WDT core Ivan Khoronzhuk
2013-11-27 12:48 ` Ivan Khoronzhuk
2013-11-27 12:48 ` Ivan Khoronzhuk
2013-12-04 18:04 ` Sekhar Nori
2013-12-04 18:04 ` Sekhar Nori
2013-12-04 18:04 ` Sekhar Nori
2013-12-04 18:28 ` Guenter Roeck
2013-12-04 18:28 ` Guenter Roeck
2013-12-04 18:28 ` Guenter Roeck
2013-12-04 18:42 ` ivan.khoronzhuk
2013-12-04 18:42 ` ivan.khoronzhuk
2013-12-04 18:42 ` ivan.khoronzhuk
2013-12-04 18:58 ` Guenter Roeck [this message]
2013-12-04 18:58 ` Guenter Roeck
2013-12-04 18:58 ` Guenter Roeck
2013-12-04 19:06 ` ivan.khoronzhuk
2013-12-04 19:06 ` ivan.khoronzhuk
2013-12-04 19:06 ` ivan.khoronzhuk
2013-11-27 12:48 ` [PATCH v4 2/5] watchdog: davinci: use davinci_wdt_device structure to hold device data Ivan Khoronzhuk
2013-11-27 12:48 ` Ivan Khoronzhuk
2013-11-27 12:48 ` Ivan Khoronzhuk
2013-11-27 12:48 ` [PATCH v4 3/5] watchdog: davinci: add GET_TIMELEFT option support Ivan Khoronzhuk
2013-11-27 12:48 ` Ivan Khoronzhuk
2013-11-27 12:48 ` Ivan Khoronzhuk
2013-11-27 12:48 ` [PATCH v4 4/5] watchdog: davinci: add "timeout-sec" property Ivan Khoronzhuk
2013-11-27 12:48 ` Ivan Khoronzhuk
2013-11-27 12:48 ` Ivan Khoronzhuk
2013-11-27 12:48 ` [PATCH v4 5/5] watchdog: davinci: reuse driver for keystone arch Ivan Khoronzhuk
2013-11-27 12:48 ` Ivan Khoronzhuk
2013-11-27 12:48 ` Ivan Khoronzhuk
2013-11-29 13:18 ` [PATCH v4 0/5] Update Davinci watchdog driver Grygorii Strashko
2013-11-29 13:18 ` Grygorii Strashko
2013-11-29 13:18 ` Grygorii Strashko
2013-11-29 14:57 ` Santosh Shilimkar
2013-11-29 14:57 ` Santosh Shilimkar
2013-11-29 14:57 ` Santosh Shilimkar
2013-12-04 18:10 ` Sekhar Nori
2013-12-04 18:10 ` Sekhar Nori
2013-12-04 18:10 ` Sekhar Nori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131204185837.GA16166@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Pawel.Moll@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@kernel.crashing.org \
--cc=grant.likely@linaro.org \
--cc=grygorii.strashko@ti.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ivan.khoronzhuk@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nsekhar@ti.com \
--cc=rob.herring@calxeda.com \
--cc=santosh.shilimkar@ti.com \
--cc=swarren@wwwdotorg.org \
--cc=wim@iguana.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.