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

U96V2: Powersequence the Wifi chip on SD interface #18

Open
wants to merge 1 commit into
base: 2020.2
Choose a base branch
from

Conversation

ubfx
Copy link

@ubfx ubfx commented Apr 15, 2021

See #17

@ubfx ubfx closed this Apr 15, 2021
@ubfx ubfx deleted the sd_pwrseq_fix branch April 15, 2021 14:36
@ubfx ubfx restored the sd_pwrseq_fix branch April 15, 2021 14:38
@ubfx ubfx reopened this Apr 15, 2021
@ubfx ubfx changed the title Powersequence the Wifi chip on SD interface U96V2: Powersequence the Wifi chip on SD interface Apr 15, 2021
@narrucmot
Copy link
Contributor

Hi Felix,
Are these commits meant to fix an error you are seeing, or are you trying to eliminate a warning. This devicetree has been in use for a long time and with many versions of PetaLinux.

@ubfx
Copy link
Author

ubfx commented Apr 15, 2021

Hi,
I'm using these device trees with a custom linux yocto build. Without this power sequencing the wifi won't work (the Wifi chip wont turn on). It works on petalinux, because petalinux includes the devicetree of the first version of the Ultra96 [1]. If you look through that file you will see that the power sequencing happens there, which is why it's not needed in the u96v2 device tree when it's used as an extension of the v1 devicetree.

I think that the devicetree for the Ultra96v2 shouldn't be dependent on the one of the first board. It should work on its own.

[1] https://github.com/Xilinx/device-tree-xlnx/blob/master/device_tree/data/kernel_dtsi/2019.2/BOARD/avnet-ultra96-rev1.dtsi

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.

2 participants