From: Guenter Roeck <linux@roeck-us.net>
To: Pankaj Dubey <pankaj.dubey@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, kgene.kim@samsung.com,
tomasz.figa@gmail.com, linux@arm.linux.org.uk,
thomas.ab@samsung.com, vikas.sajjan@samsung.com,
naushad@samsung.com
Subject: Re: [PATCH v3 0/2] Handle reboot for Exynos SoC via restart_handler
Date: Tue, 7 Oct 2014 09:51:57 -0700 [thread overview]
Message-ID: <20141007165157.GH28835@roeck-us.net> (raw)
In-Reply-To: <1412668401-21837-1-git-send-email-pankaj.dubey@samsung.com>
On Tue, Oct 07, 2014 at 01:23:19PM +0530, Pankaj Dubey wrote:
> This patch removes restart hook from machine_desc of Exynos, and moves
> respective code into reboot_notifiers.
Nitpick:
s/reboot_notifiers/restart_notifiers/
Guenter
> Exynos5440 handles reboot via clock register so let's register a
> restart_handler in Exynos5440 clock driver.
> For rest Exynos SoC, reboot is handled via PMU SWRESET register so
> let's register a restart_handler in PMU driver for handling this.
>
> This patch is inspired and dependent on following patch series[1] from
> Geunter Roeck.
>
> Also this patch is dependent on PMU platform driver patch [2] by me, and
> has been prepared on top of it.
>
> [1]: kernel: Add support for kernel restart handler call chain
> https://lkml.org/lkml/2014/8/19/652
>
> [2]: ARM: Exynos: Convert PMU implementation into a platform driver
> https://lkml.org/lkml/2014/10/6/89
>
> I have tested reboot functionality on Exynos3250 based board, on
> kgene/for-next as well as linux-next's next-20140925 tag.
>
> Patch v2 and related discussion can be found here
> http://www.spinics.net/lists/linux-samsung-soc/msg37457.html
>
> Changes since v2:
> - Used register_restart_handler instead of register_reboot_notifier.
> - Updated notifier names and commit message accordingly.
>
> Changes since v1:
> - Addressed review comments from Tomasz Figa. Removed usage of
> local variables where ever unnecessary.
> - Make reg_base as global in clk-exynos5440.c file, to avoid
> iomapping it again in reboot_notifier handler.
>
> Pankaj Dubey (2):
> clk: samsung: exynos5440: move restart code into clock driver
> ARM: EXYNOS: PMU: move restart code into pmu driver
>
> arch/arm/mach-exynos/common.h | 1 -
> arch/arm/mach-exynos/exynos.c | 23 -----------------------
> arch/arm/mach-exynos/pmu.c | 24 ++++++++++++++++++++++++
> drivers/clk/samsung/clk-exynos5440.c | 29 ++++++++++++++++++++++++++++-
> 4 files changed, 52 insertions(+), 25 deletions(-)
>
> --
> 1.7.9.5
>
next prev parent reply other threads:[~2014-10-07 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 7:53 [PATCH v3 0/2] Handle reboot for Exynos SoC via restart_handler Pankaj Dubey
2014-10-07 7:53 ` [PATCH v3 1/2] clk: samsung: exynos5440: move restart code into clock driver Pankaj Dubey
2014-10-07 7:53 ` [PATCH v3 2/2] ARM: EXYNOS: PMU: move restart code into pmu driver Pankaj Dubey
2014-10-07 16:51 ` Guenter Roeck [this message]
2014-11-10 11:28 ` [PATCH v3 0/2] Handle reboot for Exynos SoC via restart_handler Pankaj Dubey
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=20141007165157.GH28835@roeck-us.net \
--to=linux@roeck-us.net \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=naushad@samsung.com \
--cc=pankaj.dubey@samsung.com \
--cc=thomas.ab@samsung.com \
--cc=tomasz.figa@gmail.com \
--cc=vikas.sajjan@samsung.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