• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 102 subscribers
  • Views 364 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

PROCESSOR-SDK-J721E: TDA4VM - Serdes DT nodes for custom board

PROCESSOR-SDK-J721E: TDA4VM - DT node for Serdes PHY

Sakthivelu Sambasivam
Prodigy 100 points

Part Number: PROCESSOR-SDK-J721E
Other Parts Discussed in Thread: TDA4VM

Hi Team,

In our custom board we have the Serdes muxing as below:

Serdes 0 : lane 0 -> SGMII

Serdes 0 : lane 1 -> SGMII

Serdes 1 : lane 1 -> SGMII

Serdes 3 : USB3 (Type C)

Referring to the k3-j721e-r5-common-proc-board.dts -> serdes_wiz0: wiz@5000000

As per DT bindings for this node, there should be a "Serdes" sub-node and in evm it is pointing to PCIe link @ serdes0 with (PHY_TYPE_PCIE).

serdes0: serdes@5000000 {
            compatible = "cdns,ti,sierra-phy-t0";
            reg-names = "serdes";
            reg = <0x00 0x5000000 0x00 0x10000>;
            #address-cells = <1>;
            #size-cells = <0>;
            resets = <&serdes_wiz0 0>;
            reset-names = "sierra_reset";
            clocks = <&wiz0_cmn_refclk>, <&wiz0_cmn_refclk1>;
            clock-names = "cmn_refclk", "cmn_refclk1";
           u-boot,dm-spl;

}

&serdes0 {
    serdes0_pcie_link: link@0 {
        reg = <0>;
        cdns,num-lanes = <1>;
        #phy-cells = <0>;
        cdns,phy-type = <PHY_TYPE_PCIE>;
        resets = <&serdes_wiz0 1>;
        u-boot,dm-spl;
    };
};

For my custom board case, how this node should be ?

  • 0
    TI__Mastermind 23125 points

    Mr. Samb, 

    I asked my colleague to generate an example configuration per your system so we can test. can you confirm the dts file name should be "k3-j721e-common-proc-board.dts"? you have "-r5" in the file name just want to confirm it was just your build configurations. 

    thanks
    Jian

  • 0 in reply to jian35385
    Prodigy 100 points

    hi,

    I am following the SDK convention only:

    k3-j721e-r5-common-proc-board.dts -> this is used by R5 u-boot/spl

    k3-j721e-common-proc-board.dts -> this is used by A72 u-boot/spl

    k3-j721e-common-proc-board.dts -> this is used by Kernel (this file is under Kernel DT folder)

    Hope this clarifies.

  • +1
    TI__Intellectual 1385 points

    SGMII is fully configured by Ethfw, so shouldn't be configured by kernel.

    SERDES3 is already used by USB in TDA4VM, so no modifications to be done for serdes3.

    So for serdes0, serdes1, serdes2, it should all be disabled in kernel.

    diff --git a/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts b/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts
    index 7d4b2a7b2130..cb73f0765391 100644
    --- a/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts
    +++ b/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts
    @@ -811,6 +811,7 @@
    };

    &serdes0 {
    + status = "disabled";
    serdes0_pcie_link: link@0 {
    reg = <0>;
    cdns,num-lanes = <1>;
    @@ -821,6 +822,7 @@
    };

    &serdes1 {
    + status = "disabled";
    serdes1_pcie_link: link@0 {
    reg = <0>;
    cdns,num-lanes = <2>;
    @@ -831,6 +833,7 @@
    };

    &serdes2 {
    + status = "disabled";
    serdes2_pcie_link: link@0 {
    reg = <0>;
    cdns,num-lanes = <2>;

    Also note default Ethfw might not support SGMII.

    Thanks

    Kishon