From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1] watchdog: Introduce watchdog driver for Intel Tangier
Date: Tue, 18 Apr 2017 12:30:46 -0400 [thread overview]
Message-ID: <20170418163046.GG19487@bill-the-cat> (raw)
In-Reply-To: <1492527451.24567.74.camel@linux.intel.com>
On Tue, Apr 18, 2017 at 05:57:31PM +0300, Andy Shevchenko wrote:
> On Tue, 2017-04-18 at 16:49 +0200, Lukasz Majewski wrote:
> > Hi Andy,
> >
> > > From: Felipe Balbi <felipe.balbi@linux.intel.com>
> > >
> > > Add watchdog driver for Intel Tangier based platforms.
> > >
> > > Signed-off-by: Vincent Tinelli <vincent.tinelli@intel.com>
> > > Signed-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>
> > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > > ---
> > > common/board_f.c | 1 +
> > > drivers/watchdog/Kconfig | 8 ++++++
> > > drivers/watchdog/Makefile | 1 +
> > > drivers/watchdog/tangier_wdt.c | 63
> > > ++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 73
> > > insertions(+) create mode 100644 drivers/watchdog/tangier_wdt.c
> > >
> > > diff --git a/common/board_f.c b/common/board_f.c
> > > index d9431ee79a..ad1eae98a5 100644
> > > --- a/common/board_f.c
> > > +++ b/common/board_f.c
> > > @@ -91,6 +91,7 @@ static int init_func_watchdog_init(void)
> > > (defined(CONFIG_M68K) || defined(CONFIG_MICROBLAZE) || \
> > > defined(CONFIG_SH) || defined(CONFIG_AT91SAM9_WATCHDOG) ||
> > > \
> > > defined(CONFIG_DESIGNWARE_WATCHDOG) || \
> > > + defined(CONFIG_TANGIER_WATCHDOG) || \
> > > defined(CONFIG_IMX_WATCHDOG))
> >
> > I have stumbled upon similar patch... There should be new Kconfig
> > option created and enabled in required SoCs.
>
> I'm glad to use one if there is one.
> For now I prefer to have it functional.
We have time to get this right. Looking at the code context,
CONFIG_HW_WATCHDOG_ENABLE, and some help text saying that it enables the
hardware watchdog during U-Boot's initialization process would be
enough. Then select that in your next patch and you can leave the rest
of the conversion for later. Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170418/9fe36ea0/attachment.sig>
next prev parent reply other threads:[~2017-04-18 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 13:51 [U-Boot] [PATCH v1] watchdog: Introduce watchdog driver for Intel Tangier Andy Shevchenko
2017-04-18 14:49 ` Lukasz Majewski
2017-04-18 14:57 ` Andy Shevchenko
2017-04-18 16:30 ` Tom Rini [this message]
2017-07-04 19:48 ` Andy Shevchenko
2017-07-04 20:31 ` Tom Rini
2017-07-04 20:41 ` Andy Shevchenko
2017-07-04 21:23 ` lukma
2017-07-04 22:36 ` Andy Shevchenko
2017-07-05 15:59 ` Andy Shevchenko
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=20170418163046.GG19487@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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