netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Alayev Michael <malayev@iai.co.il>
Cc: netdev@vger.kernel.org, Efter Yoram <yefter@iai.co.il>,
	Dror Alon <adror@iai.co.il>
Subject: Re: DTS for our Configuration
Date: Mon, 19 Mar 2018 17:56:38 +0100	[thread overview]
Message-ID: <20180319165622.GJ26039@lunn.ch> (raw)
In-Reply-To: <48F7D4389F30BA4383F214EE802BA47101706554EB@EXS10.iai.co.il>

On Mon, Mar 19, 2018 at 04:23:11PM +0000, Alayev Michael wrote:
> Hello Andrew,
> 
> You deserve a big thank you for your solution to our device-tree - the linux bootup log looks a lot better and It made a big progress for us.
> Though we still have some issues...
> 
> 1. Attached are 2 log files that are the result of your suggested dts:
> 	1st is your device-tree as is : results in kernel panic. Its probably caused by the "link" parameter.

The link parameters look correct. It is a pointer to the switches port
in the DSA link.

But i spotted a real problem. See bellow.

> 2. The switch's product number should be 0x0a1 but instead its 0xa10 (is it just a high-low byte thing?)

This is correct. The product number is contains the revision. You have
revision 0.

> 3. The stand-alone phy (gem1) is not detected properly. It should be device id mv88e1510.

> 	switch0: switch@1c: {
> 		compatible = "marvell,mv88e6190";
> 		reg = <0x1c>;
> 
> 		ports {
> 			#address-cells = <1>;
> 			#size-cells = <0>;
> 
> 			port@0 {
> 				reg = <0>;
> 				label = "cpu";
> 				fixed-link {
> 					speed = <1000>;
> 					full-duplex;
> 				};

There is a missing property here:

      	   	   	        ethernet = <&gem0>;


> 			port@1 {
> 				reg = <1>;
> 				label = "lan0";
> 			};
> 			port@2 {
> 				reg = <2>;
> 				label = "lan1";
> 			};
> 			...
> 			switch0port10: port@10 {
> 				reg = <10>;
> 				label = "dsa";
> 				link = <&switch1port10>;
> 				phy-mode = "sgmii";
> 			 	fixed-link {
> 					speed = <1000>;
> 					full-duplex;
> 				};
> 			};
> 		};
> 	};
> 
> 
> gem1: {
>       phy-handle = <phy0>;

and this is missing an &

       phy-handle = <&phy0>;

       Andrew

  reply	other threads:[~2018-03-19 16:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3988EA6F088014488BE41D19253A7EE40152236E92@EXS10.iai.co.il>
2018-03-16 15:12 ` DTS for our Configuration Andrew Lunn
     [not found]   ` <3988EA6F088014488BE41D19253A7EE40152236EE1@EXS10.iai.co.il>
2018-03-19 16:23     ` Alayev Michael
2018-03-19 16:56       ` Andrew Lunn [this message]
     [not found]         ` <48F7D4389F30BA4383F214EE802BA471017065554B@EXS10.iai.co.il>
2018-03-20 12:38           ` Andrew Lunn
     [not found] <48F7D4389F30BA4383F214EE802BA47101706555D3@EXS10.iai.co.il>
2018-03-22  9:55 ` Alayev Michael
2018-03-22 13:55   ` Andrew Lunn

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=20180319165622.GJ26039@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=adror@iai.co.il \
    --cc=malayev@iai.co.il \
    --cc=netdev@vger.kernel.org \
    --cc=yefter@iai.co.il \
    /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).