From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Tomasz Figa' <tomasz.figa@gmail.com>,
'Thomas Abraham' <thomas.ab@samsung.com>
Cc: cpufreq@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, mturquette@linaro.org,
shawn.guo@linaro.org, t.figa@samsung.com, l.majewski@samsung.com,
viresh.kumar@linaro.org, heiko@sntech.de
Subject: RE: [PATCH v5 0/7] cpufreq: use cpufreq-cpu0 driver for exynos based platforms
Date: Mon, 26 May 2014 10:37:50 +0900 [thread overview]
Message-ID: <032801cf7883$1cde3fd0$569abf70$@samsung.com> (raw)
In-Reply-To: <538294F9.2060508@gmail.com>
Tomasz Figa wrote:
>
> Hi Kukjin,
>
Hi,
> On 26.05.2014 00:50, Kukjin Kim wrote:
> > On 05/23/14 23:27, Thomas Abraham wrote:
> >> Changes since v4:
> >> - Various changes in clock code suggested by Tomasz
> >> Figa<t.figa@samsung.com>
> >> - This series depends on mutiple other patches
> >> [a] patch that introduces read-only attribute for clock dividers.
> >> -
> >> http://lists.infradead.org/pipermail/linux-arm-kernel/2014-
> May/259264.html
> >>
> >> [b] the series "PM / OPP: move cpufreq specific helpers out of OPP
> >> layer"
> >> -
> >> https://www.mail-archive.com/linux-omap@vger.kernel.org/msg104610.html
> >> [c] the series "cpufreq: opp: Add device tree based lookup of boost
> >> mode frequency"
> >> - http://www.spinics.net/lists/arm-kernel/msg334336.html
> >>
> > This series looks good to me after quick loking at but as I replied on
> > other thread, I'm not sure above changes are ready for 3.16 or not...
> >
> > Maybe we can revisit this series for 3.17?...hmm...
>
> Also two more issues:
>
> 1) DT bindings are not acked by DT maintainers,
> 2) there are my comments to DT bindings from v4 not addressed.
>
> There are also several comments about the code of v4 not addressed, but
> this is not that important, as opposed to DT bindings which are supposed
> to be stable ABI.
>
> Still, I don't think this is a big deal anymore, as we can have cpufreq
> working with multiplatform with my hack patch and polish the
> implementation of this series without any hurry.
>
Yeah, I'm waiting for Viresh's ack on your v2 exynos-cpufreq changes for
multiplatform...
- Kukjin
WARNING: multiple messages have this Message-ID (diff)
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/7] cpufreq: use cpufreq-cpu0 driver for exynos based platforms
Date: Mon, 26 May 2014 10:37:50 +0900 [thread overview]
Message-ID: <032801cf7883$1cde3fd0$569abf70$@samsung.com> (raw)
In-Reply-To: <538294F9.2060508@gmail.com>
Tomasz Figa wrote:
>
> Hi Kukjin,
>
Hi,
> On 26.05.2014 00:50, Kukjin Kim wrote:
> > On 05/23/14 23:27, Thomas Abraham wrote:
> >> Changes since v4:
> >> - Various changes in clock code suggested by Tomasz
> >> Figa<t.figa@samsung.com>
> >> - This series depends on mutiple other patches
> >> [a] patch that introduces read-only attribute for clock dividers.
> >> -
> >> http://lists.infradead.org/pipermail/linux-arm-kernel/2014-
> May/259264.html
> >>
> >> [b] the series "PM / OPP: move cpufreq specific helpers out of OPP
> >> layer"
> >> -
> >> https://www.mail-archive.com/linux-omap at vger.kernel.org/msg104610.html
> >> [c] the series "cpufreq: opp: Add device tree based lookup of boost
> >> mode frequency"
> >> - http://www.spinics.net/lists/arm-kernel/msg334336.html
> >>
> > This series looks good to me after quick loking at but as I replied on
> > other thread, I'm not sure above changes are ready for 3.16 or not...
> >
> > Maybe we can revisit this series for 3.17?...hmm...
>
> Also two more issues:
>
> 1) DT bindings are not acked by DT maintainers,
> 2) there are my comments to DT bindings from v4 not addressed.
>
> There are also several comments about the code of v4 not addressed, but
> this is not that important, as opposed to DT bindings which are supposed
> to be stable ABI.
>
> Still, I don't think this is a big deal anymore, as we can have cpufreq
> working with multiplatform with my hack patch and polish the
> implementation of this series without any hurry.
>
Yeah, I'm waiting for Viresh's ack on your v2 exynos-cpufreq changes for
multiplatform...
- Kukjin
next prev parent reply other threads:[~2014-05-26 1:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 14:27 [PATCH v5 0/7] cpufreq: use cpufreq-cpu0 driver for exynos based platforms Thomas Abraham
2014-05-23 14:27 ` Thomas Abraham
2014-05-23 14:27 ` [PATCH v5 1/7] cpufreq: cpufreq-cpu0: allow use of optional boost mode frequencies Thomas Abraham
2014-05-23 14:27 ` Thomas Abraham
2014-05-26 6:12 ` Viresh Kumar
2014-05-26 6:12 ` Viresh Kumar
2014-05-23 14:27 ` [PATCH v5 2/7] clk: samsung: add infrastructure to register cpu clocks Thomas Abraham
2014-05-23 14:27 ` Thomas Abraham
2014-05-23 14:27 ` [PATCH v5 3/7] Documentation: devicetree: add cpu clock configuration data binding for Exynos4/5 Thomas Abraham
2014-05-23 14:27 ` Thomas Abraham
2014-05-23 14:27 ` [PATCH v5 4/7] clk: exynos: use cpu-clock provider type to represent arm clock Thomas Abraham
2014-05-23 14:27 ` Thomas Abraham
2014-05-23 14:27 ` [PATCH v5 5/7] ARM: dts: Exynos: add cpu nodes, opp and cpu clock configuration data Thomas Abraham
2014-05-23 14:27 ` Thomas Abraham
2014-05-23 14:27 ` [PATCH v5 6/7] ARM: Exynos: switch to using generic cpufreq-cpu0 driver Thomas Abraham
2014-05-23 14:27 ` Thomas Abraham
2014-05-26 6:17 ` Viresh Kumar
2014-05-26 6:17 ` Viresh Kumar
2014-05-23 14:27 ` [PATCH v5 7/7] cpufreq: exynos: remove all exynos specific cpufreq driver support Thomas Abraham
2014-05-23 14:27 ` Thomas Abraham
2014-05-26 6:18 ` Viresh Kumar
2014-05-26 6:18 ` Viresh Kumar
2014-05-25 22:50 ` [PATCH v5 0/7] cpufreq: use cpufreq-cpu0 driver for exynos based platforms Kukjin Kim
2014-05-25 22:50 ` Kukjin Kim
2014-05-26 1:12 ` Tomasz Figa
2014-05-26 1:12 ` Tomasz Figa
2014-05-26 1:37 ` Kukjin Kim [this message]
2014-05-26 1:37 ` Kukjin Kim
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='032801cf7883$1cde3fd0$569abf70$@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=cpufreq@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=l.majewski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=shawn.guo@linaro.org \
--cc=t.figa@samsung.com \
--cc=thomas.ab@samsung.com \
--cc=tomasz.figa@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.