All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: "G.N, Vijayakumar" <vijaykumar.gn@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 0/3] omap3: pm: removes hardcoded VDD1/2 OPP values and make threshold generic
Date: Thu, 19 Nov 2009 10:53:53 -0800	[thread overview]
Message-ID: <87y6m28hxa.fsf@deeprootsystems.com> (raw)
In-Reply-To: <E0D41E29EB0DAC4E9F3FF173962E9E940254330A61@dbde02.ent.ti.com> (G. N.'s message of "Thu\, 19 Nov 2009 16\:52\:29 +0530")

"G.N, Vijayakumar" <vijaykumar.gn@ti.com> writes:

> With 3 patches I am trying to 
> 1. Remove hardcoded VDD1 OPP values and make threshold generic
> 2. Remove hardcoded VDD2 OPP values and make threshold generic
> 3. adding new api inplace of MIN/MAX_VDD1/VDD2_OPP 
>          to support 3630 OPP constraning along with the existing 3430 constraint.
>
> Patches are rebased on the 2.6.32-rc7.
>
> Patches have been tested for 3630 for 2.6.32-rc5.

I'm going to hold off on this series.

We're in the middle of discussions and proposals on a major rework of
the OPP layer, so I don't think it's worthwhile to spend time on these
relatively minor cleanups at the moment.

Kevin

      reply	other threads:[~2009-11-19 18:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E0D41E29EB0DAC4E9F3FF173962E9E940254169ADA@dbde02.ent.ti.com>
2009-11-19 11:22 ` [PATCH 0/3] omap3: pm: removes hardcoded VDD1/2 OPP values and make threshold generic G.N, Vijayakumar
2009-11-19 18:53   ` Kevin Hilman [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=87y6m28hxa.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=vijaykumar.gn@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 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.