[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140923175556.GG868@joshc.qualcomm.com>
Date: Tue, 23 Sep 2014 12:55:56 -0500
From: Josh Cartwright <joshc@...eaurora.org>
To: Kumar Gala <galak@...eaurora.org>
Cc: Pramod Gurav <pramod.gurav@...rtplayin.com>,
linux-kernel@...r.kernel.org, Guenter Roeck <linux@...ck-us.net>,
Josh Cartwright <joshc@...eaurora.org>,
Sebastian Reichel <sre@...nel.org>,
Dmitry Eremin-Solenikov <dbaryshkov@...il.com>,
David Woodhouse <dwmw2@...radead.org>,
Stephen Boyd <sboyd@...eaurora.org>, linux-pm@...r.kernel.org,
linux-arm-msm <linux-arm-msm@...r.kernel.org>
Subject: Re: [PATCH v3] power: reset: use restart_notifier mechanism for
msm-poweroff
On Tue, Sep 23, 2014 at 12:48:42PM -0500, Kumar Gala wrote:
>
> On Sep 23, 2014, at 1:28 AM, Pramod Gurav <pramod.gurav@...rtplayin.com> wrote:
>
> > +linux-arm-msm
> > On Tuesday 23 September 2014 11:38 AM, Pramod Gurav wrote:
> >> This change replaces use of arm_pm_restart with recently introduced
> >> reset mechanism in Linux kernel called restart_notifier.
>
> Can you update the commit message to include details about the priority level we are setting it to.
>
> Probably something like Josh had:
>
> Choose priority 128, as according to documentation, this mechanism "is
> sufficient to restart the entire system?.
>
> Hmm, what happens if we have ps_hold restart and msm-poweroff enabled.
> Which one should have priority?
I would hope we would avoid a situation where both this driver is
probed, and the pinctrl-msm driver has registered a restart handler?
That is, we wouldn't ever mix the pinctrl-msm ps_hold mechanism (for
MSM8660/MSM8960/APQ8064, etc) and msm-poweroff (APQ8074 and later). Is
this a case you're worried about?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists