From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: ARMADA 370 - Distributed Switch Architecture (dsa) - device tree
Date: Mon, 13 Oct 2014 15:19:11 +0200 [thread overview]
Message-ID: <20141013131911.GD26864@lunn.ch> (raw)
In-Reply-To: <f1e8d1ba750bfb63f84471d0ec7de988@twien.net>
On Mon, Oct 13, 2014 at 12:14:41PM +0200, post at twien.net wrote:
> Dear all,
> I have a custom board equipped with an ARMADA 370 SoC (88f6W11) and
> a Marvell switch chip (88e6352) (I have written a device driver for
> the latter).
Hi Tormon
I think this is the first board anybody has tried DSA with the mvmeta
driver. So there could be issues there. You also need to be a little
bit careful with the kirkwood examples. Until recently, they were
broken.
You dsa node in your DT tree looks good. The dmesg output also seems
O.K. in terms of DSA. It has found the switch, meaning communication
through the ethernet mdio bus is working.
I think the issue is either in your mdio node, or the mvneta driver.
I'm currently working on a D-LINK DIR665, with a DSA setup. This is
kirkwood. My mdio node is simply:
&mdio {
status = "okay";
};
And the speed and duplex goes into the ethernet node:
ð0 {
status = "okay";
ethernet0-port at 0 {
speed = <1000>;
duplex = <1>;
};
};
The Ethernet node does not have a phandle to a phy node.
Can you try something similar?
Andrew
next prev parent reply other threads:[~2014-10-13 13:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 10:14 ARMADA 370 - Distributed Switch Architecture (dsa) - device tree post at twien.net
2014-10-13 11:19 ` Jason Cooper
2014-10-23 9:20 ` Thomas Petazzoni
2014-10-23 12:10 ` Jason Cooper
2014-10-23 12:57 ` post at twien.net
2014-10-23 14:05 ` Andrew Lunn
2014-10-23 14:19 ` post at twien.net
2014-10-13 13:19 ` Andrew Lunn [this message]
2014-10-13 18:25 ` Guenter Roeck
2014-10-14 6:05 ` post at twien.net
2014-10-14 13:30 ` Guenter Roeck
2014-10-14 11:35 ` Richard Cochran
2014-10-14 13:24 ` Guenter Roeck
2014-10-23 8:32 ` Richard Cochran
2014-10-14 2:08 ` Florian Fainelli
2014-10-14 11:14 ` post at twien.net
2014-10-14 16:14 ` Florian Fainelli
2014-10-15 13:42 ` post at twien.net
2014-10-15 13:47 ` Guenter Roeck
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=20141013131911.GD26864@lunn.ch \
--to=andrew@lunn.ch \
--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).