From: gerg@snapgear.com (Greg Ungerer)
To: linux-arm-kernel@lists.infradead.org
Subject: Freescale fec.c driver breakage
Date: Tue, 5 Jun 2012 23:24:29 +1000 [thread overview]
Message-ID: <4FCE088D.1060604@snapgear.com> (raw)
In-Reply-To: <20120605124844.GR30400@pengutronix.de>
On 06/05/2012 10:48 PM, Sascha Hauer wrote:
> On Tue, Jun 05, 2012 at 10:17:02PM +1000, Greg Ungerer wrote:
>>
>>> clkdev
>>> provides an abstraction which can map these onto the platform, even if
>>> you don't use the generic clk API clkdev is still very useful and will
>>> help with a lot of these issues.
>>
>> In this specific case I don't know what the ipg or ahb clocks are on iMX
>> (Sascha?), but there is nothing equivalent to them in the FEC cores used
>> on existing ColdFire CPUs. They seem to be platform specific (iMX) more
>> than FEC driver specific.
>
> I am sure the Coldfire FEC also needs clocks to work. Just like Mark
> said, they may be not software controllable. The names 'ipg' and 'ahb'
> may be i.MX specific though.
Well, yeah, of course there are clocks involved. But you pretty much
hit the point here. 'ipg' and 'ahb' here are platform specific.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg at 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
next prev parent reply other threads:[~2012-06-05 13:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 4:42 Freescale fec.c driver breakage Greg Ungerer
2012-06-04 8:19 ` Sascha Hauer
2012-06-04 9:16 ` Mark Brown
2012-06-05 6:55 ` Greg Ungerer
2012-06-05 9:41 ` Mark Brown
2012-06-05 12:17 ` Greg Ungerer
2012-06-05 12:24 ` Mark Brown
2012-06-05 12:36 ` Greg Ungerer
2012-06-05 12:40 ` Mark Brown
2012-06-05 12:48 ` Sascha Hauer
2012-06-05 13:24 ` Greg Ungerer [this message]
2012-06-05 13:41 ` Mark Brown
2012-06-05 14:35 ` Steven King
2012-06-06 7:41 ` Greg Ungerer
2012-06-07 23:36 ` Mark Brown
2012-06-05 13:42 ` Sascha Hauer
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=4FCE088D.1060604@snapgear.com \
--to=gerg@snapgear.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 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.