From: Jamie Iles <jamie@jamieiles.com>
To: Dinh Nguyen <dinh.linux@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Guenter Roeck <linux@roeck-us.net>,
"dinguyen@altera.com" <dinguyen@altera.com>,
Jamie Iles <jamie@jamieiles.com>,
Viresh Kumar <viresh.linux@gmail.com>,
Wim Van Sebroeck <wim@iguana.be>, Pavel Machek <pavel@denx.de>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Pawel Moll <Pawel.Moll@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Ian Campbell <ian.campbell@citrix.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>
Subject: Re: [RESEND PATCHv2] watchdog: dw: Enable OF support for DW watchdog timer.
Date: Tue, 22 Oct 2013 12:02:42 +0100 [thread overview]
Message-ID: <20131022110242.GA7560@maple> (raw)
In-Reply-To: <52665A1E.5020700@gmail.com>
On Tue, Oct 22, 2013 at 05:57:34AM -0500, Dinh Nguyen wrote:
> On 10/22/13 5:39 AM, Mark Rutland wrote:
> >Does the device have any interrupts, even if they're unused?
> Yes, the device does have an interrupt. Should I add it as an
> optional property?
iirc the interrupt feature is part of the IP configuration so not all
instantiations will have the interrupt, so this should be an optional
property.
Jamie
prev parent reply other threads:[~2013-10-22 11:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 18:44 [RESEND PATCHv2] watchdog: dw: Enable OF support for DW watchdog timer dinguyen
2013-10-02 19:27 ` Guenter Roeck
2013-10-21 11:05 ` Mark Rutland
2013-10-22 0:41 ` Guenter Roeck
2013-10-22 10:39 ` Mark Rutland
2013-10-22 10:57 ` Dinh Nguyen
2013-10-22 11:02 ` Mark Rutland
2013-10-22 11:02 ` Jamie Iles [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=20131022110242.GA7560@maple \
--to=jamie@jamieiles.com \
--cc=Pawel.Moll@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@altera.com \
--cc=dinh.linux@gmail.com \
--cc=ian.campbell@citrix.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=pavel@denx.de \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.org \
--cc=viresh.linux@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).