doc: _scripts: gen_devicetree_rest: add link to driver sources #79259
+73
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When generating the documentation pages for the devicetree bindings, add a link to the .c file implementing the corresponding driver, or folder likely to contain the driver implementation, using heuristics to determine the most likely location of the driver sources. There's probably a few edge cases of drivers that aren't properly "guessed", but for the wide majority of bindings, this significantly improves the user experience when it comes to being able to quickly find the source code of the driver matching a given compatible.
As CI is running in "DT turbo mode" and hence not generating the docs for the DT bindings, you may check the result of this PR over at: https://builds.zephyrproject.io/zephyr/pr/79259-alt/html/build/dts/api/bindings.html