Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hw/arm/xlnx-versal-virt: modify gem/phy DT nodes #7

Merged
merged 1 commit into from
Sep 18, 2024

Conversation

ho28
Copy link
Collaborator

@ho28 ho28 commented Sep 17, 2024

Modify the gem/phy device tree nodes so that VxWorks properly binds the genericPhy driver to the ethernet-phy DT node. Previously, the phy was represented using a fixed-link node that VxWorks does not parse properly.

The compatible string for the gem node has been modified from "cdns,zynqmp-gem" to "cdns,versal-gem". The VxWorks gem driver does not match "cdns,zynqmp-gem".

Note: VxWorks needs additional property "phy-mode" to properly bind the driver against "cdns,versal-gem".

hw/arm/xlnx-versal-virt.c Outdated Show resolved Hide resolved
@calvincramer
Copy link
Collaborator

@ho28 can you show some test results? Manual is fine. I'm not too familiar with what the CI tests test, but it looked like generic arm and generic x86 64.

Copy link
Collaborator

@calvincramer calvincramer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ho28 showed it working live

Modify the gem/phy device tree nodes so that VxWorks
properly binds the genericPhy driver to the ethernet-phy
DT node. Previously, the phy was represented using a
fixed-link node that VxWorks does not parse properly.

The compatible string for the gem node has been modified
from "cdns,zynqmp-gem" to "cdns,versal-gem". The VxWorks
gem driver does not match "cdns,zynqmp-gem".

Note: VxWorks needs additional property "phy-mode" to
properly bind the driver against "cdns,versal-gem".

Signed-off-by: Nelson Ho <Nelson.Ho@windriver.com>
@ho28
Copy link
Collaborator Author

ho28 commented Sep 17, 2024

I made the changes mentioned above, removed the unnecessary properties from the phy node.

I also did some additional reading on the reg property of the phy node. I was under the assumption previously that the reg field (0xc) specified an offset from the regs or ranges presented by the GEM. After consulting the device tree documentation, it turns out the reg field is simply the phy index when specified as a property of a phy. I modified the constants and fields as appropriate.

@ho28 ho28 merged commit 02ee127 into Wind-River:wr-integration Sep 18, 2024
1 check passed
@ho28 ho28 deleted the nho/versal/genericphy branch September 18, 2024 05:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

vxworks cadence GEM driver fails to bind to the ethernet node in the xlnx-versal-virt generated device tree
3 participants