€•cŒsphinx.addnodes”Œdocument”“”)”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)”}”(hhh]”(hŒ pending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ:/translations/zh_CN/devicetree/bindings/submitting-patches”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ:/translations/zh_TW/devicetree/bindings/submitting-patches”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ:/translations/it_IT/devicetree/bindings/submitting-patches”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ:/translations/ja_JP/devicetree/bindings/submitting-patches”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ:/translations/ko_KR/devicetree/bindings/submitting-patches”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ:/translations/sp_SP/devicetree/bindings/submitting-patches”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ SPDX-License-Identifier: GPL-2.0”h]”hŒ SPDX-License-Identifier: GPL-2.0”…””}”hh£sbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1h¡hhhžhhŸŒT/var/lib/git/docbuild/linux/Documentation/devicetree/bindings/submitting-patches.rst”h KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ*Submitting Devicetree (DT) binding patches”h]”hŒ*Submitting Devicetree (DT) binding patches”…””}”(hh»hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hh¶hžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒI. For patch submitters”h]”hŒI. For patch submitters”…””}”(hhÌhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hhÉhžhhŸh³h KubhŒ block_quote”“”)”}”(hXü 0) Normal patch submission rules from Documentation/process/submitting-patches.rst applies. 1) The Documentation/ and include/dt-bindings/ portion of the patch should be a separate patch. The preferred subject prefix for binding patches is:: "dt-bindings: : ..." Few subsystems, like ASoC, media, regulators and SPI, expect reverse order of the prefixes:: ": dt-bindings: ..." The 80 characters of the subject are precious. It is recommended to not use "Documentation" or "doc" because that is implied. All bindings are docs. Repeating "binding" again should also be avoided. 2) DT binding files are written in DT schema format using json-schema vocabulary and YAML file format. The DT binding files must pass validation by running:: make dt_binding_check See Documentation/devicetree/bindings/writing-schema.rst for more details about schema and tools setup. 3) DT binding files should be dual licensed. The preferred license tag is (GPL-2.0-only OR BSD-2-Clause). 4) Submit the entire series to the devicetree mailinglist at devicetree@vger.kernel.org and Cc: the DT maintainers. Use scripts/get_maintainer.pl to identify all of the DT maintainers. 5) The Documentation/ portion of the patch should come in the series before the code implementing the binding. 6) Any compatible strings used in a chip or board DTS file must be previously documented in the corresponding DT binding file in Documentation/devicetree/bindings. This rule applies even if the Linux device driver does not yet match on the compatible string. [ checkpatch will emit warnings if this step is not followed as of commit bff5da4335256513497cc8c79f9a9d1665e09864 ("checkpatch: add DT compatible string documentation checks"). ] 7) DTS is treated in general as driver-independent hardware description, thus any DTS patches, regardless whether using existing or new bindings, should be placed at the end of patchset to indicate no dependency of drivers on the DTS. DTS will be anyway applied through separate tree or branch, so different order would indicate the serie is non-bisectable. If a driver subsystem maintainer prefers to apply entire set, instead of their relevant portion of patchset, please split the DTS patches into separate patchset with a reference in changelog or cover letter to the bindings submission on the mailing list. 8) If a documented compatible string is not yet matched by the driver, the documentation should also include a compatible string that is matched by the driver. 9) Bindings are actively used by multiple projects other than the Linux Kernel, extra care and consideration may need to be taken when making changes to existing bindings. ”h]”hŒenumerated_list”“”)”}”(hhh]”(hŒ list_item”“”)”}”(hŒYNormal patch submission rules from Documentation/process/submitting-patches.rst applies. ”h]”hŒ paragraph”“”)”}”(hŒXNormal patch submission rules from Documentation/process/submitting-patches.rst applies.”h]”hŒXNormal patch submission rules from Documentation/process/submitting-patches.rst applies.”…””}”(hhíhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h K hhçubah}”(h]”h ]”h"]”h$]”h&]”uh1håhhâubhæ)”}”(hXThe Documentation/ and include/dt-bindings/ portion of the patch should be a separate patch. The preferred subject prefix for binding patches is:: "dt-bindings: : ..." Few subsystems, like ASoC, media, regulators and SPI, expect reverse order of the prefixes:: ": dt-bindings: ..." The 80 characters of the subject are precious. It is recommended to not use "Documentation" or "doc" because that is implied. All bindings are docs. Repeating "binding" again should also be avoided. ”h]”(hì)”}”(hŒ’The Documentation/ and include/dt-bindings/ portion of the patch should be a separate patch. The preferred subject prefix for binding patches is::”h]”hŒ‘The Documentation/ and include/dt-bindings/ portion of the patch should be a separate patch. The preferred subject prefix for binding patches is:”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h K hjubhŒ literal_block”“”)”}”(hŒ!"dt-bindings: : ..."”h]”hŒ!"dt-bindings: : ..."”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jhŸh³h Khjubhì)”}”(hŒ\Few subsystems, like ASoC, media, regulators and SPI, expect reverse order of the prefixes::”h]”hŒ[Few subsystems, like ASoC, media, regulators and SPI, expect reverse order of the prefixes:”…””}”(hj#hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h Khjubj)”}”(hŒ!": dt-bindings: ..."”h]”hŒ!": dt-bindings: ..."”…””}”hj1sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jhŸh³h Khjubhì)”}”(hŒÆThe 80 characters of the subject are precious. It is recommended to not use "Documentation" or "doc" because that is implied. All bindings are docs. Repeating "binding" again should also be avoided.”h]”hŒÒThe 80 characters of the subject are precious. It is recommended to not use “Documentation†or “doc†because that is implied. All bindings are docs. Repeating “binding†again should also be avoided.”…””}”(hj?hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h Khjubeh}”(h]”h ]”h"]”h$]”h&]”uh1håhhâubhæ)”}”(hXDT binding files are written in DT schema format using json-schema vocabulary and YAML file format. The DT binding files must pass validation by running:: make dt_binding_check See Documentation/devicetree/bindings/writing-schema.rst for more details about schema and tools setup. ”h]”(hì)”}”(hŒšDT binding files are written in DT schema format using json-schema vocabulary and YAML file format. The DT binding files must pass validation by running::”h]”hŒ™DT binding files are written in DT schema format using json-schema vocabulary and YAML file format. The DT binding files must pass validation by running:”…””}”(hjWhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h KhjSubj)”}”(hŒmake dt_binding_check”h]”hŒmake dt_binding_check”…””}”hjesbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jhŸh³h KhjSubhì)”}”(hŒgSee Documentation/devicetree/bindings/writing-schema.rst for more details about schema and tools setup.”h]”hŒgSee Documentation/devicetree/bindings/writing-schema.rst for more details about schema and tools setup.”…””}”(hjshžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h K!hjSubeh}”(h]”h ]”h"]”h$]”h&]”uh1håhhâubhæ)”}”(hŒgDT binding files should be dual licensed. The preferred license tag is (GPL-2.0-only OR BSD-2-Clause). ”h]”hì)”}”(hŒfDT binding files should be dual licensed. The preferred license tag is (GPL-2.0-only OR BSD-2-Clause).”h]”hŒfDT binding files should be dual licensed. The preferred license tag is (GPL-2.0-only OR BSD-2-Clause).”…””}”(hj‹hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h K$hj‡ubah}”(h]”h ]”h"]”h$]”h&]”uh1håhhâubhæ)”}”(hŒºSubmit the entire series to the devicetree mailinglist at devicetree@vger.kernel.org and Cc: the DT maintainers. Use scripts/get_maintainer.pl to identify all of the DT maintainers. ”h]”(hì)”}”(hŒ9Submit the entire series to the devicetree mailinglist at”h]”hŒ9Submit the entire series to the devicetree mailinglist at”…””}”(hj£hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h K'hjŸubhÛ)”}”(hŒdevicetree@vger.kernel.org ”h]”hì)”}”(hŒdevicetree@vger.kernel.org”h]”hŒ reference”“”)”}”(hj·h]”hŒdevicetree@vger.kernel.org”…””}”(hj»hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œ!mailto:devicetree@vger.kernel.org”uh1j¹hjµubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h K)hj±ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K)hjŸubhì)”}”(hŒ`and Cc: the DT maintainers. Use scripts/get_maintainer.pl to identify all of the DT maintainers.”h]”hŒ`and Cc: the DT maintainers. Use scripts/get_maintainer.pl to identify all of the DT maintainers.”…””}”(hjÖhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h K+hjŸubeh}”(h]”h ]”h"]”h$]”h&]”uh1håhhâubhæ)”}”(hŒlThe Documentation/ portion of the patch should come in the series before the code implementing the binding. ”h]”hì)”}”(hŒkThe Documentation/ portion of the patch should come in the series before the code implementing the binding.”h]”hŒkThe Documentation/ portion of the patch should come in the series before the code implementing the binding.”…””}”(hjîhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h K.hjêubah}”(h]”h ]”h"]”h$]”h&]”uh1håhhâubhæ)”}”(hX¶Any compatible strings used in a chip or board DTS file must be previously documented in the corresponding DT binding file in Documentation/devicetree/bindings. This rule applies even if the Linux device driver does not yet match on the compatible string. [ checkpatch will emit warnings if this step is not followed as of commit bff5da4335256513497cc8c79f9a9d1665e09864 ("checkpatch: add DT compatible string documentation checks"). ] ”h]”hì)”}”(hXµAny compatible strings used in a chip or board DTS file must be previously documented in the corresponding DT binding file in Documentation/devicetree/bindings. This rule applies even if the Linux device driver does not yet match on the compatible string. [ checkpatch will emit warnings if this step is not followed as of commit bff5da4335256513497cc8c79f9a9d1665e09864 ("checkpatch: add DT compatible string documentation checks"). ]”h]”hX¹Any compatible strings used in a chip or board DTS file must be previously documented in the corresponding DT binding file in Documentation/devicetree/bindings. This rule applies even if the Linux device driver does not yet match on the compatible string. [ checkpatch will emit warnings if this step is not followed as of commit bff5da4335256513497cc8c79f9a9d1665e09864 (“checkpatch: add DT compatible string documentation checksâ€). ]”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h K1hjubah}”(h]”h ]”h"]”h$]”h&]”uh1håhhâubhæ)”}”(hXdDTS is treated in general as driver-independent hardware description, thus any DTS patches, regardless whether using existing or new bindings, should be placed at the end of patchset to indicate no dependency of drivers on the DTS. DTS will be anyway applied through separate tree or branch, so different order would indicate the serie is non-bisectable. If a driver subsystem maintainer prefers to apply entire set, instead of their relevant portion of patchset, please split the DTS patches into separate patchset with a reference in changelog or cover letter to the bindings submission on the mailing list. ”h]”(hì)”}”(hXcDTS is treated in general as driver-independent hardware description, thus any DTS patches, regardless whether using existing or new bindings, should be placed at the end of patchset to indicate no dependency of drivers on the DTS. DTS will be anyway applied through separate tree or branch, so different order would indicate the serie is non-bisectable.”h]”hXcDTS is treated in general as driver-independent hardware description, thus any DTS patches, regardless whether using existing or new bindings, should be placed at the end of patchset to indicate no dependency of drivers on the DTS. DTS will be anyway applied through separate tree or branch, so different order would indicate the serie is non-bisectable.”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h K9hjubhì)”}”(hŒþIf a driver subsystem maintainer prefers to apply entire set, instead of their relevant portion of patchset, please split the DTS patches into separate patchset with a reference in changelog or cover letter to the bindings submission on the mailing list.”h]”hŒþIf a driver subsystem maintainer prefers to apply entire set, instead of their relevant portion of patchset, please split the DTS patches into separate patchset with a reference in changelog or cover letter to the bindings submission on the mailing list.”…””}”(hj,hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h K?hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1håhhâubhæ)”}”(hŒIf a documented compatible string is not yet matched by the driver, the documentation should also include a compatible string that is matched by the driver. ”h]”hì)”}”(hŒœIf a documented compatible string is not yet matched by the driver, the documentation should also include a compatible string that is matched by the driver.”h]”hŒœIf a documented compatible string is not yet matched by the driver, the documentation should also include a compatible string that is matched by the driver.”…””}”(hjDhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h KDhj@ubah}”(h]”h ]”h"]”h$]”h&]”uh1håhhâubhæ)”}”(hŒ©Bindings are actively used by multiple projects other than the Linux Kernel, extra care and consideration may need to be taken when making changes to existing bindings. ”h]”hì)”}”(hŒ¨Bindings are actively used by multiple projects other than the Linux Kernel, extra care and consideration may need to be taken when making changes to existing bindings.”h]”hŒ¨Bindings are actively used by multiple projects other than the Linux Kernel, extra care and consideration may need to be taken when making changes to existing bindings.”…””}”(hj\hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h KHhjXubah}”(h]”h ]”h"]”h$]”h&]”uh1håhhâubeh}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œarabic”Œprefix”hŒsuffix”Œ)”Œstart”Kuh1hàhhÜubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K hhÉhžhubeh}”(h]”Œi-for-patch-submitters”ah ]”h"]”Œi. for patch submitters”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒII. For kernel maintainers”h]”hŒII. For kernel maintainers”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjŠhžhhŸh³h KMubhÛ)”}”(hXR1) If you aren't comfortable reviewing a given binding, reply to it and ask the devicetree maintainers for guidance. This will help them prioritize which ones to review and which ones are ok to let go. 2) For driver (not subsystem) bindings: If you are comfortable with the binding, and it hasn't received an Acked-by from the devicetree maintainers after a few weeks, go ahead and take it. For subsystem bindings (anything affecting more than a single device), getting a devicetree maintainer to review it is required. 3) For a series going though multiple trees, the binding patch should be kept with the driver using the binding. 4) The DTS files should however never be applied via driver subsystem tree, but always via platform SoC trees on dedicated branches (see also Documentation/process/maintainer-soc.rst). ”h]”há)”}”(hhh]”(hæ)”}”(hŒÈIf you aren't comfortable reviewing a given binding, reply to it and ask the devicetree maintainers for guidance. This will help them prioritize which ones to review and which ones are ok to let go. ”h]”hì)”}”(hŒÇIf you aren't comfortable reviewing a given binding, reply to it and ask the devicetree maintainers for guidance. This will help them prioritize which ones to review and which ones are ok to let go.”h]”hŒÉIf you aren’t comfortable reviewing a given binding, reply to it and ask the devicetree maintainers for guidance. This will help them prioritize which ones to review and which ones are ok to let go.”…””}”(hj¦hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h KOhj¢ubah}”(h]”h ]”h"]”h$]”h&]”uh1håhjŸubhæ)”}”(hX<For driver (not subsystem) bindings: If you are comfortable with the binding, and it hasn't received an Acked-by from the devicetree maintainers after a few weeks, go ahead and take it. For subsystem bindings (anything affecting more than a single device), getting a devicetree maintainer to review it is required. ”h]”(hì)”}”(hŒ¹For driver (not subsystem) bindings: If you are comfortable with the binding, and it hasn't received an Acked-by from the devicetree maintainers after a few weeks, go ahead and take it.”h]”hŒ»For driver (not subsystem) bindings: If you are comfortable with the binding, and it hasn’t received an Acked-by from the devicetree maintainers after a few weeks, go ahead and take it.”…””}”(hj¾hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h KShjºubhì)”}”(hŒ€For subsystem bindings (anything affecting more than a single device), getting a devicetree maintainer to review it is required.”h]”hŒ€For subsystem bindings (anything affecting more than a single device), getting a devicetree maintainer to review it is required.”…””}”(hjÌhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h KWhjºubeh}”(h]”h ]”h"]”h$]”h&]”uh1håhjŸubhæ)”}”(hŒnFor a series going though multiple trees, the binding patch should be kept with the driver using the binding. ”h]”hì)”}”(hŒmFor a series going though multiple trees, the binding patch should be kept with the driver using the binding.”h]”hŒmFor a series going though multiple trees, the binding patch should be kept with the driver using the binding.”…””}”(hjähžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h KZhjàubah}”(h]”h ]”h"]”h$]”h&]”uh1håhjŸubhæ)”}”(hŒ¶The DTS files should however never be applied via driver subsystem tree, but always via platform SoC trees on dedicated branches (see also Documentation/process/maintainer-soc.rst). ”h]”hì)”}”(hŒµThe DTS files should however never be applied via driver subsystem tree, but always via platform SoC trees on dedicated branches (see also Documentation/process/maintainer-soc.rst).”h]”hŒµThe DTS files should however never be applied via driver subsystem tree, but always via platform SoC trees on dedicated branches (see also Documentation/process/maintainer-soc.rst).”…””}”(hjühžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h K]hjøubah}”(h]”h ]”h"]”h$]”h&]”uh1håhjŸubeh}”(h]”h ]”h"]”h$]”h&]”jvjwjxhjyjzuh1hàhj›ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KOhjŠhžhubeh}”(h]”Œii-for-kernel-maintainers”ah ]”h"]”Œii. for kernel maintainers”ah$]”h&]”uh1h´hh¶hžhhŸh³h KMubhµ)”}”(hhh]”(hº)”}”(hŒ III. Notes”h]”hŒ III. Notes”…””}”(hj'hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj$hžhhŸh³h KbubhÛ)”}”(hX|0) Please see Documentation/devicetree/bindings/ABI.rst for details regarding devicetree ABI. 1) This document is intended as a general familiarization with the process as decided at the 2013 Kernel Summit. When in doubt, the current word of the devicetree maintainers overrules this document. In that situation, a patch updating this document would be appreciated.”h]”há)”}”(hhh]”(hæ)”}”(hŒ[Please see Documentation/devicetree/bindings/ABI.rst for details regarding devicetree ABI. ”h]”hì)”}”(hŒZPlease see Documentation/devicetree/bindings/ABI.rst for details regarding devicetree ABI.”h]”hŒZPlease see Documentation/devicetree/bindings/ABI.rst for details regarding devicetree ABI.”…””}”(hj@hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h Kdhj<ubah}”(h]”h ]”h"]”h$]”h&]”uh1håhj9ubhæ)”}”(hXThis document is intended as a general familiarization with the process as decided at the 2013 Kernel Summit. When in doubt, the current word of the devicetree maintainers overrules this document. In that situation, a patch updating this document would be appreciated.”h]”hì)”}”(hXThis document is intended as a general familiarization with the process as decided at the 2013 Kernel Summit. When in doubt, the current word of the devicetree maintainers overrules this document. In that situation, a patch updating this document would be appreciated.”h]”hXThis document is intended as a general familiarization with the process as decided at the 2013 Kernel Summit. When in doubt, the current word of the devicetree maintainers overrules this document. In that situation, a patch updating this document would be appreciated.”…””}”(hjXhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhŸh³h KghjTubah}”(h]”h ]”h"]”h$]”h&]”uh1håhj9ubeh}”(h]”h ]”h"]”h$]”h&]”jvjwjxhjyjzj{Kuh1hàhj5ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Kdhj$hžhubeh}”(h]”Œ iii-notes”ah ]”h"]”Œ iii. notes”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kbubeh}”(h]”Œ(submitting-devicetree-dt-binding-patches”ah ]”h"]”Œ*submitting devicetree (dt) binding patches”ah$]”h&]”uh1h´hhhžhhŸh³h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h³uh1hŒcurrent_source”NŒ current_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¹NŒ generator”NŒ datestamp”NŒ source_link”NŒ source_url”NŒ toc_backlinks”Œentry”Œfootnote_backlinks”KŒ sectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒ strip_classes”NŒ report_level”KŒ halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ traceback”ˆŒinput_encoding”Œ utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”j«Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œ language_code”Œen”Œrecord_dependencies”NŒconfig”NŒ id_prefix”hŒauto_id_prefix”Œid”Œ dump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h³Œ _destination”NŒ _config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒ raw_enabled”KŒline_length_limit”M'Œpep_references”NŒ pep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒ rfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œ smart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œ docinfo_xform”KŒsectsubtitle_xform”‰Œ image_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(j…j‚j‡j„j!jj}jzuŒ nametypes”}”(j…‰j‡‰j!‰j}‰uh}”(j‚h¶j„hÉjjŠjzj$uŒ footnote_refs”}”Œ citation_refs”}”Œ autofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ footnotes”]”Œ citations”]”Œautofootnote_start”KŒsymbol_footnote_start”KŒ id_counter”Œ collections”ŒCounter”“”}”…”R”Œparse_messages”]”(hŒsystem_message”“”)”}”(hhh]”hì)”}”(hŒ:Enumerated list start value not ordinal-1: "0" (ordinal 0)”h]”hŒ>Enumerated list start value not ordinal-1: “0†(ordinal 0)”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhjubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”ŒINFO”Œsource”h³Œline”Kuh1j hhÜubj)”}”(hhh]”hì)”}”(hŒ:Enumerated list start value not ordinal-1: "0" (ordinal 0)”h]”hŒ>Enumerated list start value not ordinal-1: “0†(ordinal 0)”…””}”(hj.hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëhj+ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j(Œsource”h³Œline”Kuh1j hj5ubeŒtransform_messages”]”Œ transformer”NŒ include_log”]”Œ decoration”Nhžhub.