Hello,
The VSC plugin is showing squiggles for SPI related nodes which are valid. (compile with no errors)
Here is an example:
Here is the error message
Thanks
Hello,
The VSC plugin is showing squiggles for SPI related nodes which are valid. (compile with no errors)
Here is an example:
Here is the error message
Thanks
I don't believe there is anything in the devicetree-language that requires the "compatible" field. Basically this is requiring all devices to have a device driver. I would like to use the devicetree structure to describe the interface but communicate with the SPI device directly without the need for a driver.
I don't believe there is anything in the devicetree-language that requires the "compatible" field. Basically this is requiring all devices to have a device driver. I would like to use the devicetree structure to describe the interface but communicate with the SPI device directly without the need for a driver.
I talked to the developer and got some more insight. The statement I wrote about the DT language is not correct. However, in the DT extension we mark stuff that "should" be done, as errors. The reason you got the squiggly red lines, is because the extension expect it to be set according to https://docs.zephyrproject.org/latest/guides/dts/bindings.html#on-bus.
In your case, you can just ignore the error.
Would it be possible to flag this an a warning vs. an error? Also, could we make the error message more useful? Something like 'warning missing "compatible" element'
Thanks for the input, I'll forward it to the developers working with the extension.
I forwarded this to the developer, and he is actually working on this. It should be fixed in the January release.