Comments (2)
There's 2 things here I think. Just defining best practice or .dts coding style. That would be good I think, but I don't think that belongs in the spec (though could be an appendix). This is also something tools can check, so I'd rather see tools for this first rather than an appendix for people to ignore.
We went down this path effectively trying to enforce some bracketing practice when dtschema relied on bracketing. There's a bunch of patches changing .dts files for that. That hit a roadblock in dtc when I tried to output brackets using the knowledge the dtc checks already has. That was needed when checking of DTBs was needed where we don't have any DTS and any and all bracketing is lost. Anyway, any checks of bracketing are gone, but I would like to see some separate tool do that and other things. A DTS linter essentially (which has come up before: devicetree-org/dt-schema#18).
The 2nd thing here sounds like generating #foo-cells based on brackets (or from phandles in the phandle+args style bindings). Like dtschema, that's probably a deadend in dtc. I think it falls into a larger topic of defining a higher level syntax than DTS (or DTSv2 maybe). The systemdt folks are doing some of this I think including just what you described. Take a look at lopper or talk to @zeddii perhaps.
from devicetree-specification.
I was doing the dishes and suddenly had this idea... things like this could be required in a theoretical /dts-v2/
, which we could perhaps open a meta discussion issue for.. Now that there are more eyes on shipping actual products with what we consider "proper" (a.k.a. in accordance to the upstream linux standards & dt-bindings) DTs that adhere to the backwards compatibility and ACPI (more-or-less-)equivalence, this could be a good forum for discussing possible evolutions.
There are some rough edges (like this one) that could be polished if things got less ambiguous, while retaining compatibility with what's here today. Another thing that immediately comes to mind is going little endian.
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
- 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.