From: Greg Ungerer <gerg@snapgear.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: linux-m68k@vger.kernel.org,
uClinux development list <uclinux-dev@uclinux.org>
Subject: Re: [PATCH 00/12] m68knommu: generalize the ColdFire clock support for all CPU types
Date: Tue, 27 Nov 2012 08:49:07 +1000 [thread overview]
Message-ID: <50B3F1E3.8040004@snapgear.com> (raw)
In-Reply-To: <20121126163431.62231f3b@skate>
Hi Thomas,
On 11/27/2012 01:34 AM, Thomas Petazzoni wrote:
> On Fri, 16 Nov 2012 14:47:24 +1000, gerg@snapgear.com wrote:
>> The current Coldfire clock code only really supports those ColdFire
>> CPU types that have the more advanced enable/disable clock hardware
>> support. If we generalize our clock code we can support all types,
>> even those with simpler fixed clock trees.
>>
>> This results in much cleaner and consistent clock support. And it
>> means that we can in the future use the clock API in our timers and
>> throughout the other ColdFire p[eripheraps, instead of hard coded
>> clock definitions.
>
> Have you considered instead using the generic clock framework that is
> now in drivers/clk/ ?
I have, and that is what I plan to do next. This set of patches
was intended to clean up (and generalize) what we currently have.
It doesn't really change the current ColdFire clocking code in
any way, just makes it work consistently across all CPU types.
Regards
Greg
--
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close, FAX: +61 7 3891 3630
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
prev parent reply other threads:[~2012-11-26 22:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 4:47 [PATCH 00/12] m68knommu: generalize the ColdFire clock support for all CPU types gerg
2012-11-16 4:47 ` [PATCH 01/12] m68knommu: add clock creation support macro for other ColdFire CPUs gerg
2012-11-16 6:30 ` Geert Uytterhoeven
2012-11-16 4:47 ` [PATCH 02/12] m68knommu: add clock definitions for 5206 ColdFire CPU types gerg
2012-11-16 4:47 ` [PATCH 03/12] m68knommu: add clock definitions for 523x " gerg
2012-11-16 4:47 ` [PATCH 04/12] m68knommu: add clock definitions for 5249 " gerg
2012-11-16 4:47 ` [PATCH 05/12] m68knommu: add clock definitions for 525x " gerg
2012-11-16 4:47 ` [PATCH 06/12] m68knommu: add clock definitions for 5272 " gerg
2012-11-16 4:47 ` [PATCH 07/12] m68knommu: add clock definitions for 527x " gerg
2012-11-16 4:47 ` [PATCH 08/12] m68knommu: add clock definitions for 528x " gerg
2012-11-16 4:47 ` [PATCH 09/12] m68knommu: add clock definitions for 5307 " gerg
2012-11-16 4:47 ` [PATCH 10/12] m68knommu: add clock definitions for 5407 " gerg
2012-11-16 4:47 ` [PATCH 11/12] m68knommu: add clock definitions for 54xx " gerg
2012-11-16 4:47 ` [PATCH 12/12] m68knommu: modify clock code so it can be used by all " gerg
2012-11-16 6:28 ` [PATCH 00/12] m68knommu: generalize the ColdFire clock support for all " Geert Uytterhoeven
2012-11-16 9:09 ` Greg Ungerer
2012-11-26 15:34 ` [uClinux-dev] " Thomas Petazzoni
2012-11-26 22:49 ` 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=50B3F1E3.8040004@snapgear.com \
--to=gerg@snapgear.com \
--cc=linux-m68k@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox