Is your enhancement proposal related to a problem? Please describe.
DTS bindings are now available in zephyr documentation (https://docs.zephyrproject.org/latest/reference/devicetree/bindings.html)
and maintainers have a way to document these important pieces of driver configuration.
The last important missing piece of information is to indicate how a driver should be enabled, operation typically achieved using Kconfig flags.

This piece of info would would be missing to automatize generation of supported features in boards documentation (cf #29652).

One easy way to get this link would be to document drivers matching Kconfig flag in dts bindings flag directly.
But, as said @mbolivar-nordic: "kind of defeats the 'OS independent' goal for bindings IMO".

So I'm raising this issue in order to reach an agreement on how to document dts bindings Kconfig relation w/o breaking OS independent promises.