From: Wim Van Sebroeck <wim@iguana.be>
To: Damien Riegel <damien.riegel@savoirfairelinux.com>
Cc: linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Guenter Roeck <linux@roeck-us.net>,
kernel@savoirfairelinux.com
Subject: Re: [PATCH v8] watchdog: ts4800: add driver for TS-4800 watchdog
Date: Wed, 23 Dec 2015 17:03:29 +0100 [thread overview]
Message-ID: <20151223160329.GA434@spo001.leaseweb.nl> (raw)
In-Reply-To: <20151223154359.GA6265@localhost>
Hi Damien,
> On Tue, Dec 08, 2015 at 11:37:28AM -0500, Damien Riegel wrote:
> > This watchdog is instantiated in a FPGA that is memory mapped. It is
> > made of only one register, called the feed register. Writing to this
> > register will re-arm the watchdog for a given time (and enable it if it
> > was disable). It can be disabled by writing a special value into it.
> >
> > It is part of a syscon block, and the watchdog register offset in this
> > block varies from board to board. This offset is passed in the syscon
> > property after the phandle to the syscon node.
> >
> > Signed-off-by: Damien Riegel <damien.riegel@savoirfairelinux.com>
> > Acked-by: Rob Herring <robh@kernel.org>
> > Reviewed-by: Guenter Roeck <linux@roeck-us.net>
>
> Hi Guenter,
>
>
> You have reviewed this patch but not picked it up in your tree. Shall I
> expect Wim to pick it up directly for the next merge window? The board
> would be quite useless without its watchdog driver.
>
>
> Thanks,
> Damien
It's on my todo list for the next merge window.
Kind regards,
Wim.
next prev parent reply other threads:[~2015-12-23 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 16:37 [PATCH v8] watchdog: ts4800: add driver for TS-4800 watchdog Damien Riegel
2015-12-23 15:43 ` Damien Riegel
2015-12-23 16:03 ` Wim Van Sebroeck [this message]
2015-12-23 16:11 ` Guenter Roeck
2015-12-28 21:41 ` 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=20151223160329.GA434@spo001.leaseweb.nl \
--to=wim@iguana.be \
--cc=damien.riegel@savoirfairelinux.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kernel@savoirfairelinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
/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