summaryrefslogtreecommitdiff
path: root/scripts/stackusage
diff options
context:
space:
mode:
authorKrzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>2026-04-27 19:07:40 +0300
committerRob Herring (Arm) <robh@kernel.org>2026-05-05 18:40:08 +0300
commitcdd5ffcec0dd8320969623e3acd36811bc05852a (patch)
treee78aeb9e4ee4c7c93af538d9acc271587b3c3078 /scripts/stackusage
parent63353810c08499476efc1e1e85ca7b8e33d54ef7 (diff)
downloadlinux-cdd5ffcec0dd8320969623e3acd36811bc05852a.tar.xz
docs: dt: writing-bindings: Extend compatible fallbacks guideline
Extend the guidelines when to use fallback compatibles to cover to common review responses. Devices are most likely compatible and should use fallbacks when having: 1. Compatible programming interface, meaning one is a subset, and Linux device drivers can use the subset to correctly match/bind and still operate with the subset features. 2. Device variant discovery through some means, like registers. Devices are incompatible and fallback is not suitable when that fallback cannot be used by the drivers to match/bind. In the same time commit message should clearly explain when the code suggests devices are compatible, but the binding does not define them as such. Acked-by: Conor Dooley <conor.dooley@microchip.com> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com> Link: https://patch.msgid.link/20260427160739.175451-2-krzysztof.kozlowski@oss.qualcomm.com Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
Diffstat (limited to 'scripts/stackusage')
0 files changed, 0 insertions, 0 deletions