€•GL      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ6/translations/zh_CN/driver-api/thermal/cpu-cooling-api”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ6/translations/zh_TW/driver-api/thermal/cpu-cooling-api”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ6/translations/it_IT/driver-api/thermal/cpu-cooling-api”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ6/translations/ja_JP/driver-api/thermal/cpu-cooling-api”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ6/translations/ko_KR/driver-api/thermal/cpu-cooling-api”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ6/translations/sp_SP/driver-api/thermal/cpu-cooling-api”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒCPU cooling APIs How To”h]”hŒCPU cooling APIs How To”…””}”(hh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒP/var/lib/git/docbuild/linux/Documentation/driver-api/thermal/cpu-cooling-api.rst”h KubhŒ	paragraph”“”)”}”(hŒ8Written by Amit Daniel Kachhap <amit.kachhap@linaro.org>”h]”(hŒ Written by Amit Daniel Kachhap <”…””}”(hh¹hžhhŸNh NubhŒ	reference”“”)”}”(hŒamit.kachhap@linaro.org”h]”hŒamit.kachhap@linaro.org”…””}”(hhÃhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:amit.kachhap@linaro.org”uh1hÁhh¹ubhŒ>”…””}”(hh¹hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubh¸)”}”(hŒUpdated: 6 Jan 2015”h]”hŒUpdated: 6 Jan 2015”…””}”(hhÝhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubh¸)”}”(hŒHCopyright (c)  2012 Samsung Electronics Co., Ltd(http://www.samsung.com)”h]”(hŒ1Copyright (c)  2012 Samsung Electronics Co., Ltd(”…””}”(hhëhžhhŸNh NubhÂ)”}”(hŒhttp://www.samsung.com”h]”hŒhttp://www.samsung.com”…””}”(hhóhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”hõuh1hÁhhëubhŒ)”…””}”(hhëhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K	hh£hžhubh¢)”}”(hhh]”(h§)”}”(hŒ0. Introduction”h]”hŒ0. Introduction”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj  hžhhŸh¶h Kubh¸)”}”(hŒäThe generic cpu cooling(freq clipping) provides registration/unregistration APIs
to the caller. The binding of the cooling devices to the trip point is left for
the user. The registration APIs returns the cooling device pointer.”h]”hŒäThe generic cpu cooling(freq clipping) provides registration/unregistration APIs
to the caller. The binding of the cooling devices to the trip point is left for
the user. The registration APIs returns the cooling device pointer.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khj  hžhubeh}”(h]”Œintroduction”ah ]”h"]”Œ0. introduction”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒ1. cpu cooling APIs”h]”hŒ1. cpu cooling APIs”…””}”(hj6  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj3  hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒ,1.1 cpufreq registration/unregistration APIs”h]”hŒ,1.1 cpufreq registration/unregistration APIs”…””}”(hjG  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjD  hžhhŸh¶h KubhŒblock_quote”“”)”}”(hX¹   ::

     struct thermal_cooling_device
     *cpufreq_cooling_register(struct cpumask *clip_cpus)

 This interface function registers the cpufreq cooling device with the name
 "thermal-cpufreq-%x". This api can support multiple instances of cpufreq
 cooling devices.

clip_cpus:
     cpumask of cpus where the frequency constraints will happen.

 ::

     struct thermal_cooling_device
     *of_cpufreq_cooling_register(struct cpufreq_policy *policy)

 This interface function registers the cpufreq cooling device with
 the name "thermal-cpufreq-%x" linking it with a device tree node, in
 order to bind it via the thermal DT code. This api can support multiple
 instances of cpufreq cooling devices.

 policy:
     CPUFreq policy.


 ::

     void cpufreq_cooling_unregister(struct thermal_cooling_device *cdev)

 This interface function unregisters the "thermal-cpufreq-%x" cooling device.

 cdev: Cooling device pointer which has to be unregistered.
”h]”(jV  )”}”(hX  ::

    struct thermal_cooling_device
    *cpufreq_cooling_register(struct cpumask *clip_cpus)

This interface function registers the cpufreq cooling device with the name
"thermal-cpufreq-%x". This api can support multiple instances of cpufreq
cooling devices.
”h]”(hŒliteral_block”“”)”}”(hŒRstruct thermal_cooling_device
*cpufreq_cooling_register(struct cpumask *clip_cpus)”h]”hŒRstruct thermal_cooling_device
*cpufreq_cooling_register(struct cpumask *clip_cpus)”…””}”hja  sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1j_  hŸh¶h Khj[  ubh¸)”}”(hŒ¤This interface function registers the cpufreq cooling device with the name
"thermal-cpufreq-%x". This api can support multiple instances of cpufreq
cooling devices.”h]”hŒ¨This interface function registers the cpufreq cooling device with the name
â€œthermal-cpufreq-%xâ€. This api can support multiple instances of cpufreq
cooling devices.”…””}”(hjq  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khj[  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jU  hŸh¶h KhjW  ubhŒdefinition_list”“”)”}”(hhh]”hŒdefinition_list_item”“”)”}”(hXŸ  clip_cpus:
    cpumask of cpus where the frequency constraints will happen.

::

    struct thermal_cooling_device
    *of_cpufreq_cooling_register(struct cpufreq_policy *policy)

This interface function registers the cpufreq cooling device with
the name "thermal-cpufreq-%x" linking it with a device tree node, in
order to bind it via the thermal DT code. This api can support multiple
instances of cpufreq cooling devices.

policy:
    CPUFreq policy.


::

    void cpufreq_cooling_unregister(struct thermal_cooling_device *cdev)

This interface function unregisters the "thermal-cpufreq-%x" cooling device.

cdev: Cooling device pointer which has to be unregistered.
”h]”(hŒterm”“”)”}”(hŒ
clip_cpus:”h]”hŒ
clip_cpus:”…””}”(hj’  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh¶h K8hjŒ  ubhŒ
definition”“”)”}”(hhh]”(jV  )”}”(hŒ=cpumask of cpus where the frequency constraints will happen.
”h]”h¸)”}”(hŒ<cpumask of cpus where the frequency constraints will happen.”h]”hŒ<cpumask of cpus where the frequency constraints will happen.”…””}”(hj©  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K"hj¥  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jU  hŸh¶h K"hj¢  ubj`  )”}”(hŒYstruct thermal_cooling_device
*of_cpufreq_cooling_register(struct cpufreq_policy *policy)”h]”hŒYstruct thermal_cooling_device
*of_cpufreq_cooling_register(struct cpufreq_policy *policy)”…””}”hj½  sbah}”(h]”h ]”h"]”h$]”h&]”jo  jp  uh1j_  hŸh¶h K&hj¢  ubh¸)”}”(hŒôThis interface function registers the cpufreq cooling device with
the name "thermal-cpufreq-%x" linking it with a device tree node, in
order to bind it via the thermal DT code. This api can support multiple
instances of cpufreq cooling devices.”h]”hŒøThis interface function registers the cpufreq cooling device with
the name â€œthermal-cpufreq-%xâ€ linking it with a device tree node, in
order to bind it via the thermal DT code. This api can support multiple
instances of cpufreq cooling devices.”…””}”(hjË  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K)hj¢  ubj†  )”}”(hhh]”j‹  )”}”(hŒpolicy:
CPUFreq policy.

”h]”(j‘  )”}”(hŒpolicy:”h]”hŒpolicy:”…””}”(hjà  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh¶h K0hjÜ  ubj¡  )”}”(hhh]”h¸)”}”(hŒCPUFreq policy.”h]”hŒCPUFreq policy.”…””}”(hjñ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K/hjî  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j   hjÜ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jŠ  hŸh¶h K0hjÙ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j…  hj¢  ubj`  )”}”(hŒDvoid cpufreq_cooling_unregister(struct thermal_cooling_device *cdev)”h]”hŒDvoid cpufreq_cooling_unregister(struct thermal_cooling_device *cdev)”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”jo  jp  uh1j_  hŸh¶h K4hj¢  ubh¸)”}”(hŒLThis interface function unregisters the "thermal-cpufreq-%x" cooling device.”h]”hŒPThis interface function unregisters the â€œthermal-cpufreq-%xâ€ cooling device.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K6hj¢  ubh¸)”}”(hŒ:cdev: Cooling device pointer which has to be unregistered.”h]”hŒ:cdev: Cooling device pointer which has to be unregistered.”…””}”(hj-  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K8hj¢  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j   hjŒ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jŠ  hŸh¶h K8hj‡  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j…  hjW  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jU  hŸh¶h KhjD  hžhubeh}”(h]”Œ(cpufreq-registration-unregistration-apis”ah ]”h"]”Œ,1.1 cpufreq registration/unregistration apis”ah$]”h&]”uh1h¡hj3  hžhhŸh¶h Kubeh}”(h]”Œcpu-cooling-apis”ah ]”h"]”Œ1. cpu cooling apis”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒ2. Power models”h]”hŒ2. Power models”…””}”(hjf  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjc  hžhhŸh¶h K;ubh¸)”}”(hXÜ  The power API registration functions provide a simple power model for
CPUs.  The current power is calculated as dynamic power (static power isn't
supported currently).  This power model requires that the operating-points of
the CPUs are registered using the kernel's opp library and the
`cpufreq_frequency_table` is assigned to the `struct device` of the
cpu.  If you are using CONFIG_CPUFREQ_DT then the
`cpufreq_frequency_table` should already be assigned to the cpu
device.”h]”(hX#  The power API registration functions provide a simple power model for
CPUs.  The current power is calculated as dynamic power (static power isnâ€™t
supported currently).  This power model requires that the operating-points of
the CPUs are registered using the kernelâ€™s opp library and the
”…””}”(hjt  hžhhŸNh NubhŒtitle_reference”“”)”}”(hŒ`cpufreq_frequency_table`”h]”hŒcpufreq_frequency_table”…””}”(hj~  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j|  hjt  ubhŒ is assigned to the ”…””}”(hjt  hžhhŸNh Nubj}  )”}”(hŒ`struct device`”h]”hŒstruct device”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j|  hjt  ubhŒ: of the
cpu.  If you are using CONFIG_CPUFREQ_DT then the
”…””}”(hjt  hžhhŸNh Nubj}  )”}”(hŒ`cpufreq_frequency_table`”h]”hŒcpufreq_frequency_table”…””}”(hj¢  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j|  hjt  ubhŒ. should already be assigned to the cpu
device.”…””}”(hjt  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K=hjc  hžhubh¸)”}”(hŒƒThe dynamic power consumption of a processor depends on many factors.
For a given processor implementation the primary factors are:”h]”hŒƒThe dynamic power consumption of a processor depends on many factors.
For a given processor implementation the primary factors are:”…””}”(hjº  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KFhjc  hžhubhŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒºThe time the processor spends running, consuming dynamic power, as
compared to the time in idle states where dynamic consumption is
negligible.  Herein we refer to this as 'utilisation'.”h]”h¸)”}”(hŒºThe time the processor spends running, consuming dynamic power, as
compared to the time in idle states where dynamic consumption is
negligible.  Herein we refer to this as 'utilisation'.”h]”hŒ¾The time the processor spends running, consuming dynamic power, as
compared to the time in idle states where dynamic consumption is
negligible.  Herein we refer to this as â€˜utilisationâ€™.”…””}”(hjÓ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KIhjÏ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÍ  hjÊ  hžhhŸh¶h NubjÎ  )”}”(hŒwThe voltage and frequency levels as a result of DVFS.  The DVFS
level is a dominant factor governing power consumption.”h]”h¸)”}”(hŒwThe voltage and frequency levels as a result of DVFS.  The DVFS
level is a dominant factor governing power consumption.”h]”hŒwThe voltage and frequency levels as a result of DVFS.  The DVFS
level is a dominant factor governing power consumption.”…””}”(hjë  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KLhjç  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÍ  hjÊ  hžhhŸh¶h NubjÎ  )”}”(hX  In running time the 'execution' behaviour (instruction types, memory
access patterns and so forth) causes, in most cases, a second order
variation.  In pathological cases this variation can be significant,
but typically it is of a much lesser impact than the factors above.
”h]”h¸)”}”(hX  In running time the 'execution' behaviour (instruction types, memory
access patterns and so forth) causes, in most cases, a second order
variation.  In pathological cases this variation can be significant,
but typically it is of a much lesser impact than the factors above.”h]”hX  In running time the â€˜executionâ€™ behaviour (instruction types, memory
access patterns and so forth) causes, in most cases, a second order
variation.  In pathological cases this variation can be significant,
but typically it is of a much lesser impact than the factors above.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KNhjÿ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÍ  hjÊ  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1jÈ  hŸh¶h KIhjc  hžhubh¸)”}”(hŒIA high level dynamic power consumption model may then be represented as::”h]”hŒHA high level dynamic power consumption model may then be represented as:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KShjc  hžhubj`  )”}”(hŒ3Pdyn = f(run) * Voltage^2 * Frequency * Utilisation”h]”hŒ3Pdyn = f(run) * Voltage^2 * Frequency * Utilisation”…””}”hj-  sbah}”(h]”h ]”h"]”h$]”h&]”jo  jp  uh1j_  hŸh¶h KUhjc  hžhubh¸)”}”(hŒf(run) here represents the described execution behaviour and its
result has a units of Watts/Hz/Volt^2 (this often expressed in
mW/MHz/uVolt^2)”h]”hŒf(run) here represents the described execution behaviour and its
result has a units of Watts/Hz/Volt^2 (this often expressed in
mW/MHz/uVolt^2)”…””}”(hj;  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KWhjc  hžhubh¸)”}”(hX“  The detailed behaviour for f(run) could be modelled on-line.  However,
in practice, such an on-line model has dependencies on a number of
implementation specific processor support and characterisation
factors.  Therefore, in initial implementation that contribution is
represented as a constant coefficient.  This is a simplification
consistent with the relative contribution to overall power variation.”h]”hX“  The detailed behaviour for f(run) could be modelled on-line.  However,
in practice, such an on-line model has dependencies on a number of
implementation specific processor support and characterisation
factors.  Therefore, in initial implementation that contribution is
represented as a constant coefficient.  This is a simplification
consistent with the relative contribution to overall power variation.”…””}”(hjI  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K[hjc  hžhubh¸)”}”(hŒ5In this simplified representation our model becomes::”h]”hŒ4In this simplified representation our model becomes:”…””}”(hjW  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kbhjc  hžhubj`  )”}”(hŒ8Pdyn = Capacitance * Voltage^2 * Frequency * Utilisation”h]”hŒ8Pdyn = Capacitance * Voltage^2 * Frequency * Utilisation”…””}”hje  sbah}”(h]”h ]”h"]”h$]”h&]”jo  jp  uh1j_  hŸh¶h Kdhjc  hžhubh¸)”}”(hXo  Where `capacitance` is a constant that represents an indicative
running time dynamic power coefficient in fundamental units of
mW/MHz/uVolt^2.  Typical values for mobile CPUs might lie in range
from 100 to 500.  For reference, the approximate values for the SoC in
ARM's Juno Development Platform are 530 for the Cortex-A57 cluster and
140 for the Cortex-A53 cluster.”h]”(hŒWhere ”…””}”(hjs  hžhhŸNh Nubj}  )”}”(hŒ`capacitance`”h]”hŒcapacitance”…””}”(hj{  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j|  hjs  ubhX^   is a constant that represents an indicative
running time dynamic power coefficient in fundamental units of
mW/MHz/uVolt^2.  Typical values for mobile CPUs might lie in range
from 100 to 500.  For reference, the approximate values for the SoC in
ARMâ€™s Juno Development Platform are 530 for the Cortex-A57 cluster and
140 for the Cortex-A53 cluster.”…””}”(hjs  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kfhjc  hžhubeh}”(h]”Œpower-models”ah ]”h"]”Œ2. power models”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K;ubeh}”(h]”Œcpu-cooling-apis-how-to”ah ]”h"]”Œcpu cooling apis how to”ah$]”h&]”uh1h¡hhhž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  j0  j-  j`  j]  jX  jU  j˜  j•  uŒ	nametypes”}”(j   ‰j0  ‰j`  ‰jX  ‰j˜  ‰uh}”(j  h£j-  j  j]  j3  jU  jD  j•  jc  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”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.