From: Nishanth Menon <nm@ti.com>
To: Kevin Hilman <khilman@linaro.org>
Cc: linux-omap@vger.kernel.org, "Rob Herring" <robherring2@gmail.com>,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
"Rajendra Nayak" <rnayak@ti.com>,
"Paul Walmsley" <paul@pwsan.com>,
"Benoît Cousson" <b-cousson@ti.com>,
"Jon Hunter" <jon-hunter@ti.com>, Keerthy <j-keerthy@ti.com>,
"Santosh Shilimkar" <santosh.shilimkar@ti.com>,
"Shawn Guo" <shawn.guo@linaro.org>
Subject: Re: [PATCH V3 0/2] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot
Date: Wed, 3 Apr 2013 13:22:24 -0500 [thread overview]
Message-ID: <20130403182224.GA3410@kahuna> (raw)
In-Reply-To: <87y5czzetg.fsf@linaro.org>
On 10:47-20130403, Kevin Hilman wrote:
> Nishanth Menon <nm@ti.com> writes:
[...]
> > Test coverage:
> > test script: http://pastebin.com/zrr8ptge
> > Platforms verified:
> > beaglebone(rev A6a) - AM33xx compatible - http://pastebin.com/GVP2wDVr
> > beagleboard (rev C1D) - OMAP3430 compatible
> > - DT enabled boot: http://pastebin.com/2AY1F5Qa
> > - No DT enabled boot: http://pastebin.com/hDk0gbpU
> > omap3-beagle-xm -OMAP3630 compatible - http://pastebin.com/5tHAQcLZ
> > Pandaboard -(OMAP4430 ES2.2) - http://pastebin.com/6D9aDPXT
> > Pandaboard-ES -(OMAP4460 ES1.1) - http://pastebin.com/ExrBEczr
>
> And thanks also for the broad testing.
>
> One nit about the test report/coverage is I don't see any
> test/verification that the voltage is still being scaled based on the DT
> based OPPs. It's easy to verify at least from the regulator PoV that
> the voltage is scaled also.
I had probed and verified voltage on beagle and beagle XM. OMAP4
obviously wont scale (as mentioned) due to the fact that vc-vp regulator
is needed.
>
> My dumb DVFS test script (below) should work on any busybox rootfs
thanks for the script. yep - I can use this as well, but given that probe
did verify voltage scale on TWL5030 inductors, it might be redundant.
Ref:
https://plus.google.com/photos/112464029509057661457/albums/5715034179943520193/5854221132322035042
I can take it again and show the same snap along with the log with the
mentioned script later today.
--
Regards,
Nishanth Menon
prev parent reply other threads:[~2013-04-03 18:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 21:52 [PATCH V3 0/2] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot Nishanth Menon
2013-03-28 21:52 ` Nishanth Menon
2013-03-28 21:52 ` [PATCH V3 1/2] ARM: OMAP3+: use cpu0-cpufreq driver in device tree supported boot Nishanth Menon
2013-03-28 21:52 ` Nishanth Menon
2013-04-03 18:47 ` Kevin Hilman
2013-04-03 18:47 ` Kevin Hilman
2013-04-04 2:52 ` Nishanth Menon
2013-04-04 5:13 ` Rajendra Nayak
2013-04-04 19:00 ` Nishanth Menon
2013-04-05 9:50 ` Rajendra Nayak
2013-04-05 11:26 ` Nishanth Menon
2013-04-05 16:13 ` Tony Lindgren
2013-04-05 16:32 ` Nishanth Menon
2013-04-05 17:05 ` Tony Lindgren
2013-04-05 17:17 ` Nishanth Menon
2013-04-05 19:28 ` Tony Lindgren
2013-04-05 20:02 ` Nishanth Menon
2013-04-05 21:10 ` Tony Lindgren
2013-04-05 21:32 ` Nishanth Menon
2013-04-05 21:40 ` Tony Lindgren
2013-04-05 22:10 ` Nishanth Menon
2013-04-05 22:17 ` Tony Lindgren
2013-04-05 22:23 ` Nishanth Menon
2013-03-28 21:52 ` [PATCH V3 2/2] cpufreq: OMAP: instantiate omap-cpufreq as a platform_driver Nishanth Menon
2013-03-28 21:52 ` Nishanth Menon
2013-03-29 2:59 ` Viresh Kumar
2013-04-05 17:07 ` Nishanth Menon
2013-04-05 21:34 ` Kevin Hilman
2013-04-05 21:34 ` Kevin Hilman
2013-04-05 21:36 ` Nishanth Menon
2013-04-03 17:47 ` [PATCH V3 0/2] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot Kevin Hilman
2013-04-03 18:22 ` Nishanth Menon [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=20130403182224.GA3410@kahuna \
--to=nm@ti.com \
--cc=b-cousson@ti.com \
--cc=cpufreq@vger.kernel.org \
--cc=j-keerthy@ti.com \
--cc=jon-hunter@ti.com \
--cc=khilman@linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=robherring2@gmail.com \
--cc=santosh.shilimkar@ti.com \
--cc=shawn.guo@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.