From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: "'amit daniel kachhap'" <amit.daniel@samsung.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"'Thomas Abraham'" <thomas.abraham@linaro.org>,
cpufreq@vger.kernel.org,
"'Inderpal Singh'" <inderpal.singh@linaro.org>,
"'Viresh Kumar'" <viresh.kumar@linaro.org>,
"'Sylwester Nawrocki'" <s.nawrocki@samsung.com>,
"'Russell King - ARM Linux'" <linux@arm.linux.org.uk>
Subject: Re: [PATCH V5 0/4] cpufreq: exynos5440: support for cpufreq driver
Date: Mon, 08 Apr 2013 21:49:33 +0200 [thread overview]
Message-ID: <1403255.89Vcuzrghk@vostro.rjw.lan> (raw)
In-Reply-To: <2d0501ce3450$fac4e9c0$f04ebd40$%kim@samsung.com>
On Monday, April 08, 2013 09:02:44 PM Kukjin Kim wrote:
> amit daniel kachhap wrote:
> >
> > On Fri, Apr 5, 2013 at 6:08 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > > On Thursday, March 28, 2013 01:35:18 PM Amit Daniel Kachhap wrote:
> > >> Submitting the V5 version of exynos5440 cpufreq driver. This patchset
> > addresses
> > >> all the coding and design concerns raised especially by Viresh.
> > >>
> > >> Changes in V5:
> > >> * Removed the unnecessary DT look up entry from mach-exynos5-dt.c.
> > >> * Fixed all coding and comments issue raised by Viresh.
> > >>
> > >> Changes in V4:
> > >> * Added dev_err logs instead of pr_err.
> > >> * Used the devm_ioremap_resource API.
> > >> * Implemented several coding guidelines and minor error comments from
> > Sylwester,
> > >> Russell and Viresh.
> > >>
> > >> Changes in V3:
> > >> * Converted the driver to probe based as suggested by Viresh. This is
> > also
> > >> beneficial for multiplatform kernel.
> > >> * Other coding guidelines related changes.
> > >> * Moved the DT node outside cpu0 node as the driver is now a platform
> > >> driver.
> > >>
> > >> Changes in V2:
> > >> * Added OPP library support to parse DT parameters.
> > >> * Removed a hack to handle interrupts in bootup.
> > >> * Implemented other review comments from Viresh and Inder.
> > >>
> > >> All these patches are dependent on Thomas Abraham common clock patches.
> > >> (http://www.mail-archive.com/linux-samsung-
> > soc@vger.kernel.org/msg15860.html)
> > >> This whole patch series is based on 3.9-rc4.
> > >>
> > >> Amit Daniel Kachhap (4):
> > >> cpufreq: exynos: Add cpufreq driver for exynos5440
> > >> cpufreq: exynos: Remove error return even if no soc is found
> > >> arm: exynos: Enable OPP library support for exynos5440
> > >> arm: dts: Add cpufreq controller node for Exynos5440 SoC
> > >>
> > >> .../bindings/cpufreq/cpufreq-exynos5440.txt | 28 ++
> > >> arch/arm/boot/dts/exynos5440.dtsi | 12 +
> > >> arch/arm/mach-exynos/Kconfig | 2 +
> > >> drivers/cpufreq/Kconfig.arm | 9 +
> > >> drivers/cpufreq/Makefile | 1 +
> > >> drivers/cpufreq/exynos-cpufreq.c | 2 +-
> > >> drivers/cpufreq/exynos5440-cpufreq.c | 474
> > ++++++++++++++++++++
> > >> 7 files changed, 527 insertions(+), 1 deletions(-)
> > >> create mode 100644 Documentation/devicetree/bindings/cpufreq/cpufreq-
> > exynos5440.txt
> > >> create mode 100644 drivers/cpufreq/exynos5440-cpufreq.c
> > >
> > > Is this for me or the Samsung tree?
> > >
> > > If it's for me, I need ACKs from the Samsung tree maintainers. Also,
> > please
> > > address the Viresh's comments.
> > >
> > > Thanks,
> > > Rafael
> > >
> > Hi Rafael,
> >
> > I submitted the V6 version with all comments from Viresh addressed.
> >
> > Hi Kukjin Kim,
> >
> > Any suggestion on how this patch should be merged. In my opinion it
> > should go via Rafael's tree as this patch uses some fixes present in
> > Rafael's tree like modified cpufreq_notify_transition API.
> >
> Yes, I agree. The v6 series including resending 1/4 patch looks good to me.
> But the patch V6 4/4 would be sent to upstream via samsung tree to avoid
> useless merge conflicts and I think, it's possible.
>
> So Rafael, please take 1/4 ~ 3/4 patches in your tree with my ack.
>
> Acked-by: Kukjin Kim <kgene.kim@samsung.com>
>
> If any problems, please let me know.
I will, thank you!
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2013-04-08 19:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 8:05 Amit Daniel Kachhap
2013-03-28 8:05 ` [PATCH V5 1/4] cpufreq: exynos: Add cpufreq driver for exynos5440 Amit Daniel Kachhap
2013-03-28 8:53 ` Viresh Kumar
2013-03-28 12:42 ` Viresh Kumar
2013-04-08 8:25 ` amit daniel kachhap
2013-03-28 8:05 ` [PATCH V5 2/4] cpufreq: exynos: Remove error return even if no soc is found Amit Daniel Kachhap
2013-03-28 8:05 ` [PATCH V5 3/4] arm: exynos: Enable OPP library support for exynos5440 Amit Daniel Kachhap
2013-03-28 8:05 ` [PATCH V5 4/4] arm: dts: Add cpufreq controller node for Exynos5440 SoC Amit Daniel Kachhap
2013-03-28 8:33 ` [PATCH V5 0/4] cpufreq: exynos5440: support for cpufreq driver Viresh Kumar
2013-04-05 12:38 ` Rafael J. Wysocki
2013-04-08 8:36 ` amit daniel kachhap
2013-04-08 12:02 ` Kukjin Kim
2013-04-08 19:49 ` Rafael J. Wysocki [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=1403255.89Vcuzrghk@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=amit.daniel@samsung.com \
--cc=cpufreq@vger.kernel.org \
--cc=inderpal.singh@linaro.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=s.nawrocki@samsung.com \
--cc=thomas.abraham@linaro.org \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®