From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/5] omap timer changes for v3.8 merge window
Date: Wed, 14 Nov 2012 18:56:44 -0800 [thread overview]
Message-ID: <mailman.4.1352948229.1035.linux-arm-kernel@lists.infradead.org> (raw)
In-Reply-To: <pull-1352948204-277861>
The following changes since commit d308ba50a1234b299a00e63a95e61fdeb2f1a2df:
Merge branch 'omap-for-v3.8/cleanup-headers-prepare-multiplatform-v3' into omap-for-v3.8/dt (2012-11-09 14:58:34 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.8/timer-signed
for you to fetch changes up to 9dc57643738f9fbe45c10cc062903d5dfda5bdd9:
Merge branch 'fixes-timer' of github.com:jonhunter/linux into omap-for-v3.8/timer (2012-11-13 13:52:38 -0800)
----------------------------------------------------------------
Timer fixes for omaps via Jon Hunter <jon-hunter@ti.com>:
Several fixes for the OMAP DMTIMER driver including ...
1. Adding workaround for OMAP3+ errata i103/i767
2. Fixing posted mode support
3. Spurious interrupts when using match interrupt
4. HWMOD fixes for timers
5. Unnecessary restoration of read-only registers
6. Adds function for disabling timer interrupts
7. Fixing timer1 reset for OMAP1
----------------------------------------------------------------
Jon Hunter (13):
ARM: OMAP: Add DMTIMER definitions for posted mode
ARM: OMAP3+: Implement timer workaround for errata i103 and i767
ARM: OMAP: Fix timer posted mode support
ARM: OMAP3: Correct HWMOD DMTIMER SYSC register declarations
ARM: OMAP2/3: Define HWMOD software reset status for DMTIMERs
ARM: OMAP2+: Don't use __omap_dm_timer_reset()
ARM: OMAP: Fix dmtimer reset for timer1
ARM: OMAP: Don't restore of DMTIMER TISTAT register
ARM: OMAP: Don't restore DMTIMER interrupt status register
ARM: OMAP: Fix spurious interrupts when using timer match feature
ARM: OMAP: Add dmtimer interrupt disable function
ARM: OMAP: Remove unnecessary call to clk_get()
ARM: OMAP: Remove __omap_dm_timer_set_source function
Tony Lindgren (1):
Merge branch 'fixes-timer' of github.com:jonhunter/linux into omap-for-v3.8/timer
arch/arm/mach-omap2/omap_hwmod_2xxx_ipblock_data.c | 15 ++++-
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 41 ++++++------
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 4 ++
arch/arm/mach-omap2/timer.c | 70 +++++++++++++++-----
arch/arm/plat-omap/dmtimer.c | 77 +++++++++++++---------
arch/arm/plat-omap/include/plat/dmtimer.h | 72 ++++++++++++++------
6 files changed, 188 insertions(+), 91 deletions(-)
next prev parent reply other threads:[~2012-11-15 2:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 2:56 [GIT PULL 1/5] omap non critical fixes for v3.8 merge window Tony Lindgren
2012-11-15 2:56 ` [GIT PULL 2/5] omap cleanup fix and soc detection improvment " Tony Lindgren
2012-11-15 2:56 ` [GIT PULL 5/5] omap full-chip retention in suspend " Tony Lindgren
2012-11-15 2:56 ` [GIT PULL 3/5] omap common clock changes " Tony Lindgren
2012-11-15 2:56 ` Tony Lindgren [this message]
2012-11-15 16:51 ` [GIT PULL 1/5] omap non critical fixes " Arnd Bergmann
2012-11-15 17:35 ` 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=mailman.4.1352948229.1035.linux-arm-kernel@lists.infradead.org \
--to=tony@atomide.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).