From: Andrii Tseglytskyi <andrii.tseglytskyi@ti.com>
To: khilman@linaro.org, j-keerthy@ti.com
Cc: linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: [PATCH v2 0/2] PM / AVS: SmartReflex: optimization series
Date: Tue, 4 Jun 2013 12:58:31 +0300 [thread overview]
Message-ID: <1370339913-16135-1-git-send-email-andrii.tseglytskyi@ti.com> (raw)
The following patch series introduces a few optimizations for SmartReflex driver.
1. devm_* API usage for SmartReflex.
Benefits:
- auto handling of resources - allocation/auto free, map/auto unmap.
- lot of error checks can be dropped.
2. Another small optimization resolves order of initialization between SmartReflex driver
and SmartReflex class. Class is initialized before driver.
Patches are based on:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
tag: v3.10-rc4
Verified on OMAP4430. Boot - OK. SmartReflex registers debug dump - OK
Series v2 contains:
- spurious #define removed from "PM / AVS: SmartReflex: use devm_* API to initialize SmartReflex"
- rebased to v3.10-rc4
Andrii Tseglytskyi (2):
PM / AVS: SmartReflex: use devm_* API to initialize SmartReflex
PM / AVS: SmartReflex/class3: Fix order of initialization of SR class
and SR driver
arch/arm/mach-omap2/smartreflex-class3.c | 2 +-
drivers/power/avs/smartreflex.c | 85 ++++++++----------------------
2 files changed, 22 insertions(+), 65 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-06-04 9:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 9:58 Andrii Tseglytskyi [this message]
2013-06-04 9:58 ` [PATCH v2 1/2] PM / AVS: SmartReflex: use devm_* API to initialize SmartReflex Andrii Tseglytskyi
2013-06-10 17:51 ` Kevin Hilman
2013-06-04 9:58 ` [PATCH v2 2/2] PM / AVS: SmartReflex/class3: Fix order of initialization of SR class and SR driver Andrii Tseglytskyi
2013-06-10 17:52 ` Kevin Hilman
2013-06-12 13:32 ` Tony Lindgren
2013-06-12 15:33 ` Andrii Tseglytskyi
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=1370339913-16135-1-git-send-email-andrii.tseglytskyi@ti.com \
--to=andrii.tseglytskyi@ti.com \
--cc=j-keerthy@ti.com \
--cc=khilman@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@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;
as well as URLs for NNTP newsgroup(s).