Linux M68K Architecture development
 help / color / mirror / Atom feed
From: gerg@uclinux.org
To: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org
Cc: Greg Ungerer <gerg@uclinux.org>
Subject: [PATCH 0/2] m68knommu: clean up timer code on the ColdFire 53xx
Date: Tue, 27 May 2014 16:28:20 +1000	[thread overview]
Message-ID: <1401172102-1599-1-git-send-email-gerg@uclinux.org> (raw)

From: Greg Ungerer <gerg@uclinux.org>

The timer code used on the ColdFire 53xx series is abusing the old 16bit
timer code. The hardware module it uses is really the more modern DMA
timer hardware module. It bends the reads/writes and modifies some addresses
so that it basically works.

It would be much better to use the modern Programmable Interrupt Timer
hardware module that these SoC contain. This PIT timer is used on all
the other modern ColdFire family members.

We also have DMA timer code that we will in the future use as a more
accurate clock source and cycle counter. So the idea here is to clean up
this usage to free up the timer hardware.

I don't have any 53xx based hardware, so I have not been able to run time
test this. If anyone can test this and confirm that it works as expected
that would be great.

Signed-off-by: Greg Ungerer <gerg@uclinux.org>
---
 arch/m68k/Kconfig.cpu                |    2 ++
 arch/m68k/include/asm/m53xxsim.h     |   19 ++++++++++---------
 arch/m68k/include/asm/mcftimer.h     |    4 ----
 arch/m68k/platform/coldfire/Makefile |    2 +-
 arch/m68k/platform/coldfire/timers.c |   16 ++--------------
 5 files changed, 15 insertions(+), 28 deletions(-)

             reply	other threads:[~2014-05-27  6:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27  6:28 gerg [this message]
2014-05-27  6:28 ` [PATCH 1/2] m68knommu: modify ColdFire 53xx family to use PIT timer gerg
2014-05-27  6:28 ` [PATCH 2/2] m68knommu: clean up ColdFire legacy timer gerg

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=1401172102-1599-1-git-send-email-gerg@uclinux.org \
    --to=gerg@uclinux.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=uclinux-dev@uclinux.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