devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Stefan Agner <stefan@agner.ch>
Cc: lee.jones@linaro.org, lgirdwood@gmail.com, broonie@kernel.org,
	khilman@baylibre.com, carlo@caione.org, b.galvani@gmail.com,
	max.oss.09@gmail.com, marcel@ziswiler.com, linux@armlinux.org.uk,
	galak@codeaurora.org, ijc+devicetree@hellion.org.uk,
	mark.rutland@arm.com, pawel.moll@arm.com, robh+dt@kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-amlogic@lists.infradead.org
Subject: Re: [v3,5/5] mfd: rn5t618: register restart handler
Date: Sun, 26 Jun 2016 08:13:18 -0700	[thread overview]
Message-ID: <20160626151318.GA15869@roeck-us.net> (raw)
In-Reply-To: <20160626011515.4428-6-stefan@agner.ch>

On Sat, Jun 25, 2016 at 06:15:15PM -0700, Stefan Agner wrote:
> Use the PMIC's repower capability for reboots. Register a restart
> handler and use a slightly elevated priority of 192 since the PMIC
> has suprior reset capability (causing a system wide reset).
> 
> Signed-off-by: Stefan Agner <stefan@agner.ch>
> Reviewed-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
> ---
>  drivers/mfd/rn5t618.c | 42 ++++++++++++++++++++++++++++++++++++------
>  1 file changed, 36 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/mfd/rn5t618.c b/drivers/mfd/rn5t618.c
> index 1831740..14f3b5f 100644
> --- a/drivers/mfd/rn5t618.c
> +++ b/drivers/mfd/rn5t618.c
> @@ -12,11 +12,13 @@
>   * along with this program. If not, see <http://www.gnu.org/licenses/>.
>   */
>  
> +#include <linux/delay.h>
>  #include <linux/i2c.h>
>  #include <linux/mfd/core.h>
>  #include <linux/mfd/rn5t618.h>
>  #include <linux/module.h>
>  #include <linux/of_device.h>
> +#include <linux/reboot.h>
>  #include <linux/regmap.h>
>  
>  static const struct mfd_cell rn5t618_cells[] = {
> @@ -50,17 +52,37 @@ static const struct regmap_config rn5t618_regmap_config = {
>  };
>  
>  static struct rn5t618 *rn5t618_pm_power_off;
> +static struct notifier_block rn5t618_restart_handler;
>  
> -static void rn5t618_power_off(void)
> +static void rn5t618_trigger_poweroff_sequence(bool repower)
>  {
>  	/* disable automatic repower-on */
>  	regmap_update_bits(rn5t618_pm_power_off->regmap, RN5T618_REPCNT,
> -			   RN5T618_REPCNT_REPWRON, 0);
> +			   RN5T618_REPCNT_REPWRON, repower);

This only works because RN5T618_REPCNT_REPWRON happens to be BIT(0).
Better would be

			RN5T618_REPCNT_REPWRON,
			repower ?  RN5T618_REPCNT_REPWRON : 0

Guenter

      reply	other threads:[~2016-06-26 15:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-26  1:15 [PATCH v3 0/5] regulator: add Ricoh RN5T567 PMIC support Stefan Agner
2016-06-26  1:15 ` [PATCH v3 1/5] ARM: dts: meson: minix-neo-x8: define PMIC as power controller Stefan Agner
     [not found]   ` <20160626011515.4428-2-stefan-XLVq0VzYD2Y@public.gmane.org>
2016-06-27  8:45     ` Carlo Caione
2016-06-26  1:15 ` [PATCH v3 2/5] mfd: add Ricoh RN5T567 PMIC support Stefan Agner
2016-06-29 18:05   ` Applied "mfd: rn5t618: Add Ricoh RN5T567 PMIC support" to the regulator tree Mark Brown
2016-06-30  7:43     ` Lee Jones
2016-06-26  1:15 ` [PATCH v3 3/5] regulator: rn5t618: add RN5T567 PMIC support Stefan Agner
2016-06-26  1:15 ` [PATCH v3 4/5] mfd: rn5t618: register power off callback optionally Stefan Agner
     [not found]   ` <20160626011515.4428-5-stefan-XLVq0VzYD2Y@public.gmane.org>
2016-06-29 18:05     ` Applied "mfd: rn5t618: Register power off callback optionally" to the regulator tree Mark Brown
2016-06-26  1:15 ` [PATCH v3 5/5] mfd: rn5t618: register restart handler Stefan Agner
2016-06-26 15:13   ` Guenter Roeck [this message]

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=20160626151318.GA15869@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=b.galvani@gmail.com \
    --cc=broonie@kernel.org \
    --cc=carlo@caione.org \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=khilman@baylibre.com \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=marcel@ziswiler.com \
    --cc=mark.rutland@arm.com \
    --cc=max.oss.09@gmail.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=stefan@agner.ch \
    /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).