[PATCH 0/5] MIPS: OCTEON: Convert some device to use Device Tree.

From: David Daney
Date: Mon Mar 26 2012 - 20:28:11 EST

From: David Daney <david.daney@xxxxxxxxxx>

This patch set depends on the previous set to add Device Tree to
OCTEON. That set can be found here:


The patches are for drivers scattered throughout the tree, but there
is an order dependency as well as the dependency mentioned above, so
it may be preferable to merge them all via Ralf's linux-mips.org tree
rather that separately via the various device sub-system maintainers.

The mdio-octeon.c and octeon_mgmt patches were already Acked-by davem.

The i2c has been seen before, but to my knowledge was never acked.

The octeon_ethernet patch is in staging and has also been seen before.

The serial patch is new.

David Daney (5):
i2c: Convert i2c-octeon.c to use device tree.
netdev: mdio-octeon.c: Convert to use device tree.
netdev: octeon_mgmt: Convert to use device tree.
staging: octeon_ethernet: Convert to use device tree.
MIPS: Octeon: Use device tree to register serial ports.

arch/mips/cavium-octeon/octeon-irq.c | 8 -
arch/mips/cavium-octeon/octeon-platform.c | 176 ----------------
arch/mips/cavium-octeon/serial.c | 134 +++++--------
arch/mips/include/asm/octeon/octeon.h | 5 -
drivers/i2c/busses/i2c-octeon.c | 94 +++++----
drivers/net/ethernet/octeon/octeon_mgmt.c | 312 +++++++++++++++++++----------
drivers/net/phy/mdio-octeon.c | 92 ++++++---
drivers/staging/octeon/ethernet-mdio.c | 28 ++--
drivers/staging/octeon/ethernet.c | 153 +++++++++-----
drivers/staging/octeon/octeon-ethernet.h | 3 +
10 files changed, 487 insertions(+), 518 deletions(-)

Cc: netdev@xxxxxxxxxxxxxxx
Cc: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
Cc: David S. Miller <davem@xxxxxxxxxxxxx>
Cc: "Jean Delvare (PC drivers, core)" <khali@xxxxxxxxxxxx>
Cc: "Ben Dooks (embedded platforms)" <ben-linux@xxxxxxxxx>
Cc: "Wolfram Sang (embedded platforms)" <w.sang@xxxxxxxxxxxxxx>
Cc: linux-i2c@xxxxxxxxxxxxxxx

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/