tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

docs: dt: submitting-patches: Document sending DTS patches

Document two rules already widely used and enforced by DT maintainers
and SoC platform maintainers:

1. DTS patches should be placed at the end of driver patchset to
indicate no dependencies of driver code on DTS.

2. DTS patches should be applied via SoC platform maintainers, because
it is a driver-independent hardware description. However some
driver maintainers are reluctant to pick up portions of patchsets and
prefer to take entire set at once. For such cases, the DTS portion
should be split into separate patchset, so it will not end up in the
driver subsystem integration tree.

Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Link: https://lore.kernel.org/r/20250225184822.213296-1-krzysztof.kozlowski@linaro.org
Signed-off-by: Rob Herring (Arm) <robh@kernel.org>

authored by

Krzysztof Kozlowski and committed by
Rob Herring (Arm) b31cc6af 2ac95560

+17 -2
+17 -2
Documentation/devicetree/bindings/submitting-patches.rst
··· 54 54 followed as of commit bff5da4335256513497cc8c79f9a9d1665e09864 55 55 ("checkpatch: add DT compatible string documentation checks"). ] 56 56 57 - 7) If a documented compatible string is not yet matched by the 57 + 7) DTS is treated in general as driver-independent hardware description, thus 58 + any DTS patches, regardless whether using existing or new bindings, should 59 + be placed at the end of patchset to indicate no dependency of drivers on 60 + the DTS. DTS will be anyway applied through separate tree or branch, so 61 + different order would indicate the serie is non-bisectable. 62 + 63 + If a driver subsystem maintainer prefers to apply entire set, instead of 64 + their relevant portion of patchset, please split the DTS patches into 65 + separate patchset with a reference in changelog or cover letter to the 66 + bindings submission on the mailing list. 67 + 68 + 8) If a documented compatible string is not yet matched by the 58 69 driver, the documentation should also include a compatible 59 70 string that is matched by the driver. 60 71 61 - 8) Bindings are actively used by multiple projects other than the Linux 72 + 9) Bindings are actively used by multiple projects other than the Linux 62 73 Kernel, extra care and consideration may need to be taken when making changes 63 74 to existing bindings. 64 75 ··· 89 78 90 79 3) For a series going though multiple trees, the binding patch should be 91 80 kept with the driver using the binding. 81 + 82 + 4) The DTS files should however never be applied via driver subsystem tree, 83 + but always via platform SoC trees on dedicated branches (see also 84 + Documentation/process/maintainer-soc.rst). 92 85 93 86 III. Notes 94 87 ==========