From: Josh Cartwright <joshc@ni.com>
To: Michal Simek <michal.simek@xilinx.com>,
S?ren Brinkmann <soren.brinkmann@xilinx.com>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] ARM: zynq: use restart_handler mechanism for slcr reset
Date: Wed, 11 Mar 2015 10:41:50 -0500 [thread overview]
Message-ID: <20150311154150.GA3851@jcartwri.amer.corp.natinst.com> (raw)
In-Reply-To: <1425049769-24929-1-git-send-email-joshc@ni.com>
On Fri, Feb 27, 2015 at 09:09:29AM -0600, Josh Cartwright wrote:
> By making use of the restart_handler chain mechanism, the SLCR-based
> reset mechanism can be prioritized amongst other mechanisms available on
> a particular board.
Have either of you had a chance to look at this yet? On our boards we
have a chip external to the SoC that manages power sequencing (and a
hodgepodge of other board-level things), and we would like it to be
prioritized above the SLCR reset mechanism.
Previously we've just hacked up mach-zynq/common.c to not register a
restart handler, and set arm_pm_restart ourselves, but that doesn't seem
appropriate now that the restart chain exists.
Thanks,
Josh
next prev parent reply other threads:[~2015-03-11 15:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 15:09 Josh Cartwright
2015-03-11 15:41 ` Josh Cartwright [this message]
2015-03-19 10:44 ` Michal Simek
2015-03-19 12:44 ` Josh Cartwright
2015-03-19 13:19 ` Michal Simek
2015-03-19 13:33 ` [PATCH v3 1/2] " Josh Cartwright
2015-03-19 13:33 ` [PATCH 2/2] ARM: zynq: drop use of slcr_unlock in zynq_slcr_system_restart Josh Cartwright
2015-03-19 13:49 ` Josh Cartwright
2015-03-19 14:01 ` [PATCH v3 1/2] ARM: zynq: use restart_handler mechanism for slcr reset Michal Simek
2015-03-19 14:22 ` Josh Cartwright
2015-03-19 14:24 ` [PATCH v4] " Josh Cartwright
2015-03-20 7:48 ` Michal Simek
2015-03-19 13:37 ` [PATCH v2] " Josh Cartwright
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=20150311154150.GA3851@jcartwri.amer.corp.natinst.com \
--to=joshc@ni.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=soren.brinkmann@xilinx.com \
/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
all inboxes | Powered by JetHome®