From: Greg Ungerer <gerg@uclinux.org>
To: Steven King <sfking@fdwdc.com>
Cc: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org
Subject: Re: [PATCH 0/9] m68knommu: use ColdFire DMA timer
Date: Fri, 30 May 2014 10:51:34 +1000 [thread overview]
Message-ID: <5387D616.8030408@uclinux.org> (raw)
In-Reply-To: <201405291622.11925.sfking@fdwdc.com>
Hi Steven,
On 30/05/14 09:22, Steven King wrote:
> On Tuesday 27 May 2014 5:49:40 pm gerg@uclinux.org wrote:
>> From: Greg Ungerer <gerg@uclinux.org>
>>
>> Most of the modern ColdFire family members contain the DMA timer hardware
>> module. Build the support code for it and use it on those that do. We can
>> use it as an accurate time source.
>>
>> I don't have test platforms based on all of these ColdFire types, it would
>> be really helpful if anyone that has any of these can test these changes.
>> It build tests fine on all these types, and it works on 520x and 527x
>> based platforms.
>>
>> These changes are (neccessarily) on top of my recent patch series titled
>> "clean up timer code on the ColdFire 53xx".
>>
>> Signed-off-by: Greg Ungerer <gerg@uclinux.org>
>> ---
>> arch/m68k/include/asm/m520xsim.h | 8 ++++++++
>> arch/m68k/include/asm/m523xsim.h | 8 ++++++++
>> arch/m68k/include/asm/m527xsim.h | 8 ++++++++
>> arch/m68k/include/asm/m528xsim.h | 8 ++++++++
>> arch/m68k/include/asm/m53xxsim.h | 10 +++++-----
>> arch/m68k/include/asm/m5441xsim.h | 8 ++++++++
>> arch/m68k/platform/coldfire/Makefile | 10 +++++-----
>> arch/m68k/platform/coldfire/dma_timer.c | 24 +++++++++++++-----------
>> 8 files changed, 63 insertions(+), 21 deletions(-)
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> Hi Greg,
>
> I was able to to test this on 528x and 5441x and didnt have problems, so you
> can add my Acked-by if you want.
Great, thanks for testing. I will add your acked-by.
The most significant change is for the 532x and 537x, but
I don't have either of those to test with.
Regards
Greg
prev parent reply other threads:[~2014-05-30 0:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 0:49 [PATCH 0/9] m68knommu: use ColdFire DMA timer gerg
2014-05-28 0:49 ` [PATCH 1/9] m68knommu: add DMA timer base address definitions for ColdFire 53xx gerg
2014-05-28 0:49 ` [PATCH 2/9] m68knommu: add DMA timer base address definitions for ColdFire 520x gerg
2014-05-28 0:49 ` [PATCH 3/9] m68knommu: add DMA timer base address definitions for ColdFire 523x gerg
2014-05-28 0:49 ` [PATCH 4/9] m68knommu: add DMA timer base address definitions for ColdFire 527x gerg
2014-05-28 0:49 ` [PATCH 5/9] m68knommu: add DMA timer base address definitions for ColdFire 528x gerg
2014-05-28 0:49 ` [PATCH 6/9] m68knommu: add DMA timer base address definitions for ColdFire 5441x gerg
2014-05-28 0:49 ` [PATCH 7/9] m68knommu: modify ColdFire dma_timer to use common definitions gerg
2014-05-28 0:49 ` [PATCH 8/9] m68knommu: enable clock when using dma_timer hardware module gerg
2014-05-28 0:49 ` [PATCH 9/9] m68knommu: use ColdFire DMA timer module on devices that have it gerg
2014-05-28 15:59 ` Steven King
2014-05-28 23:46 ` Greg Ungerer
2014-05-29 23:22 ` [PATCH 0/9] m68knommu: use ColdFire DMA timer Steven King
2014-05-30 0:51 ` Greg Ungerer [this message]
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=5387D616.8030408@uclinux.org \
--to=gerg@uclinux.org \
--cc=linux-m68k@vger.kernel.org \
--cc=sfking@fdwdc.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.