From: Guenter Roeck <linux@roeck-us.net>
To: Dirk Eibach <dirk.eibach@gdsys.cc>
Cc: linux-kernel@vger.kernel.org,
Kumar Gala <galak@kernel.crashing.org>,
Wim Van Sebroeck <wim@iguana.be>,
linux-watchdog@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: Make Book E watchdog reset type configurable
Date: Fri, 3 May 2013 06:46:10 -0700 [thread overview]
Message-ID: <20130503134610.GA31037@roeck-us.net> (raw)
In-Reply-To: <7be2cb3417615ff206270a756c6422d6@gdsys.cc>
On Fri, May 03, 2013 at 10:33:13AM +0200, Dirk Eibach wrote:
> Hi Guenter,
>
> >>>>diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> >>>>index e89fc31..6048593 100644
> >>>>--- a/drivers/watchdog/Kconfig
> >>>>+++ b/drivers/watchdog/Kconfig
> >>>>@@ -1172,6 +1172,38 @@ config BOOKE_WDT_DEFAULT_TIMEOUT
> >>>>
> >>>> The value can be overridden by the wdt_period command-line
> >>>>parameter.
> >>>>
> >>>>+choice
> >>>>+ prompt "PowerPC Book-E Watchdog reset type"
> >>>>+ depends on BOOKE_WDT
> >>>>+ default BOOKE_WDT_RESET_CHIP
> >>>>+ help
> >>>>+ Specify what kind of reset will be executed on watchdog
> >>>>timeout.
> >>>>+
> >>>Seems to me it would be much better to make this configurable via
> >>>platform data
> >>>and/or device tree.
> >>
> >>good catch. What do the device-tree gurus think to be a nice
> >>property name?
>
> having a closer look, I realized booke_wdt is not device-tree based
> yet. Migrating it would come close to a rewrite, breaking
> compatibility for all current users. Sorry, this is way beyond the
Really ? I don't think making it a platform driver would be that hard,
or break anything.
> time I have for this project. So I suggest merging the change the
> way it is, as it is clearly an improvement.
>
That will be up to Wim to decide.
Thanks,
Guenter
next prev parent reply other threads:[~2013-05-03 13:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 14:45 [PATCH] powerpc: Make Book E watchdog reset type configurable dirk.eibach
2013-05-02 16:17 ` Guenter Roeck
2013-05-02 19:11 ` Dirk Eibach
2013-05-03 1:17 ` Guenter Roeck
2013-05-03 8:33 ` Dirk Eibach
2013-05-03 13:46 ` Guenter Roeck [this message]
2013-05-03 18:30 ` Dirk Eibach
2013-05-03 20:33 ` Guenter Roeck
2013-05-03 15:59 ` Guenter Roeck
2013-05-26 17:04 ` Wim Van Sebroeck
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=20130503134610.GA31037@roeck-us.net \
--to=linux@roeck-us.net \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dirk.eibach@gdsys.cc \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox