From: Vijay <katoch.vijay@gmail•com>
To: netdev@vger•kernel.org
Subject: Re: PHYless ethernet switch MAC-MAC serdes connection
Date: Wed, 21 Jan 2015 07:09:45 +0000 (UTC) [thread overview]
Message-ID: <loom.20150121T075010-767@post.gmane.org> (raw)
In-Reply-To: 54BE9B0B.7070507@gmail.com
Florian Fainelli <f.fainelli <at> gmail.com> writes:
>
> Do lan1 and lan2 interfaces set the RUNNING flag, which would indicate
> that the switch driver has detected a carrier for these individual
ports?
>
> Is the DSA switch driver correctly polling for LAN ports link
statuses?
>
Yes RUNNING flag is set.
Whenever I unplug/plug Ethernet cable. I see notification from dsa about
link up/down correctly.
>
> DSA registers a slave MDIO bus interface which calls into the "real"
> MDIO bus hardware to talk to the switch. In your case, you have both
an
> external switch and an external PHY connected to the same MDIO bus,
> which is fine.
>
> Your DT looks sane, although I suspect that lan2's PHY address is 3,
and
> not 2, as address 0 is typically a special MDIO broadcast address, so
> Port 0's PHY can be read at PHY addr 1, Port 1's PHY can be read at
PHY
> addr 2 etc... If you remove "lan2", does it work slightly better?
>
No, lan 1 and lan2 addresses are 0 and 1 respectively. I have logged
these values and these are printed on console as:
DSA: dsa.c: Init slave bus
DSA: slave.c: dsa_slave_mii_bus_init sw addr =0x1f , slave_mii_bus_id =
0x0
DSA: dsa.c: register created slave_mii_bus
Debug: drivers/net/phy/phy_device.c: Creating PHY-> phy_id = 0x1410c89,
addr = 0x0
Creating PHY-> AUTONEG_ENABLE for phy_id = 0x1410c89, addr = 0x0
Debug: drivers/net/phy/phy_device.c: Creating PHY-> phy_id = 0x1410c89,
addr = 0x1
Creating PHY-> AUTONEG_ENABLE for phy_id = 0x1410c89, addr = 0x1
libphy: dsa slave smi: probed
net lan1: PHY already attached
DSA: slave.c: mii_bus-> name = dsa slave smi , id =dsa-0:1f
net lan2: PHY already attached
DSA: slave.c: mii_bus-> name = dsa slave smi , id =dsa-0:1f
My eth0 fixed-link address is also 0 and eth1 PHY address is 1.
Removing lan2 is not improving the situation.
Even if I do not set up eth1. Then same issue is happening between lan1
and lan2. Whichever is configured first ( using ifconfig) is able to
transmit packet (Tx increments). And rest all ports ( lan2) are just
receiving (their Tx counters remain 0). Even if I ping to lan2 ip,
response will be received only when ethernet cable is plugged to lan1 (
because it will only be able transmit the response), It does not matter
if cable is plugged to lan2 port.
next prev parent reply other threads:[~2015-01-21 7:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 13:20 PHYless ethernet switch MAC-MAC serdes connection Vijay
2015-01-20 18:14 ` Florian Fainelli
2015-01-21 7:09 ` Vijay [this message]
2015-01-23 16:49 ` Vijay Katoch
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=loom.20150121T075010-767@post.gmane.org \
--to=katoch.vijay@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.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