From: tarun.kanti@ti.com (DebBarma, Tarun Kanti)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] ARM: OMAP2+: dmtimer: cleanup related to devm API and clk usage
Date: Thu, 5 Jul 2012 09:32:58 +0530 [thread overview]
Message-ID: <CAC83ZvLcyRSc-X2o_05tS7R3S1s190ejDQaBOYHOK1JuknrAxA@mail.gmail.com> (raw)
In-Reply-To: <CAMQu2gxDbi191EdA0_acaJwhuAddXJ44FzVQJ=5c1Fh0PFDG4w@mail.gmail.com>
Hi Tony,
On Thu, Jun 14, 2012 at 4:28 PM, Shilimkar, Santosh
<santosh.shilimkar@ti.com> wrote:
> Tony,
>
> On Thu, Jun 14, 2012 at 4:24 PM, DebBarma, Tarun Kanti
> <tarun.kanti@ti.com> wrote:
>> On Fri, Apr 20, 2012 at 6:09 PM, Tarun Kanti DebBarma
>> <tarun.kanti@ti.com> wrote:
>>> The devm API usage in probe() simplifies error handling operation.
>>> Since iclk is not used in the driver it is removed from wherever
>>> not needed.
>>> Corrected the timer fck name mis-match between clock44xx_data.c and
>>> omap_hwmod_44xx_data.c.
>>> Added omap_hwmod_get_main_clk() API. There is no more need to construct
>>> clock names using sprintf() to be used in clk_get() during initialization.
>>>
>>> Reference:
>>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
>>> Commit: e816b57a337ea3b755de72bec38c10c864f23015 (Linux 3.4-rc3)
>>>
>>> Series is available here for reference:
>>> git://gitorious.org/~tarunkanti/omap-sw-develoment/tarunkantis-linux-omap-dev dmtimer_cleanup_for_3.5
>>>
>>> Tested on following platforms:
>>> OMAP5, OMAP4430SDP, OMAP3430SDP, OMAP2430SDP.
>>> Could not test on OMAP2420 due to unavailability of board.
>>>
>>> v2:
>>> - Use devm_request_and_ioremap() instead of request_mem_region() and ioremap()
>>> - Add omap_hwmod_get_main_clk() API
>>> - Reverted changes of clock names from OMAP2 and OMAP3 platforms
>>>
>>> Cc: Cousson, Benoit <b-cousson@ti.com>
>>> Cc: Paul Walmsley <paul@pwsan.com>
>>> Cc: Tony Lindgren <tony@atomide.com>
>>> Cc: Kevin Hilman <khilman@ti.com>
>>> Cc: Rajendra Nayak <rnayak@ti.com>
>>> Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
>>>
>>> Tarun Kanti DebBarma (4):
>>> ARM: OMAP: dmtimer: use devm_ API and do some cleanup in probe()
>>> ARM: OMAP2+: hwmod: add omap_hwmod_get_main_clk() API
>>> ARM: OMAP2+: dmtimer: cleanup iclk usage
>>> ARM: OMAP2+: dmtimer: cleanup fclk usage
>> [ping]
>> Only one of the patches in the series (ARM: OMAP2+: dmtimer: cleanup iclk usage)
>> has been taken. I just applied the remaining patches on top of Linux 3.5-rc2 and
>> tested on OMAP3 and OMAP4. Can the remaining patches be taken as well?
>
> Just to let you know that this cleanup is essential for Benoit's OMAP4
> hwmod cleanup
> and OMAP5 minimal support series.
This is a gentle reminder in case you have missed somehow!!
Let me know if anything else needs to be done.
Thanks.
--
Tarun
next prev parent reply other threads:[~2012-07-05 4:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 12:39 [PATCH v2 0/4] ARM: OMAP2+: dmtimer: cleanup related to devm API and clk usage Tarun Kanti DebBarma
2012-04-20 12:39 ` [PATCH v2 1/4] ARM: OMAP: dmtimer: use devm_ API and do some cleanup in probe() Tarun Kanti DebBarma
2012-04-20 12:39 ` [PATCH v2 2/4] ARM: OMAP2+: hwmod: add omap_hwmod_get_main_clk() API Tarun Kanti DebBarma
2012-04-20 15:10 ` Cousson, Benoit
2012-06-18 16:23 ` Paul Walmsley
2012-07-04 15:39 ` Paul Walmsley
2012-04-20 12:39 ` [PATCH v2 3/4] ARM: OMAP2+: dmtimer: cleanup iclk usage Tarun Kanti DebBarma
2012-04-23 17:48 ` Kevin Hilman
2012-04-23 19:36 ` DebBarma, Tarun Kanti
2012-04-24 0:34 ` Kevin Hilman
2012-04-20 12:39 ` [PATCH v2 4/4] ARM: OMAP2+: dmtimer: cleanup fclk usage Tarun Kanti DebBarma
2012-06-14 10:54 ` [PATCH v2 0/4] ARM: OMAP2+: dmtimer: cleanup related to devm API and clk usage DebBarma, Tarun Kanti
2012-06-14 10:58 ` Shilimkar, Santosh
2012-07-05 4:02 ` DebBarma, Tarun Kanti [this message]
2012-07-05 9:28 ` Tony Lindgren
2012-07-05 11:41 ` DebBarma, Tarun Kanti
2012-07-06 7:09 ` Tony Lindgren
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=CAC83ZvLcyRSc-X2o_05tS7R3S1s190ejDQaBOYHOK1JuknrAxA@mail.gmail.com \
--to=tarun.kanti@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).