At present it is possible to add invalid settings (e.g. a typo on the setting name) and this is not picked up by the chromeos-config-bsp ebuilds.

We have a binding for the master configuration [1] but we do not programatically validate against it.

Some work has been done to implement this:

https://lwn.net/Articles/568217/
http://events.linuxfoundation.org/sites/events/files/slides/ELC14-Device_Tree_validation_0.pdf
http://elinux.org/Device_tree_plumbers_2016_etherpad

But perhaps  we should consider a simple script written in Python for now? It could parse the README.md, or we could convert it to yaml or the format mentioned in the first article above.


[1] https://chromium.googlesource.com/chromiumos/platform2/+/refs/heads/master/chromeos-config/README.md