linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@codeaurora.org>
To: Al Stone <al.stone@linaro.org>,
	linux-watchdog@vger.kernel.org,
	Ashwin Chaugule <ashwin.chaugule@linaro.org>,
	Vipul Gandhi <vgandhi@codeaurora.org>, Fu Wei <fu.wei@linaro.org>,
	Wim Van Sebroeck <wim@iguana.be>,
	Hanjun Guo <hanjun.guo@linaro.org>, Arnd Bergmann <arnd@arndb.de>,
	Guenter Roeck <linux@roeck-us.net>,
	Graeme Gregory <graeme.gregory@linaro.org>,
	linaro-acpi@lists.linaro.org
Subject: Re: [PATCH] [v4] watchdog: introduce the ARM64 SBSA watchdog driver
Date: Tue, 26 May 2015 15:49:22 -0500	[thread overview]
Message-ID: <5564DC52.6010204@codeaurora.org> (raw)
In-Reply-To: <5564D9D6.9050309@linaro.org>

On 05/26/2015 03:38 PM, Al Stone wrote:
> Ah.  I have to think on that a bit; it sounds reasonable.  I guess I was
> wondering about how the DT usage would work vs the ACPI usage and trying
> to make them very similar in my head.  That may just give me a headache,
> however.

I haven't tested the code myself, but the driver uses named properties 
to get the base address for the device, so as long as the device tree 
has those property names, it should work automatically.

-- 
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.

  reply	other threads:[~2015-05-26 20:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22 22:52 [PATCH] [v4] watchdog: introduce the ARM64 SBSA watchdog driver Timur Tabi
2015-05-26 17:11 ` Al Stone
2015-05-26 17:58   ` Timur Tabi
2015-05-26 20:38     ` Al Stone
2015-05-26 20:49       ` Timur Tabi [this message]
2015-05-27 21:47   ` [Linaro-acpi] " administrator
2015-06-10 14:55     ` Fu Wei

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=5564DC52.6010204@codeaurora.org \
    --to=timur@codeaurora.org \
    --cc=al.stone@linaro.org \
    --cc=arnd@arndb.de \
    --cc=ashwin.chaugule@linaro.org \
    --cc=fu.wei@linaro.org \
    --cc=graeme.gregory@linaro.org \
    --cc=hanjun.guo@linaro.org \
    --cc=linaro-acpi@lists.linaro.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=vgandhi@codeaurora.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;
as well as URLs for NNTP newsgroup(s).