From: khilman@ti•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 3/4] ARM: OMAP2+: dmtimer: cleanup iclk usage
Date: Mon, 23 Apr 2012 10:48:44 -0700 [thread overview]
Message-ID: <87obqijq4j.fsf@ti.com> (raw)
In-Reply-To: <1334925563-20768-4-git-send-email-tarun.kanti@ti.com> (Tarun Kanti DebBarma's message of "Fri, 20 Apr 2012 18:09:22 +0530")
Tarun Kanti DebBarma <tarun.kanti@ti•com> writes:
> We do not use iclk anywhere in the dmtimer driver and so removing it.
> Hence removing the timer iclk entries from OMAP4 clkdev table as well.
What about the OMAP2/3 clkdev tables? Can't those be removed as well?
Comment applies to PATCH 4/4 also.
Kevin
next prev parent reply other threads:[~2012-04-23 17:48 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 [this message]
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
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=87obqijq4j.fsf@ti.com \
--to=khilman@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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