Comments (3)
Unrelated, and not sure I've read closely enough: Why is the interrupt parent unit address included in
interrupt-map
? The phandle already points to its node, so it seems redundant.
Hmm... think I get it now. It's just so that the parent specifier can recursively translated with the same logic as for e.g. gpio-map
, making it consistent. Might be nice to clarify that.
from devicetree-specification.
Can you submit a patch to fix this.
It's the child address that is part of the interrupt-map. I think the child address was primarily needed for PCI in some cases.
from devicetree-specification.
It's the child address that is part of the interrupt-map. I think the child address was primarily needed for PCI in some cases.
The parent address is included as well, in addition to the parent phandle:
interrupt-map:
...
child unit address: ...
child interrupt specifier: ...
interrupt-parent: <phandle>
parent unit address: The unit address in the domain of the interrupt parent. The number of 32-bit cells required to specify this address is described by the #address-cells property of the node pointed to by the interrupt-parent field.
parent interrupt specifier: ...
In the PCI example, #address-cells = <0>
for the parent though, so it disappears.
from devicetree-specification.
Related Issues (20)
- cpu node requirements don't match schema HOT 9
- Rewrite the specs in Kaitai Struct and generate the text docs from KS specs HOT 2
- Build latexpdf error HOT 1
- MIME type for DeviceTree dts files HOT 5
- Invalid MAC address in example HOT 1
- Memory terminology WIMG and VLE used w/o reference or definition HOT 3
- dma-ranges null and not present not well defined HOT 1
- This repo has both master and main branches HOT 3
- Interrupt tree example (current Fig 2.3) does not show in PDF HOT 8
- Generic node name for vibration motor / haptics HOT 1
- Provide more information about RAM from the bootloader HOT 6
- Enforce ARRAY_SIZE(property) == ARRAY_SIZE(property-names) HOT 2
- enhancement: addition of /delete-label/ HOT 3
- Codify array values syntax HOT 2
- Table 1: Revision History was not updated for Release v0.4 HOT 1
- WARNING: Invalid device tree, expect boot to fail | openbsd-current Firefly RK3399 ARM SoC HOT 3
- Architecture bindings? HOT 2
- Property inheritance HOT 6
- chapter2-devicetree-basics.rst refers to missing Appendix A HOT 1
- Usage of EfiReservedMemoryType
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from devicetree-specification.