All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-watchdog@vger.kernel.org, Wim Van Sebroeck <wim@iguana.be>,
	support.opensource@diasemi.com, kernel@pengutronix.de
Subject: Re: [PATCH 1/2] watchdog: da9063: Ping watchdog only during allowed time window
Date: Fri, 07 Aug 2015 10:33:44 -0700	[thread overview]
Message-ID: <55C4EBF8.5060004@roeck-us.net> (raw)
In-Reply-To: <1438967295.3638.41.camel@pengutronix.de>

Hi Philipp,

On 08/07/2015 10:08 AM, Philipp Zabel wrote:
> Hi Guenter,
>
> Am Freitag, den 07.08.2015, 06:36 -0700 schrieb Guenter Roeck:
>> On 08/06/2015 09:36 AM, Philipp Zabel wrote:
>>> There is a cooldown period after watchdog timer setup, and also after each
>>> watchdog ping. If a ping is issued too early, the watchdog triggers the
>>> watchdog error condition and causes a system reset.
>>>
>>> The 256 ms period length is a best guess based on the same value being used
>>> for the DA9053 predecessor PMIC and experiments that have shown 200 ms are
>>> not enough to avoid the error.
>>>
>>> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
>>
>> Hi Philipp,
>>
>> instead of using this quite complex approach, would it be possible to use the
>> same approach as the da9062 driver ?
>>
>> I understand the downside, which is that the caller may end up sleeping,
>> but this should not happen too often.
>
> Depending on the userspace this can happen quite a lot ...
>
Your call, ultimately. I don't want to spend time reviewing the changes
as is, given they are quite substantial and will ultimately go away,
so we'll just have to wait for someone else to spend that time.

Thanks,
Guenter

>>   Also, I plan to move the enforcement
>> of a minimal time between heartbeats into the infrastructure, so this would
>> not least forever.
>
> ... but certainly taking care of this in the framework is better than
> doing it in the drivers.
>
> regards
> Philipp
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


      reply	other threads:[~2015-08-07 17:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06 16:36 [PATCH 1/2] watchdog: da9063: Ping watchdog only during allowed time window Philipp Zabel
2015-08-06 16:36 ` [PATCH 2/2] watchdog: da9063: Disable and wait before changing timeout Philipp Zabel
2015-08-07 13:40   ` Guenter Roeck
2015-08-07 17:09     ` Philipp Zabel
2015-08-07 10:13 ` [PATCH 1/2] watchdog: da9063: Ping watchdog only during allowed time window Opensource [Adam Thomson]
2015-08-07 10:17   ` Philipp Zabel
2015-08-24 13:39     ` Opensource [Steve Twiss]
2015-08-07 13:36 ` Guenter Roeck
2015-08-07 17:08   ` Philipp Zabel
2015-08-07 17:33     ` Guenter Roeck [this message]

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=55C4EBF8.5060004@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=kernel@pengutronix.de \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=support.opensource@diasemi.com \
    --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.