linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: baruch@tkos.co.il (Baruch Siach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] mx25: add support for FEC on i.MX25 PDK
Date: Mon, 14 Dec 2009 12:19:38 +0200	[thread overview]
Message-ID: <cover.1260785451.git.baruch@tkos.co.il> (raw)

This patch series adds support for the FEC peripheral of the i.MX25 on the 
i.MX25 PDK board.

The first two patches are fixes for compilation and run failures. The third 
patch enables RMII if the FEC driver. Finally, the last patch adds the 
necessary board support code (pads, clock, etc.)

The FEC fix seems like an ugly hack to me. Suggestions for a better solution 
are welcome.

Baruch Siach (4):
  mx25: s/NO_PAD_CTL/NO_PAD_CTRL/
  mx25: don't force input on FEC pins
  fec: add support for Freescale i.MX25 PDK (3DS)
  mx25: add support for FEC on i.MX25 PDK

 arch/arm/mach-mx25/clock.c                  |    2 +
 arch/arm/mach-mx25/devices.c                |   19 ++++++++
 arch/arm/mach-mx25/devices.h                |    1 +
 arch/arm/mach-mx25/mx25pdk.c                |   40 ++++++++++++++++-
 arch/arm/plat-mxc/include/mach/iomux-mx25.h |   64 +++++++++++++-------------
 arch/arm/plat-mxc/include/mach/mx25.h       |    4 ++
 drivers/net/fec.c                           |   22 +++++++++
 drivers/net/fec.h                           |    2 +
 8 files changed, 121 insertions(+), 33 deletions(-)

             reply	other threads:[~2009-12-14 10:19 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14 10:19 Baruch Siach [this message]
2009-12-14 10:19 ` [PATCH 1/4] mx25: s/NO_PAD_CTL/NO_PAD_CTRL/ Baruch Siach
2009-12-21 11:02   ` Sascha Hauer
2009-12-14 10:19 ` [PATCH 2/4] mx25: don't force input on FEC pins Baruch Siach
2009-12-21 11:04   ` Sascha Hauer
2009-12-22  7:12     ` Baruch Siach
2009-12-14 10:19 ` [PATCH 3/4] fec: add support for Freescale i.MX25 PDK (3DS) Baruch Siach
2009-12-14 10:33   ` Sascha Hauer
2009-12-15  8:31     ` Baruch Siach
2009-12-15 11:52       ` Greg Ungerer
2009-12-15 20:11         ` Baruch Siach
2009-12-16  0:13           ` Greg Ungerer
2009-12-16  6:34             ` Baruch Siach
2009-12-16  6:49               ` Greg Ungerer
2009-12-16  7:07                 ` Baruch Siach
2010-01-05  8:24               ` Baruch Siach
2010-01-11  3:25                 ` Greg Ungerer
2010-01-25 11:21               ` Baruch Siach
2010-05-19 15:15                 ` Jean-Christophe Dubois
2010-05-20  6:46                   ` Sascha Hauer
2010-05-20  6:49                     ` David Miller
2009-12-15  1:27   ` Greg Ungerer
2009-12-15  6:08     ` Baruch Siach
2009-12-14 10:19 ` [PATCH 4/4] mx25: add support for FEC on i.MX25 PDK Baruch Siach
2009-12-15  8:47   ` Baruch Siach
2009-12-21 11:08   ` Sascha Hauer
2009-12-21 11:44     ` [PATCH 1/2] mx25: add support for FEC on i.MX25 Baruch Siach
2009-12-21 11:44     ` [PATCH 2/2] mx25: pdk: add platform code for FEC support Baruch Siach
2009-12-21  6:04 ` [PATCH 0/4] mx25: add support for FEC on i.MX25 PDK Baruch Siach

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=cover.1260785451.git.baruch@tkos.co.il \
    --to=baruch@tkos.co.il \
    --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).