From: Vishwanath Sripathy <vishwanath.bs@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: RE: [RFC][PATCH 0/3] OMAP PM: Voltage layer clean up
Date: Tue, 15 Mar 2011 21:36:22 +0530 [thread overview]
Message-ID: <704e43df1ea426a676115cd34b93649e@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinO0XWcDO18Kv-pVL=QUTq2X5ffF5XRLw6_POOQ@mail.gmail.com>
> -----Original Message-----
> From: Menon, Nishanth [mailto:nm@ti.com]
> Sent: Tuesday, March 15, 2011 8:38 PM
> To: Vishwanath BS
> Cc: linux-omap@vger.kernel.org
> Subject: Re: [RFC][PATCH 0/3] OMAP PM: Voltage layer clean up
>
> On Tue, Mar 15, 2011 at 20:03, Vishwanath BS
> <vishwanath.bs@ti.com> wrote:
> >
> > This patch series attempts to do some more clean up on OMAP Voltage
> layer on top
> > of the clean up done by Paul as part of
> > https://patchwork.kernel.org/patch/591421/
> >
> > These patches are generated against latest omap-for-linus branch on
> Tony's tree
> > (commit id: 05f689400ea5fa3d71af82f910c8b140f87ad1f3) and tested
> on OMAP ZOOM3
> > and OMAP4430 SDP with Smartreflex enabled.
> >
> > Vishwanath BS (3):
> > OMAP PM: Seggregate Voltage layer parameters
> > OMAP PM: Add support for bypassing VP/VC in Voltage layer
> > OMAP PM: Add Board specific parameters for OMAP Volatge layer
>
> I dont really see why I need to keep fixing your $subjects, but here
> again,
> all $subjects, OMAP3+: PM: makes more sense
This is not OMAP3 specific. It applies to OMAP4 as well.
>
> > OMAP PM: Seggregate Voltage layer parameters
> ^^^^^^^ spell check please (tip: in vim, use
> ":help spell" to see how to use it while committing itself)
Thanks.
> > OMAP PM: Add support for bypassing VP/VC in Voltage layer
> > OMAP PM: Add Board specific parameters for OMAP Volatge layer
>
> ^^^^^^^^^ spell check voltage and I think you should be using
> small letters for board and voltage
>
> >
> > arch/arm/mach-omap2/board-4430sdp.c | 52 +++++++
>
> Curious if Panda and other OMAP3 platforms where considered.
That's TODO as per my Patch3 commit log.
Vishwa
>
> > arch/arm/mach-omap2/board-zoom.c | 79
> +++++++++++
> > arch/arm/mach-omap2/omap_opp_data.h | 8 +
> > arch/arm/mach-omap2/omap_twl.c | 113 ++++++++----
> ----
> > arch/arm/mach-omap2/opp3xxx_data.c | 50 +++++++
> > arch/arm/mach-omap2/opp4xxx_data.c | 38 +++++
> > arch/arm/mach-omap2/voltage.c | 179
> ++++++++++++++++++++-----
> > arch/arm/mach-omap2/voltage.h | 119
> +++++++++++++++--
> > arch/arm/mach-omap2/voltagedomains3xxx_data.c | 4 +
> > arch/arm/mach-omap2/voltagedomains44xx_data.c | 4 +
> > 10 files changed, 541 insertions(+), 105 deletions(-)
> >
>
>
> Regards,
> Nishanth Menon
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-03-15 16:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 14:33 [RFC][PATCH 0/3] OMAP PM: Voltage layer clean up Vishwanath BS
2011-03-15 14:33 ` [RFC][PATCH 1/3] OMAP PM: Seggregate Voltage layer parameters Vishwanath BS
2011-03-17 23:20 ` Kevin Hilman
2011-03-18 12:00 ` Vishwanath Sripathy
2011-04-02 0:03 ` Kevin Hilman
2011-04-05 7:08 ` Vishwanath Sripathy
2011-04-05 18:16 ` Kevin Hilman
2011-03-15 14:33 ` [RFC][PATCH 2/3] OMAP PM: Add support for bypassing VP/VC in Voltage layer Vishwanath BS
2011-03-15 15:16 ` Menon, Nishanth
2011-03-15 16:14 ` Vishwanath Sripathy
2011-03-16 6:58 ` Premi, Sanjeev
2011-03-15 14:33 ` [RFC][PATCH 3/3] OMAP PM: Add Board specific parameters for OMAP Volatge layer Vishwanath BS
2011-03-15 15:38 ` Menon, Nishanth
2011-03-16 5:53 ` Vishwanath Sripathy
2011-03-17 23:25 ` Kevin Hilman
2011-03-15 15:07 ` [RFC][PATCH 0/3] OMAP PM: Voltage layer clean up Menon, Nishanth
2011-03-15 16:06 ` Vishwanath Sripathy [this message]
2011-03-16 1:18 ` Nishanth Menon
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=704e43df1ea426a676115cd34b93649e@mail.gmail.com \
--to=vishwanath.bs@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
/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).