From: Sanjeev Premi <premi@ti.com>
To: linux-omap@vger.kernel.org
Cc: Sanjeev Premi <premi@ti.com>
Subject: [RFC 0/3] Support TPS65023 with AM35xx
Date: Wed, 23 Feb 2011 23:28:30 +0530 [thread overview]
Message-ID: <1298483913-20344-1-git-send-email-premi@ti.com> (raw)
Intent of this series is to solicit feedback on
on adding basic support for AM3517 and TPS65023.
This is definitely not the complete support, but
wanted to get early comments while i continue to
work.
Sanjeev Premi (3):
omap: voltage: Allow custom vp_init() implementation
am35xx: voltage: Add basic initialization
am35xx: pm: Hook-up with TPS65023
arch/arm/mach-omap2/am3517_tps.c | 96 ++++++++++++++++++++++++++++++++++++++
arch/arm/mach-omap2/voltage.c | 51 +++++++++++++++++++-
2 files changed, 145 insertions(+), 2 deletions(-)
create mode 100644 arch/arm/mach-omap2/am3517_tps.c
--
1.7.2.2
next reply other threads:[~2011-02-23 17:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 17:58 Sanjeev Premi [this message]
2011-02-23 17:58 ` [RFC 1/3] omap: voltage: Allow custom vp_init() implementation Sanjeev Premi
2011-02-23 18:36 ` Menon, Nishanth
2011-02-23 20:45 ` Premi, Sanjeev
2011-02-24 1:11 ` Nishanth Menon
2011-02-23 17:58 ` [RFC 2/3] am35xx: voltage: Add basic initialization Sanjeev Premi
2011-02-23 18:40 ` Menon, Nishanth
2011-02-23 17:58 ` [RFC 3/3] am35xx: pm: Hook-up with TPS65023 Sanjeev Premi
2011-02-23 18:43 ` Menon, Nishanth
2011-02-24 13:20 ` Premi, Sanjeev
2011-02-24 10:04 ` Vishwanath Sripathy
2011-03-07 15:20 ` Premi, Sanjeev
2011-03-07 16:31 ` Vishwanath Sripathy
2011-03-08 12:26 ` Premi, Sanjeev
2011-03-08 12:45 ` Vishwanath Sripathy
2011-03-08 13:25 ` Premi, Sanjeev
2011-03-08 12:46 ` Nishanth Menon
2011-03-08 13:18 ` Premi, Sanjeev
2011-03-08 13:27 ` Menon, Nishanth
2011-03-08 13:37 ` Premi, Sanjeev
2011-03-08 16:08 ` Kevin Hilman
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=1298483913-20344-1-git-send-email-premi@ti.com \
--to=premi@ti.com \
--cc=linux-omap@vger.kernel.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