€•gjŒ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ŒPortuguese (Brazilian)”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ:/translations/pt_BR/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”“”)”}”(hXI 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, SCSI, SPI and UFS, expect reverse order of the prefixes, based on subsystem name:: ": dt-bindings: ..." The 80 characters of the subject are precious. It is recommended to not use "Documentation", "doc" or "YAML" because that is implied. All bindings are docs and all new bindings are supposed to be in Devicetree schema format. Repeating "binding" again should also be avoided, so for a new device it is often enough for example:: "dt-bindings: iio: adc: Add ROHM BD79100G" Conversion of other formats to DT schema:: "dt-bindings: iio: adc: adi,ad7476: Convert to DT schema" 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 series 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.”…””}”(hjh²hh³Nh“Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h’h³hĒh“K hhūubah}”(h]”h ]”h"]”h$]”h&]”uh1hłhhöubhś)”}”(hX@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, SCSI, SPI and UFS, expect reverse order of the prefixes, based on subsystem name:: ": dt-bindings: ..." The 80 characters of the subject are precious. It is recommended to not use "Documentation", "doc" or "YAML" because that is implied. All bindings are docs and all new bindings are supposed to be in Devicetree schema format. Repeating "binding" again should also be avoided, so for a new device it is often enough for example:: "dt-bindings: iio: adc: Add ROHM BD79100G" Conversion of other formats to DT schema:: "dt-bindings: iio: adc: adi,ad7476: Convert to DT schema" ”h]”(j)”}”(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: : ..."”…””}”hj)sbah}”(h]”h ]”h"]”h$]”h&]”hÅhĘuh1j'h³hĒh“Khjubj)”}”(hŒ€Few subsystems, like ASoC, media, regulators, SCSI, SPI and UFS, expect reverse order of the prefixes, based on subsystem name::”h]”hŒFew subsystems, like ASoC, media, regulators, SCSI, SPI and UFS, expect reverse order of the prefixes, based on subsystem name:”…””}”(hj7h²hh³Nh“Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h’h³hĒh“Khjubj()”}”(hŒ!": dt-bindings: ..."”h]”hŒ!": dt-bindings: ..."”…””}”hjEsbah}”(h]”h ]”h"]”h$]”h&]”hÅhĘuh1j'h³hĒh“Khjubj)”}”(hXHThe 80 characters of the subject are precious. It is recommended to not use "Documentation", "doc" or "YAML" because that is implied. All bindings are docs and all new bindings are supposed to be in Devicetree schema format. Repeating "binding" again should also be avoided, so for a new device it is often enough for example::”h]”hXWThe 80 characters of the subject are precious. It is recommended to not use ā€œDocumentationā€, ā€œdocā€ or ā€œYAMLā€ because that is implied. All bindings are docs and all new bindings are supposed to be in Devicetree schema format. Repeating ā€œbindingā€ again should also be avoided, so for a new device it is often enough for example:”…””}”(hjSh²hh³Nh“Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h’h³hĒh“Khjubj()”}”(hŒ*"dt-bindings: iio: adc: Add ROHM BD79100G"”h]”hŒ*"dt-bindings: iio: adc: Add ROHM BD79100G"”…””}”hjasbah}”(h]”h ]”h"]”h$]”h&]”hÅhĘuh1j'h³hĒh“Khjubj)”}”(hŒ*Conversion of other formats to DT schema::”h]”hŒ)Conversion of other formats to DT schema:”…””}”(hjoh²hh³Nh“Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h’h³hĒh“Khjubj()”}”(hŒ9"dt-bindings: iio: adc: adi,ad7476: Convert to DT schema"”h]”hŒ9"dt-bindings: iio: adc: adi,ad7476: Convert to DT schema"”…””}”hj}sbah}”(h]”h ]”h"]”h$]”h&]”hÅhĘuh1j'h³hĒh“K!hjubeh}”(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]”(j)”}”(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:”…””}”(hj•h²hh³Nh“Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h’h³hĒh“K#hj‘ubj()”}”(hŒmake dt_binding_check”h]”hŒmake dt_binding_check”…””}”hj£sbah}”(h]”h ]”h"]”h$]”h&]”hÅhĘuh1j'h³hĒh“K'hj‘ubj)”}”(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.”…””}”(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ŒgDT binding files should be dual licensed. The preferred license tag is (GPL-2.0-only OR BSD-2-Clause). ”h]”j)”}”(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]”(j)”}”(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]”j)”}”(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“K1hjļubah}”(h]”h ]”h"]”h$]”h&]”uh1hīh³hĒh“K1hjŻubj)”}”(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.”…””}”(hjh²hh³Nh“Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h’h³hĒh“K3hjŻ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]”j)”}”(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“K6hj(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]”j)”}”(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ā€). ]”…””}”(hjDh²hh³Nh“Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h’h³hĒh“K9hj@ubah}”(h]”h ]”h"]”h$]”h&]”uh1hłhhöubhś)”}”(hXeDTS 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 series 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]”(j)”}”(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 series is non-bisectable.”h]”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 series is non-bisectable.”…””}”(hj\h²hh³Nh“Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h’h³hĒh“KAhjXubj)”}”(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.”…””}”(hjjh²hh³Nh“Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h’h³hĒh“KGhjXubeh}”(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]”j)”}”(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.”…””}”(hj‚h²hh³Nh“Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h’h³hĒh“KLhj~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]”j)”}”(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“KPhj–ubah}”(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”…””}”(hjĖh²hh³Nh“Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hĶhjČh²hh³hĒh“KUubhļ)”}”(hXS1) 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 through 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]”j)”}”(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“KWhją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]”(j)”}”(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“K[hjųubj)”}”(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“K_hjųubeh}”(h]”h ]”h"]”h$]”h&]”uh1hłhjŻubhś)”}”(hŒoFor a series going through multiple trees, the binding patch should be kept with the driver using the binding. ”h]”j)”}”(hŒnFor a series going through multiple trees, the binding patch should be kept with the driver using the binding.”h]”hŒnFor a series going through 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“Kbhjubah}”(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]”j)”}”(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“Kehj6ubah}”(h]”h ]”h"]”h$]”h&]”uh1hłhjŻubeh}”(h]”h ]”h"]”h$]”h&]”j“jµj¶hj·jøuh1hōhjŁubah}”(h]”h ]”h"]”h$]”h&]”uh1hīh³hĒh“KWhjČh²hubeh}”(h]”Œii-for-kernel-maintainers”ah ]”h"]”Œii. for kernel maintainers”ah$]”h&]”uh1hČhhŹh²hh³hĒh“KUubhÉ)”}”(hhh]”(hĪ)”}”(hŒ III. Notes”h]”hŒ III. Notes”…””}”(hjeh²hh³Nh“Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hĶhjbh²hh³hĒh“Kjubhļ)”}”(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]”j)”}”(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“Klhjzubah}”(h]”h ]”h"]”h$]”h&]”uh1hłhjwubhś)”}”(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]”j)”}”(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.”…””}”(hj–h²hh³Nh“Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h’h³hĒh“Kohj’ubah}”(h]”h ]”h"]”h$]”h&]”uh1hłhjwubeh}”(h]”h ]”h"]”h$]”h&]”j“jµj¶hj·jøj¹Kuh1hōhjsubah}”(h]”h ]”h"]”h$]”h&]”uh1hīh³hĒh“Klhjbh²hubeh}”(h]”Œ iii-notes”ah ]”h"]”Œ iii. notes”ah$]”h&]”uh1hČhhŹh²hh³hĒh“Kjubeh}”(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_j\j»jøuŒ nametypes”}”(jƉjʼnj_‰j»‰uh}”(jĄhŹjĀhŻj\jČjøjbuŒ 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]”j)”}”(hŒ:Enumerated list start value not ordinal-1: "0" (ordinal 0)”h]”hŒ>Enumerated list start value not ordinal-1: ā€œ0ā€ (ordinal 0)”…””}”(hjPh²hh³Nh“Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h’hjMubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”ŒINFO”Œsource”hĒŒline”Kuh1jKhhšubjL)”}”(hhh]”j)”}”(hŒ:Enumerated list start value not ordinal-1: "0" (ordinal 0)”h]”hŒ>Enumerated list start value not ordinal-1: ā€œ0ā€ (ordinal 0)”…””}”(hjlh²hh³Nh“Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h’hjiubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”jfŒsource”hĒŒline”Kuh1jKhjsubeŒtransform_messages”]”Œ transformer”NŒ include_log”]”Œ decoration”Nh²hub.