linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joel Fernandes <joelf@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Rajendra Nayak <rnayak@ti.com>,
	Linux OMAP List <linux-omap@vger.kernel.org>,
	Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/9] dmtimer code clean-up first pass
Date: Wed, 16 Apr 2014 19:00:00 -0500	[thread overview]
Message-ID: <1397692800-7395-1-git-send-email-joelf@ti.com> (raw)

Here are some minor cleanups for dmtimer code in preparation for moving it out
to drivers.

There is OMAP1 specific dmtimer code earlier, that are handled in mach-omap1
directly now.   Other than this, few functions and code has been refactored to
reduce redundancy and some minor cleanups.

OMAP1 hasn't been tested so I welcome anyone with HW to test this.

Joel Fernandes (9):
  ARM: OMAP: dmtimer: Remove setting of clk parent indirectly through
    platform hook
  ARM: OMAP: dmtimer: Add comments on OMAP1 clock framework
  ARM: OMAP: dmtimer: Add note to set parent from DT
  ARM: OMAP: dmtimer: Add function to check if timer is running
  ARM: OMAP1: dmtimer: Rewrite modify of IDLECT mask to use new
    is_running function
  ARM: OMAP: dmtimer: Add a write_ctrl function to simplify bit setting
  ARM: OMAP: dmtimer: Have __omap_dm_timer_load_start set ST bit in
    CTRL instead of caller
  ARM: OMAP: dmtimer: Add function to check for timer availability
  ARM: OMAP: dmtimer: Get rid of check for mem resource error

 arch/arm/mach-omap1/include/mach/hardware.h |    2 +
 arch/arm/mach-omap1/timer.c                 |   34 ++++-
 arch/arm/mach-omap2/timer.c                 |    6 +-
 arch/arm/plat-omap/dmtimer.c                |  185 +++++++++++++--------------
 arch/arm/plat-omap/include/plat/dmtimer.h   |    4 +-
 include/linux/platform_data/dmtimer-omap.h  |    2 -
 6 files changed, 129 insertions(+), 104 deletions(-)

-- 
1.7.9.5

                 reply	other threads:[~2014-04-17  0:00 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=1397692800-7395-1-git-send-email-joelf@ti.com \
    --to=joelf@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rnayak@ti.com \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).