cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
add_engineering
Contributor
Contributor
2,956 Views
Registered: ‎03-09-2015

How to indicate two SATA lanes on ZynqMP in device tree

This is what should be inserted in the device tree for a SATA lane (for the SERDES/PHY config)

&sata {
    phys = <&lane2 PHY_TYPE_SATA 0 3 150000000>;
};

 

However, when using 2 SATA lanes, what should be included in the device tree then? The examples list
the use of one PHY per device, while the ZynqMP has a SATA controller that has two channels, hence, 2 PHY's are required.

 

How should I enter this in the device tree?

 

Thanks!

 

0 Kudos
5 Replies
hpoetzl
Voyager
Voyager
2,926 Views
Registered: ‎06-24-2013

Hey @add_engineering

 

How should I enter this in the device tree?

I would say like this:

&sata0 {
    phys = <&lane2 PHY_TYPE_SATA 0 2 150000000>;
};

&sata1 { phys = <&lane3 PHY_TYPE_SATA 1 3 150000000>;
};

Note that you need to adjust the lane and controller numbers accordingly.

 

Hope this helps,

Herbert

-------------- Yes, I do this for fun!
0 Kudos
add_engineering
Contributor
Contributor
2,916 Views
Registered: ‎03-09-2015

Hi,

There is only one SATA entry in the generated device tree. It is an entry for the controller.

0 Kudos
hpoetzl
Voyager
Voyager
2,910 Views
Registered: ‎06-24-2013

Sorry, I don't have access to a ZynqMP, but maybe this works:

&sata {
    phys = <&lane2 PHY_TYPE_SATA 0 2 150000000>, <&lane3 PHY_TYPE_SATA 1 3 150000000>;
};

Again, double check the parameters to both entries.

 

Hope this helps,

Herbert

-------------- Yes, I do this for fun!
0 Kudos
add_engineering
Contributor
Contributor
2,887 Views
Registered: ‎03-09-2015

Hi Herbert,

 

No I already tried that. The "driver" should iterate through this list but it doesn't.

Kind Regards

0 Kudos
add_engineering
Contributor
Contributor
2,708 Views
Registered: ‎03-09-2015

The "trick" is: you do not have to specify the phy anymore. Make sure you use the driver for SATA-controller that is more recent than the one in 2017.2!  The driver in 2017.2 does not handle the use 2 SATA ports correctly!

0 Kudos