Link: https://lore.kernel.org/r/20260217200002.683975158@linuxfoundation.org Tested-by: Florian Fainelli <florian.fainelli@broadcom.com> Tested-by: Takeshi Ogasawara <takeshi.ogasawara@futuring-girl.com> Tested-by: Peter Schneider <pschneider1968@googlemail.com> Tested-by: Jon Hunter <jonathanh@nvidia.com> Tested-by: Salvatore Bonaccorso <carnil@debian.org> Tested-by: Brett A C Sheffield <bacs@librecast.net> Tested-by: Mark Brown <broonie@kernel.org> Tested-by: Luna Jernberg <droidbittin@gmail.com> Tested-by: Ronald Warsow <rwarsow@gmx.de> Tested-by: Justin M. Forbes <jforbes@fedoraproject.org> Tested-by: Ron Economos <re@w6rz.net> Tested-by: Miguel Ojeda <ojeda@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
27 lines
1.1 KiB
ReStructuredText
27 lines
1.1 KiB
ReStructuredText
.. SPDX-License-Identifier: GPL-2.0
|
|
|
|
==============================================
|
|
SoC Platforms with DTS Compliance Requirements
|
|
==============================================
|
|
|
|
Overview
|
|
--------
|
|
|
|
SoC platforms or subarchitectures should follow all the rules from
|
|
Documentation/process/maintainer-soc.rst. This document referenced in
|
|
MAINTAINERS impose additional requirements listed below.
|
|
|
|
Strict DTS DT Schema and dtc Compliance
|
|
---------------------------------------
|
|
|
|
No changes to the SoC platform Devicetree sources (DTS files) should introduce
|
|
new ``make dtbs_check W=1`` warnings. Warnings in a new board DTS, which are
|
|
results of issues in an included DTSI file, are considered existing, not new
|
|
warnings. For series split between different trees (DT bindings go via driver
|
|
subsystem tree), warnings on linux-next are decisive. The platform maintainers
|
|
have automation in place which should point out any new warnings.
|
|
|
|
If a commit introducing new warnings gets accepted somehow, the resulting
|
|
issues shall be fixed in reasonable time (e.g. within one release) or the
|
|
commit reverted.
|