From: Guenter Roeck <linux@roeck-us.net>
To: "Heiko Stübner" <heiko@sntech.de>,
"Sebastian Reichel" <sre@kernel.org>,
"Dmitry Eremin-Solenikov" <dbaryshkov@gmail.com>,
"David Woodhouse" <dwmw2@infradead.org>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] power: reset: gpio-restart: increase priority slightly
Date: Tue, 02 Jun 2015 08:25:50 -0700 [thread overview]
Message-ID: <556DCAFE.5050304@roeck-us.net> (raw)
In-Reply-To: <4893951.aWdOo6F7tl@diego>
On 06/02/2015 07:48 AM, Heiko Stübner wrote:
> gpio-restart uses a priority of 128 and currently most soc-level restart
> mechanisms use the same - with some exceptions even using 192.
> But while the soc-level restarts are provided by the soc itself,
> gpio-restarts will most of the time be board-specfic and be used
> when some special board condition makes the soc-level restart
> only a second choice.
>
> The problem at hand manifested itself on the rk3288-veyron devices.
> While the soc-level restart can sucessfully restart all other rockchip
> boards I have, the veyron devices use an external restart mechanism that
> seems to not only reset the soc but also some external needed components.
>
> With both restart handlers having priority 128 in my tests the soc-specific
> variant took precedent in all cases. While it could restart the soc
> sucessfully in all cases, firmware then got an issue when talking to an
> external component, resulting in the device being put into recovery mode.
>
> So, give the board-specific restart handler a slight push and move it
> to priority 129 to make it more important than the generic soc-specific
> restart-handler.
>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Makes sense.
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
next prev parent reply other threads:[~2015-06-02 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 14:48 [PATCH] power: reset: gpio-restart: increase priority slightly Heiko Stübner
2015-06-02 15:25 ` Guenter Roeck [this message]
2015-06-02 19:28 ` Sebastian Reichel
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=556DCAFE.5050304@roeck-us.net \
--to=linux@roeck-us.net \
--cc=dbaryshkov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sre@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.