linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: Freescale fec.c driver breakage
Date: Tue, 5 Jun 2012 15:42:55 +0200	[thread overview]
Message-ID: <20120605134255.GS30400@pengutronix.de> (raw)
In-Reply-To: <4FCE088D.1060604@snapgear.com>

On Tue, Jun 05, 2012 at 11:24:29PM +1000, Greg Ungerer wrote:
> 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.

Are there any FEC specific names? If yes, we could use these instead,
otherwise if we have to make up names ourselves I think 'ipg' and 'ahb'
are fine.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

      parent reply	other threads:[~2012-06-05 13:42 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
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 [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=20120605134255.GS30400@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --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).