From: Guenter Roeck <linux@roeck-us.net>
To: Josh Cartwright <joshc@codeaurora.org>
Cc: Wim Van Sebroeck <wim@iguana.be>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-watchdog@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Kumar Gala <galak@codeaurora.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] watchdog: qcom: add support for KPSS WDT
Date: Fri, 19 Sep 2014 09:56:31 -0700 [thread overview]
Message-ID: <20140919165631.GA32457@roeck-us.net> (raw)
In-Reply-To: <20140919162550.GI3749@joshc.qualcomm.com>
On Fri, Sep 19, 2014 at 11:25:50AM -0500, Josh Cartwright wrote:
> On Thu, Sep 18, 2014 at 08:41:43PM -0700, Guenter Roeck wrote:
> > On 09/18/2014 08:24 PM, Josh Cartwright wrote:
> > >On Thu, Sep 18, 2014 at 07:41:17PM -0700, Guenter Roeck wrote:
> > >>On 09/18/2014 03:26 PM, Josh Cartwright wrote:
> > >>>Add a driver for the watchdog timer block found in the Krait Processor
> > >>>Subsystem (KPSS) on the MSM8960, APQ8064, and IPQ8064.
> > >>>
> > >>>Signed-off-by: Josh Cartwright <joshc@codeaurora.org>
> > >>
> > >>Hi Josh,
> > >>
> > >>comments inline.
> > >
> > >Thanks for taking a look!
> > >
> [..]
> > >>>+ watchdog_init_timeout(&wdt->wdd, 0, &pdev->dev);
> > >>
> > >>That leaves you with no default timeout if timeout-sec is not set in devicetree,
> > >>which if I understand the code correctly might result in an immediate reset.
> > >>Is this really what you want to happen ?
> > >
> > >I think I'd like to handle timeout-sec being unspecified as an error at
> > >probe. If someone explicitly sets timeout-sec = <0>, then they get what
> > >they ask for. I'll take another look to see how to make this happen.
> > >
> >
> > Hmm.. kind of unusual. Usual would be to initialize the timeout together
> > with min_timeout / max_timeout above and only force the user to specify
> > a value if the default timeout is not desirable. You don't really gain
> > anything by making timeout-sec mandatory.
>
> Making timeout-sec mandatory makes it so I don't have to decide what a
> "sane default" is. :)
>
Bad excuse ;-). You just force others to make the decision for you.
> It's even less clear about what a sane default is looking at the other
> watchdog drivers. From the drivers I looked at, it ranges any where
> from 30s to 2mins. Am I just to choose? Why do these even differ
> between all of the drivers?
>
Sanity is defined as the majority opinion, as expressed quite nicely in
"Everyone is insane but me".
Just pick something in between. If you don't want to make a decision, pick
30 seconds and blame it on me.
Maybe someone at some point finds a common ground. Until then it is per driver.
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 1/3] watchdog: qcom: add support for KPSS WDT
Date: Fri, 19 Sep 2014 09:56:31 -0700 [thread overview]
Message-ID: <20140919165631.GA32457@roeck-us.net> (raw)
In-Reply-To: <20140919162550.GI3749@joshc.qualcomm.com>
On Fri, Sep 19, 2014 at 11:25:50AM -0500, Josh Cartwright wrote:
> On Thu, Sep 18, 2014 at 08:41:43PM -0700, Guenter Roeck wrote:
> > On 09/18/2014 08:24 PM, Josh Cartwright wrote:
> > >On Thu, Sep 18, 2014 at 07:41:17PM -0700, Guenter Roeck wrote:
> > >>On 09/18/2014 03:26 PM, Josh Cartwright wrote:
> > >>>Add a driver for the watchdog timer block found in the Krait Processor
> > >>>Subsystem (KPSS) on the MSM8960, APQ8064, and IPQ8064.
> > >>>
> > >>>Signed-off-by: Josh Cartwright <joshc@codeaurora.org>
> > >>
> > >>Hi Josh,
> > >>
> > >>comments inline.
> > >
> > >Thanks for taking a look!
> > >
> [..]
> > >>>+ watchdog_init_timeout(&wdt->wdd, 0, &pdev->dev);
> > >>
> > >>That leaves you with no default timeout if timeout-sec is not set in devicetree,
> > >>which if I understand the code correctly might result in an immediate reset.
> > >>Is this really what you want to happen ?
> > >
> > >I think I'd like to handle timeout-sec being unspecified as an error at
> > >probe. If someone explicitly sets timeout-sec = <0>, then they get what
> > >they ask for. I'll take another look to see how to make this happen.
> > >
> >
> > Hmm.. kind of unusual. Usual would be to initialize the timeout together
> > with min_timeout / max_timeout above and only force the user to specify
> > a value if the default timeout is not desirable. You don't really gain
> > anything by making timeout-sec mandatory.
>
> Making timeout-sec mandatory makes it so I don't have to decide what a
> "sane default" is. :)
>
Bad excuse ;-). You just force others to make the decision for you.
> It's even less clear about what a sane default is looking at the other
> watchdog drivers. From the drivers I looked at, it ranges any where
> from 30s to 2mins. Am I just to choose? Why do these even differ
> between all of the drivers?
>
Sanity is defined as the majority opinion, as expressed quite nicely in
"Everyone is insane but me".
Just pick something in between. If you don't want to make a decision, pick
30 seconds and blame it on me.
Maybe someone at some point finds a common ground. Until then it is per driver.
Thanks,
Guenter
next prev parent reply other threads:[~2014-09-19 16:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 22:26 [PATCH 0/3] watchdog: add support for QCOM WDT Josh Cartwright
2014-09-18 22:26 ` Josh Cartwright
2014-09-18 22:26 ` [PATCH 1/3] watchdog: qcom: add support for KPSS WDT Josh Cartwright
2014-09-18 22:26 ` Josh Cartwright
[not found] ` <32d17907ad1dfdcafe4e76f33adc2ff22631cd28.1411078425.git.joshc-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-09-19 2:41 ` Guenter Roeck
2014-09-19 2:41 ` Guenter Roeck
2014-09-19 2:41 ` Guenter Roeck
2014-09-19 3:24 ` Josh Cartwright
2014-09-19 3:24 ` Josh Cartwright
2014-09-19 3:41 ` Guenter Roeck
2014-09-19 3:41 ` Guenter Roeck
2014-09-19 16:25 ` Josh Cartwright
2014-09-19 16:25 ` Josh Cartwright
2014-09-19 16:56 ` Guenter Roeck [this message]
2014-09-19 16:56 ` Guenter Roeck
2014-09-18 22:27 ` [PATCH 2/3] watchdog: qcom: document device tree bindings Josh Cartwright
2014-09-18 22:27 ` Josh Cartwright
2014-09-18 22:27 ` [PATCH 3/3] watchdog: qcom: register a restart notifier Josh Cartwright
2014-09-18 22:27 ` Josh Cartwright
2014-09-19 2:47 ` Guenter Roeck
2014-09-19 2:47 ` Guenter Roeck
2014-09-19 3:32 ` Josh Cartwright
2014-09-19 3:32 ` Josh Cartwright
2014-09-19 4:03 ` Guenter Roeck
2014-09-19 4:03 ` Guenter Roeck
2014-09-19 16:29 ` Josh Cartwright
2014-09-19 16:29 ` Josh Cartwright
2014-09-19 12:47 ` Pramod Gurav
2014-09-19 12:47 ` Pramod Gurav
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=20140919165631.GA32457@roeck-us.net \
--to=linux@roeck-us.net \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=joshc@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=robh+dt@kernel.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.