From: anilkumar@ti.com (AnilKumar Ch)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: OMAP2: AM33XX: Add cpufreq support
Date: Fri, 31 Aug 2012 15:07:18 +0530 [thread overview]
Message-ID: <1346405840-31058-1-git-send-email-anilkumar@ti.com> (raw)
Add cpufreq support to AM33XX family of devices by adding OPP
information, clock entry with cpu0 name and voltage supplies
to cpu0.
These patches have been tested on AM335x-EVM, AM335x-Bone and
these patches are based on cpufreq-cpu0 driver
http://marc.info/?l=linux-arm-kernel&m=134457735413293&w=2
AnilKumar Ch (2):
ARM: OMAP2+: AM33XX: Add clock entries to omap_clk data
arm/dts: AM33XX: Add device tree OPP table
arch/arm/boot/dts/am335x-bone.dts | 6 ++++++
arch/arm/boot/dts/am335x-evm.dts | 6 ++++++
arch/arm/boot/dts/am33xx.dtsi | 15 +++++++++++++++
arch/arm/mach-omap2/clock33xx_data.c | 1 +
4 files changed, 28 insertions(+)
--
1.7.9.5
next reply other threads:[~2012-08-31 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 9:37 AnilKumar Ch [this message]
2012-08-31 9:37 ` [PATCH 1/2] ARM: OMAP2+: AM33XX: Add clock entries to omap_clk data AnilKumar Ch
2012-08-31 9:37 ` [PATCH 2/2] arm/dts: AM33XX: Add device tree OPP table AnilKumar Ch
2012-09-12 17:21 ` Benoit Cousson
2012-09-13 6:23 ` AnilKumar, Chimata
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=1346405840-31058-1-git-send-email-anilkumar@ti.com \
--to=anilkumar@ti.com \
--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).