devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "ivan.khoronzhuk" <ivan.khoronzhuk@ti.com>
To: Guenter Roeck <linux@roeck-us.net>, Sekhar Nori <nsekhar@ti.com>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	grygorii.strashko@ti.com, linux-watchdog@vger.kernel.org,
	Pawel Moll <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, wim@iguana.be,
	grant.likely@linaro.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/6] watchdog: davinci: change driver to use WDT core
Date: Wed, 27 Nov 2013 12:03:01 +0200	[thread overview]
Message-ID: <5295C355.6000604@ti.com> (raw)
In-Reply-To: <52959966.7000509@roeck-us.net>

On 11/27/2013 09:04 AM, Guenter Roeck wrote:
> On 11/26/2013 08:31 PM, Sekhar Nori wrote:
>> On Monday 25 November 2013 07:34 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.
>>>
>>> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
>>> Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>>> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
>>
>> So this still causes a regression because the clk_get()
>> fails due to the changed device name. Please fold this
>> patch in (tested on DM365, compiled on rest).
>>
>> Also, the change in device name (while needed) does not seem
>> to be related to usage of wdt core. Can you may be split
>> that change into a separate patch?
>>
>
> Given all the trouble with it, I think that would be a good idea.
>
> Guenter
>

Ok, I'll split it for convenience.

-- 
Regards,
Ivan Khoronzhuk

  reply	other threads:[~2013-11-27 10:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 14:04 [PATCH v3 0/6] Update Davinci watchdog driver Ivan Khoronzhuk
2013-11-25 14:04 ` [PATCH v3 1/6] watchdog: davinci: change driver to use WDT core Ivan Khoronzhuk
2013-11-25 14:16   ` Santosh Shilimkar
2013-11-25 14:56     ` ivan.khoronzhuk
2013-11-26 11:09   ` Grygorii Strashko
     [not found]     ` <52948184.50604-l0cyMroinI0@public.gmane.org>
2013-11-26 12:10       ` Guenter Roeck
2013-11-26 12:30         ` Grygorii Strashko
     [not found]   ` <1385388285-10553-2-git-send-email-ivan.khoronzhuk-l0cyMroinI0@public.gmane.org>
2013-11-27  4:31     ` Sekhar Nori
     [not found]       ` <5295758C.2030907-l0cyMroinI0@public.gmane.org>
2013-11-27  7:04         ` Guenter Roeck
2013-11-27 10:03           ` ivan.khoronzhuk [this message]
2013-11-25 14:04 ` [PATCH v3 2/6] watchdog: davinci: use davinci_wdt_device structure to hold device data Ivan Khoronzhuk
2013-11-25 14:04 ` [PATCH v3 3/6] watchdog: davinci: add GET_TIMELEFT option support Ivan Khoronzhuk
2013-11-25 14:04 ` [PATCH v3 4/6] watchdog: davinci: add "timeout-sec" property Ivan Khoronzhuk
2013-11-25 14:48 ` [PATCH v3 5/6] watchdog: davinci: reuse driver for keystone arch Ivan Khoronzhuk
2013-11-25 14:54 ` [PATCH v3 6/6] arm: dts: keystone: add watchdog entry Ivan Khoronzhuk
     [not found] ` <1385388285-10553-1-git-send-email-ivan.khoronzhuk-l0cyMroinI0@public.gmane.org>
2013-11-26 19:40   ` [PATCH v3 0/6] Update Davinci watchdog driver Grygorii Strashko

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=5295C355.6000604@ti.com \
    --to=ivan.khoronzhuk@ti.com \
    --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=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).