From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Watchdog on Armada 375 SoC
Date: Wed, 26 Feb 2014 13:36:33 -0700 [thread overview]
Message-ID: <20140226203633.GA24656@obsidianresearch.com> (raw)
In-Reply-To: <1393419047-10071-1-git-send-email-ezequiel.garcia@free-electrons.com>
On Wed, Feb 26, 2014 at 09:50:45AM -0300, Ezequiel Garcia wrote:
> Here we found both the above RSTOUT:
>
> 1. It has the same dedicated register as A370/XP (0x20704)
> 2. Also has a bit in the shared RSTOUT register (0x18254)
Unless you know otherwise I think the same risk exists, RSTOUT could
be (or become) internally asserted when you unmask the bit in the
control register that drives the pin, which says the watchdog driver
should control to it.
> A possible solution is to extend the reg property in the watchdog
> devicetree and allow for a new optional pair of cells to complete
> the specification of the RSTOUT.
>
> watchdog-timer at 20300 {
> compatible = "marvell,orion-wdt";
> reg = <0x20300 0x28
> {shared RSOUT} 0x4
> 0x0 0x0>;
> };
I wouldn't have the 0x0, if you want to go this way, just make the
375 compatible string require a 3 entry reg.
Jason
next prev parent reply other threads:[~2014-02-26 20:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 12:50 [PATCH 0/2] Watchdog on Armada 375 SoC Ezequiel Garcia
2014-02-26 12:50 ` [PATCH 1/2] ARM: mvebu: Enable Armada 375 watchdog in the devicetree Ezequiel Garcia
2014-02-26 12:50 ` [PATCH 2/2] ARM: mvebu: system-controller: Add A375 initialization Ezequiel Garcia
2014-02-26 20:36 ` Jason Gunthorpe [this message]
2014-02-28 15:09 ` [PATCH 0/2] Watchdog on Armada 375 SoC Ezequiel Garcia
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=20140226203633.GA24656@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).