• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 368 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:

TDA4VM: Compatible SGMII PHYs for TDA4VM

TDA4VM: SGMII/QSGMII Development Guide

John Weber
Intellectual 511 points
Part Number: TDA4VM

Hi there,

We are looking at a different QSGMII PHY than the VSC8514, due to availability.  Instead, we consider the LAN8814.

Is there a design guide (or set of guidelines) that we can refer to when designing with a QSGMII PHY?

We plan on using the native Linux drivers to control the PHY and the CPSWng.

Thanks!

  • 0
    TI__Mastermind 38910 points

    Hi,

    For hardware, It would be better for you to consult with phy manufacturer for designing with the phy.  The signals coming from TDA4VM would be mdio and serdes rx-tx lines.

    For software, the phy-driver will come from phy manufacturer. You might have to modify the device-tree node which can be done by help from the devicetree documentation available in Linux SDK at "[PSDKL-INSTALL-DIR]/board-support/linux/Documentation/devicetree/binding/net/". You should look at ethernet-phy.yaml and ethernet-controller.yaml.

    Regards,
    Tanmay

  • 0 in reply to Tanmay Patil
    Intellectual 450 points

    Hi, Tanmay:

    I am RocketRobot's colleague.

    Thanks for the feedback.

    We have some experience about dealing with RGMII MDIO PHY in Linux.

    What we are not familiar with is QSGMII on TI platform.

    For VSC8514, we see there is only a patch from TI in Linux kernel(TI SDK 08_04_00) to enable SerDes:

    It requires to enable auto-negotiation by configuring MAC SerDes PCS control register.

    VSC8514 almost goes to EOL.

    What else is required to add QSGMII support for a new PHY chip?

    Thanks~!!!

    BR,

    Richard

  • 0 in reply to Richard Hu
    TI__Mastermind 38910 points

    Hi Richard,

    I am transferring this thread to my colleague in Linux team who will be able to answer your question in detail.

    Regards,
    Tanmay

  • 0 in reply to Richard Hu
    TI__Expert 3575 points

    Hello Richard,

    The patch that you are referring to, is for adding the missing Auto-Negotiation
    feature to the mscc PHY driver. The mscc PHY driver is responsible for controlling
    the VSC8514 PHY. This auto-negotiation feature that was added, is only specific to
    VSC8514 PHY. If you are using a different PHY, ideally, the PHY driver would have
    already implemented this feature and therefore, no additional changes would be
    required in the PHY driver.

    I hope that answers your question. Please let me know if further information is
    required.

    Regards,
    Siddharth.