From: Gary Thomas <gary@mlbassoc•com>
To: Linux PPC Development <linuxppc-dev@ozlabs•org>
Subject: UCC interactions
Date: Mon, 21 Jun 2010 13:00:11 -0600 [thread overview]
Message-ID: <4C1FB6BB.4040705@mlbassoc.com> (raw)
I'm running 2.6.33.3 on MPC8358. I have UCC1+UCC2 working fine
for ethernet, but when I add UCC3 as a UART, the network devices
quit working.
Here are my device tree entries:
/* ETH0 (UCC1, MDIO 0x02, RMII) */
enet_eth0: ethernet@2000 {
device_type = "network";
compatible = "ucc_geth";
cell-index = <1>;
reg = <0x2000 0x200>;
interrupts = <32>;
interrupt-parent = <&qeic>;
local-mac-address = [ 00 00 00 00 00 00 ];
rx-clock-name = "none";
tx-clock-name = "clk16";
phy-handle = <&phy_eth0>;
phy-connection-type = "rmii";
pio-handle = <&pio_ucc1>;
linux,network-index = <0>;
};
/* ETH1 (UCC2, MDIO 0x01, GMII) */
enet_eth1: ethernet@3000 {
device_type = "network";
compatible = "ucc_geth";
cell-index = <2>;
reg = <0x3000 0x200>;
interrupts = <33>;
interrupt-parent = <&qeic>;
local-mac-address = [ 00 00 00 00 00 00 ];
rx-clock-name = "clk4";
tx-clock-name = "none";
fixed-link = <1 1 1000 0 0>;
phy-connection-type = "gmii";
pio-handle = <&pio_ucc2>;
linux,network-index = <1>;
};
/* ttyQE0 (UCC3) */
serial_qe0: serial@4000 {
device_type = "serial";
compatible = "ucc_uart";
cell-index = <3>;
reg = <0x4000 0x200>;
interrupts = <34>;
interrupt-parent = <&qeic>;
port-number = <0>;
rx-clock-name = "brg1";
tx-clock-name = "brg1";
};
Are there known interactions between these two drivers/ports?
Maybe there's something obviously wrong with my device tree?
Thanks for any ideas/pointers
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2010-06-21 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 19:00 Gary Thomas [this message]
2010-06-21 19:19 ` UCC interactions Steven Blakeslee
2010-06-21 20:23 ` Gary Thomas
2010-06-22 14:51 ` Timur Tabi
2010-06-22 15:15 ` Chuck Meade
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=4C1FB6BB.4040705@mlbassoc.com \
--to=gary@mlbassoc$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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