From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Rafael Wysocki <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 0/4] PXA cpufreq conversion to clock API
Date: Sat, 15 Oct 2016 23:17:08 +0200 [thread overview]
Message-ID: <87oa2l5n3f.fsf@belgarion.home> (raw)
In-Reply-To: <20161015203421.GG1041@n2100.armlinux.org.uk> (Russell King's message of "Sat, 15 Oct 2016 21:34:21 +0100")
Russell King - ARM Linux <linux@armlinux.org.uk> writes:
> On Sat, Oct 15, 2016 at 09:57:26PM +0200, Robert Jarzmik wrote:
>> Hi,
>>
>> This serie is a preparation to shift the cpufreq of pxa2xx platforms to clocks
>> API.
>>
>> The first 3 patches are review and merge material :
>> - patch 1/4 for Viresh and Rafael
>> - patches 2/4 and 3/4 for me
>>
>> The 4th on is for review but not merge, as the clock changes must be fully
>> reviewed and go in first as a prequisite
>
> Have you tested whether this patch set results in functional cpufreq
> support - looking at drivers/clk/pxa, the CPU clock is read-only -
> it can't be used to change the clock rate. So, I very much doubt this
> has been functionally tested.
Oh yes I did, on lubbock and mainstone ... but this requires another patchset
under review, here :
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1247123.html
> Don't forget that changing the CPU clock rate needs other changes
> (like the memory clock rate) so all that code you're removing in
> patch 4 (which does the actual clock change) needs to go somewhere.
Sure, here :
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1247130.html
I would have been wiser to quote these URLs instead of speaking of "clock
changes must be fully review and go in first as a prequisite".
Cheers.
--
Robert
next prev parent reply other threads:[~2016-10-15 21:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-15 19:57 [PATCH v2 0/4] PXA cpufreq conversion to clock API Robert Jarzmik
2016-10-15 19:57 ` [PATCH v2 1/4] cpufreq: pxa: use generic platdev driver for device-tree Robert Jarzmik
2016-10-18 11:38 ` Viresh Kumar
2016-10-18 15:35 ` Robert Jarzmik
2016-10-19 13:52 ` Viresh Kumar
2016-10-19 20:06 ` Robert Jarzmik
2016-10-20 3:34 ` Viresh Kumar
2016-10-21 15:17 ` Robert Jarzmik
2016-10-15 19:57 ` [PATCH v2 2/4] ARM: dts: pxa: add pxa25x cpu operating points Robert Jarzmik
2016-10-18 11:39 ` Viresh Kumar
2016-10-18 15:30 ` Robert Jarzmik
2016-10-19 13:51 ` Viresh Kumar
2016-10-15 19:57 ` [PATCH v2 3/4] ARM: dts: pxa: add pxa27x " Robert Jarzmik
2016-10-15 19:57 ` [PATCH v2 4/4] cpufreq: pxa: convert to clock API Robert Jarzmik
2016-10-18 11:40 ` Viresh Kumar
2016-10-22 21:37 ` Robert Jarzmik
2016-10-24 3:33 ` Viresh Kumar
2016-10-15 20:34 ` [PATCH v2 0/4] PXA cpufreq conversion " Russell King - ARM Linux
2016-10-15 21:17 ` Robert Jarzmik [this message]
2016-10-15 21:38 ` WARNING: SOMEONE RECEIVING THIS HAS BEEN HACKED (was: Re: [PATCH v2 0/4] PXA cpufreq conversion to clock API) Russell King - ARM Linux
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=87oa2l5n3f.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=daniel@zonque.org \
--cc=devicetree@vger.kernel.org \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.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