From: Romit Dasgupta <romit@ti.com>
To: khilman@deeprootsystems.com
Cc: nm@ti.com, linux-omap@vger.kernel.org
Subject: [PM-WIP-OPP] [PATCH 0/2]: OPP layer changes (introducing enum for OPP types and returning NULL on failure from some OPP APIs)
Date: Fri, 15 Jan 2010 16:32:51 +0530 [thread overview]
Message-ID: <1263553371.3490.40.camel@boson> (raw)
Based on the discussion in the mailing list, I have taken some
suggestions and am reposting the patch. In this two part patchset:
a) the first patch introduces a new enum type for identifying different
OPP types. This helps in encapsulating the actual pointers to the
respective OPP lists inside the OPP layer itself. One can now interact
with the OPP layer by passing the appropriate OPP enum type instead of
the actual pointer to the OPP list.
b) the second patch is for the OPP layer to return NULL pointer (instead
of ERR_PTR) when the return type of the API is struct omap_opp *
Signed-off-by: Romit Dasgupta <romit@ti.com>
---
arch/arm/mach-omap2/pm34xx.c | 15 --
arch/arm/mach-omap2/resource34xx.c | 86 ++++++----------
arch/arm/mach-omap2/smartreflex.c | 33 +-----
arch/arm/plat-omap/common.c | 6 -
arch/arm/plat-omap/cpu-omap.c | 12 +-
arch/arm/plat-omap/include/plat/opp.h | 58 +++++-----
arch/arm/plat-omap/omap-pm-noop.c | 4
arch/arm/plat-omap/omap-pm-srf.c | 4
arch/arm/plat-omap/opp.c | 127 ++++++++++++++++--------
9 files changed, 170 insertions(+), 175 deletions(-)
reply other threads:[~2010-01-15 11:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1263553371.3490.40.camel@boson \
--to=romit@ti.com \
--cc=khilman@deeprootsystems.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