From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 02/12] drivers: mfd: Add support for Exynos PMU driver
Date: Tue, 4 Nov 2014 08:24:02 +0000 [thread overview]
Message-ID: <20141104082402.GE17577@x1> (raw)
In-Reply-To: <002601cff7de$0f8db7e0$2ea927a0$@samsung.com>
On Tue, 04 Nov 2014, Pankaj Dubey wrote:
> On Monday, November 03, 2014 8:56 PM, Lee Jones wrote,
> > Subject: Re: [PATCH 02/12] drivers: mfd: Add support for Exynos PMU driver
> >
> > On Mon, 03 Nov 2014, Amit Daniel Kachhap wrote:
> >
> > > From: Pankaj Dubey <pankaj.dubey@samsung.com>
> > >
> > > This patch moves Exynos PMU driver implementation from "arm/mach-exynos"
> > > to "drivers/mfd". This driver is mainly used for setting misc bits of
> > > register from PMU IP of Exynos SoC which will be required to configure
> > > before Suspend/Resume. Currently all these settings are done in
> > > "arch/arm/mach-exynos/pmu.c" but moving ahead for ARM64 based SoC
> > > support, there is a need of DT based implementation of PMU driver.
> > >
> > > This driver uses already existing DT binding information.
> > >
> > > CC: Sangbeom Kim <sbkim73@samsung.com>
> > > CC: Samuel Ortiz <sameo@linux.intel.com>
> > > CC: Lee Jones <lee.jones@linaro.org>
> > > Signed-off-by: Pankaj Dubey <pankaj.dubey@samsung.com>
> > > Signed-off-by: Amit Daniel Kachhap <amit.daniel@samsung.com>
> > > ---
> > > arch/arm/mach-exynos/Kconfig | 1 +
> > > arch/arm/mach-exynos/Makefile | 2 +-
> > > drivers/mfd/Kconfig | 9 +++++++++
> > > drivers/mfd/Makefile | 1 +
> > > .../mach-exynos/pmu.c => drivers/mfd/exynos-pmu.c | 0
> > > 5 files changed, 12 insertions(+), 1 deletion(-) rename
> > > arch/arm/mach-exynos/pmu.c => drivers/mfd/exynos-pmu.c (100%)
> >
> > I thought we spoke about this already [1]? What's changed?
> >
> > [1] https://lkml.org/lkml/2014/4/29/193
> >
>
> Yes correct, we had discussion about this in above post. But at that time I was not having enough points to
> put forward for keeping Exynos PMU driver in MFD folder.
There are no valid points for keeping PMU code in MFD.
> At that point there was only one idea behind keeping Exynos PMU that in future it will be reused for ARM64
> based SoC for PM related functionalities.
> But in this series we have implemented Exynos Power Domain for Samsung's ARM64 based SoCs.
>
> As far as I can see this will in following ways -
>
> 1: Moving out PM domain specific code from mach-exynos and reuse of same code for ARM64 based SoC also.
> 2: Since PM domain relies on PMU registers and does not have its own DT binding, MFD client and MFD device
> is most suitable for making this kind of platform drivers.
MFD can be used to register the device, but the driver must not live
in MFD. Please relocate it into drivers/power.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-11-04 8:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 3:52 [PATCH 00/12] soc: samsung: Modify and enhance power domain driver Amit Daniel Kachhap
2014-11-03 3:52 ` [PATCH 01/12] ARM: EXYNOS: Move pmu specific header files under "linux/mfd/samsung" Amit Daniel Kachhap
2014-11-03 3:53 ` [PATCH 02/12] drivers: mfd: Add support for Exynos PMU driver Amit Daniel Kachhap
2014-11-03 15:26 ` Lee Jones
2014-11-04 3:18 ` Pankaj Dubey
2014-11-04 8:24 ` Lee Jones [this message]
2014-11-05 13:47 ` Sylwester Nawrocki
2014-11-03 3:53 ` [PATCH 03/12] PM / Domains: Add notifier support for power domain transitions Amit Daniel Kachhap
2014-11-03 14:54 ` Rafael J. Wysocki
2014-11-03 14:52 ` Ulf Hansson
2014-11-04 6:18 ` amit daniel kachhap
2014-11-03 18:23 ` Kevin Hilman
2014-11-04 6:44 ` amit daniel kachhap
2014-11-04 11:01 ` Sylwester Nawrocki
2014-11-07 18:45 ` Kevin Hilman
2014-11-10 9:08 ` amit daniel kachhap
2014-11-28 18:04 ` Sylwester Nawrocki
2014-11-03 18:21 ` Sylwester Nawrocki
2014-11-03 18:41 ` Sylwester Nawrocki
2014-11-04 3:23 ` Pankaj Dubey
2014-11-04 6:16 ` amit daniel kachhap
2014-11-04 12:08 ` Sylwester Nawrocki
2014-11-04 18:10 ` [RFC PATCH] pm: Add PM domain state transition notifications Sylwester Nawrocki
2014-11-03 3:53 ` [PATCH 04/12] mfd: exynos-pmu: Register exynos-pmu driver as a mfd driver Amit Daniel Kachhap
2014-11-03 3:53 ` [PATCH 05/12] arm: exynos: Add platform driver support for power domain driver Amit Daniel Kachhap
2014-11-03 3:53 ` [PATCH 06/12] soc: exynos: Move exynos power domain file to driver/soc/samsung folder Amit Daniel Kachhap
2014-11-03 3:53 ` [PATCH 07/12] soc: samsung: pm_domain: Use compatible name for power domain name Amit Daniel Kachhap
2014-11-03 3:53 ` [PATCH 08/12] soc: samsung: pm_domain: Add a new parameter for power configuration Amit Daniel Kachhap
2014-11-03 3:53 ` [PATCH 09/12] soc: samsung: pm_domain: Add support for parent power domain Amit Daniel Kachhap
2014-11-03 3:53 ` [PATCH 10/12] soc: samsung: pm_domain: Use the recently added PM Domain notifiers Amit Daniel Kachhap
2014-11-03 3:53 ` [PATCH 11/12] clk: samsung: save and restore clock registers for power domain Amit Daniel Kachhap
2014-11-03 3:53 ` [PATCH 12/12] arm64: Kconfig: Enable PM_GENERIC_DOMAINS for exynos7 Amit Daniel Kachhap
[not found] <000601cff985$5b8911f0$129b35d0$@samsung.com>
2014-11-06 6:17 ` [PATCH 02/12] drivers: mfd: Add support for Exynos PMU driver amit daniel kachhap
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=20141104082402.GE17577@x1 \
--to=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).