From: Renaud Barbier <renaud.barbier@ge.com>
To: barebox@lists.infradead.org
Subject: [PATCH v2 0/2] gianfar: prevent resource conflict
Date: Tue, 25 Jun 2013 14:09:58 +0100 [thread overview]
Message-ID: <1372165800-18759-1-git-send-email-renaud.barbier@ge.com> (raw)
In-Reply-To: <1369926935-24159-1-git-send-email-renaud.barbier@ge.com>
This patch v2 avoids resource conflicts between the gianfar port
instances by substituting dev_request_mem_region for
dev_get_mem_region.
In addition, it separates the MDIO buses from their Ethernet device
by creating MDIO bus devices to access the external bus and TBI
interfaces.
This patch is tested on the P2020RDB for which there are 3 MDIO buses:
- The main MDIO bus "gfar-mdio", linked to port eTSEC1 is used to
connect external PHYs for all ports and map the internal TBI
interface of eTSEC1.
- The MDIO buses "gfar-tpiphy" map TBI interface registers on all
remaining ports.
Renaud Barbier (2):
ppc: gianfar MDIO buses
P2020RDB: update build configuration
arch/ppc/boards/freescale-p2020rdb/p2020rdb.c | 13 ++-
arch/ppc/configs/p2020rdb_defconfig | 4 +-
arch/ppc/mach-mpc85xx/eth-devices.c | 44 +++++---
arch/ppc/mach-mpc85xx/include/mach/gianfar.h | 4 +
drivers/net/gianfar.c | 146 +++++++++++++++++++------
drivers/net/gianfar.h | 13 ++-
6 files changed, 165 insertions(+), 59 deletions(-)
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-06-25 13:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 15:15 [PATCH] " Renaud Barbier
2013-06-01 9:20 ` Sascha Hauer
2013-06-03 9:31 ` Renaud Barbier
2013-06-04 17:01 ` Renaud Barbier
2013-06-05 7:12 ` Sascha Hauer
2013-06-05 9:05 ` Renaud Barbier
2013-06-25 13:09 ` Renaud Barbier [this message]
2013-06-25 13:09 ` [PATCH 1/2] ppc: gianfar MDIO buses Renaud Barbier
2013-06-26 6:44 ` Sascha Hauer
2013-06-25 13:10 ` [PATCH 2/2] P2020RDB: update build configuration Renaud Barbier
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=1372165800-18759-1-git-send-email-renaud.barbier@ge.com \
--to=renaud.barbier@ge.com \
--cc=barebox@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