From: Stefan Agner <stefan@agner.ch>
To: Marcel Ziswiler <marcel@ziswiler.com>
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, 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: [PATCH 5/5] mfd: rn5t618: register restart handler
Date: Mon, 06 Jun 2016 10:19:42 -0700 [thread overview]
Message-ID: <534fc51778d2bea235ae465e1a40b018@agner.ch> (raw)
In-Reply-To: <56D9496A-2927-4D23-B8E2-A1A06F03A654@ziswiler.com>
On 2016-06-06 06:25, Marcel Ziswiler wrote:
> On June 5, 2016 2:17:49 AM GMT+02:00, Stefan Agner <stefan@agner.ch> wrote:
>>Use the PMIC's repower capability for reboots. Register a restart
>>handler with use a default priority of 128.
>
> Apart from that last sentence above which is not clear to me the whole
> series looks fine to me.
Check the kernel docs of the register_restart_handler:
http://lxr.free-electrons.com/source/kernel/reboot.c#L113
I am actually not sure anymore whether 128 is really a good choice. With
that, in the Colibri case, the restart handler would have the same
priority as the i.MX watchdog has (imx2_wdt.c), but the PMIC's restart
capabilities are clearly superior (as it resets all peripherals on the
module). In fact, using the watchdog to restart the system seems to hang
for some reason...
Maybe 192?
--
Stefan
>
> Reviewed-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
>
>>Signed-off-by: Stefan Agner <stefan@agner.ch>
>>---
>> 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 d9b4d40..d9bd61c 100644
>>--- a/drivers/mfd/rn5t618.c
>>+++ b/drivers/mfd/rn5t618.c
>>@@ -12,13 +12,17 @@
>> * 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>
>>
>>+#include <asm/system_misc.h>
>>+
>> static const struct mfd_cell rn5t618_cells[] = {
>> { .name = "rn5t618-regulator" },
>> { .name = "rn5t618-wdt" },
>>@@ -50,17 +54,34 @@ 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);
>> /* start power-off sequence */
>> regmap_update_bits(rn5t618_pm_power_off->regmap, RN5T618_SLPCNT,
>> RN5T618_SLPCNT_SWPWROFF, RN5T618_SLPCNT_SWPWROFF);
>> }
>>
>>+static void rn5t618_power_off(void)
>>+{
>>+ rn5t618_trigger_poweroff_sequence(false);
>>+}
>>+
>>+static int rn5t618_restart(struct notifier_block *this,
>>+ unsigned long mode, void *cmd)
>>+{
>>+ rn5t618_trigger_poweroff_sequence(true);
>>+
>>+ mdelay(10);
>>+
>>+ return NOTIFY_DONE;
>>+}
>>+
>>+
>> static const struct of_device_id rn5t618_of_match[] = {
>> { .compatible = "ricoh,rn5t567", .data = (void *)RN5T567 },
>> { .compatible = "ricoh,rn5t618", .data = (void *)RN5T618 },
>>@@ -103,13 +124,22 @@ static int rn5t618_i2c_probe(struct i2c_client
>>*i2c,
>> return ret;
>> }
>>
>>+ rn5t618_pm_power_off = priv;
>> if (of_device_is_system_power_controller(i2c->dev.of_node)) {
>>- if (!pm_power_off) {
>>- rn5t618_pm_power_off = priv;
>>+ if (!pm_power_off)
>> pm_power_off = rn5t618_power_off;
>>- } else {
>>+ else
>> dev_err(&i2c->dev, "Failed to set poweroff capability, already
>>defined\n");
>>- }
>>+ }
>>+
>>+ rn5t618_restart_handler.notifier_call = rn5t618_restart;
>>+ rn5t618_restart_handler.priority = 128;
>>+
>>+ ret = register_restart_handler(&rn5t618_restart_handler);
>>+ if (ret) {
>>+ dev_err(&i2c->dev, "%s: cannot register restart handler, %d\n",
>>+ __func__, ret);
>>+ return ret;
>> }
>>
>> return 0;
prev parent reply other threads:[~2016-06-06 17:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-05 0:17 [PATCH 0/5] regulator: add Ricoh RN5T567 PMIC support Stefan Agner
[not found] ` <20160605001749.4062-1-stefan-XLVq0VzYD2Y@public.gmane.org>
2016-06-05 0:17 ` [PATCH 1/5] ARM: dts: meson: minix-neo-x8: define PMIC as power controller Stefan Agner
2016-06-29 18:05 ` Applied "ARM: dts: meson: minix-neo-x8: define PMIC as power controller" to the regulator tree Mark Brown
2016-06-05 0:17 ` [PATCH 2/5] mfd: add Ricoh RN5T567 PMIC support Stefan Agner
2016-06-05 0:17 ` [PATCH 3/5] regulator: rn5t618: Add " Stefan Agner
2016-06-29 18:05 ` Applied "regulator: rn5t618: Add RN5T567 PMIC support" to the regulator tree Mark Brown
2016-06-05 0:17 ` [PATCH 3/5] regulator: rn5t618: add RN5T567 PMIC support Stefan Agner
2016-06-06 17:35 ` Mark Brown
2016-06-06 17:47 ` Stefan Agner
2016-06-06 18:04 ` Mark Brown
2016-06-05 0:17 ` [PATCH 4/5] mfd: rn5t618: register power off callback optionally Stefan Agner
2016-06-05 0:17 ` [PATCH 5/5] mfd: rn5t618: register restart handler Stefan Agner
[not found] ` <20160605001749.4062-7-stefan-XLVq0VzYD2Y@public.gmane.org>
2016-06-05 1:24 ` kbuild test robot
2016-06-05 2:52 ` Stefan Agner
2016-06-06 13:25 ` Marcel Ziswiler
2016-06-06 17:19 ` Stefan Agner [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=534fc51778d2bea235ae465e1a40b018@agner.ch \
--to=stefan@agner.ch \
--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 \
/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).