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

dma-ranges null and not present not well defined #53

Open
wmamills opened this issue Feb 23, 2022 · 1 comment
Open

dma-ranges null and not present not well defined #53

wmamills opened this issue Feb 23, 2022 · 1 comment

Comments

@wmamills
Copy link

If a node has ranges but not dma-ranges what should be done?

  • assume same translation as ranges? assume 1:1 translation?

Likewise is dma-ranges is present but has no value, does that mean direct mapped even when there is a ranges present?

@robherring
Copy link
Member

While 'ranges' is required to translate and define memory mapped addresses, 'dma-ranges' is optional (or forgotten). Missing is 1:1 translation.

The translation is a bit different too. For 'ranges', a DT could have 1:1 translation or make the child nodes a relative offset and the result is the same. For dma-ranges, the cpu address, bus address and addressable size are all important to the software.

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

No branches or pull requests

2 participants