€•ÑQ      Œ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”Œ//translations/zh_CN/driver-api/phy/samsung-usb2”Œ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”Œ//translations/zh_TW/driver-api/phy/samsung-usb2”Œ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”Œ//translations/it_IT/driver-api/phy/samsung-usb2”Œ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”Œ//translations/ja_JP/driver-api/phy/samsung-usb2”Œ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”Œ//translations/ko_KR/driver-api/phy/samsung-usb2”Œ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”Œ//translations/sp_SP/driver-api/phy/samsung-usb2”Œ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Œ$Samsung USB 2.0 PHY adaptation layer”h]”hŒ$Samsung USB 2.0 PHY adaptation layer”…””}”(hh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒI/var/lib/git/docbuild/linux/Documentation/driver-api/phy/samsung-usb2.rst”h Kubh¢)”}”(hhh]”(h§)”}”(hŒ1. Description”h]”hŒ1. Description”…””}”(hhºhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh·hžhhŸh¶h KubhŒ	paragraph”“”)”}”(hX  The architecture of the USB 2.0 PHY module in Samsung SoCs is similar
among many SoCs. In spite of the similarities it proved difficult to
create a one driver that would fit all these PHY controllers. Often
the differences were minor and were found in particular bits of the
registers of the PHY. In some rare cases the order of register writes or
the PHY powering up process had to be altered. This adaptation layer is
a compromise between having separate drivers and having a single driver
with added support for many special cases.”h]”hX  The architecture of the USB 2.0 PHY module in Samsung SoCs is similar
among many SoCs. In spite of the similarities it proved difficult to
create a one driver that would fit all these PHY controllers. Often
the differences were minor and were found in particular bits of the
registers of the PHY. In some rare cases the order of register writes or
the PHY powering up process had to be altered. This adaptation layer is
a compromise between having separate drivers and having a single driver
with added support for many special cases.”…””}”(hhÊhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khh·hžhubeh}”(h]”Œdescription”ah ]”h"]”Œ1. description”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒ2. Files description”h]”hŒ2. Files description”…””}”(hhãhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hhàhžhhŸh¶h KubhŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hX-  phy-samsung-usb2.c
 This is the main file of the adaptation layer. This file contains
 the probe function and provides two callbacks to the Generic PHY
 Framework. This two callbacks are used to power on and power off the
 phy. They carry out the common work that has to be done on all version
 of the PHY module. Depending on which SoC was chosen they execute SoC
 specific callbacks. The specific SoC version is selected by choosing
 the appropriate compatible string. In addition, this file contains
 struct of_device_id definitions for particular SoCs.
”h]”hŒdefinition_list”“”)”}”(hhh]”hŒdefinition_list_item”“”)”}”(hX%  phy-samsung-usb2.c
This is the main file of the adaptation layer. This file contains
the probe function and provides two callbacks to the Generic PHY
Framework. This two callbacks are used to power on and power off the
phy. They carry out the common work that has to be done on all version
of the PHY module. Depending on which SoC was chosen they execute SoC
specific callbacks. The specific SoC version is selected by choosing
the appropriate compatible string. In addition, this file contains
struct of_device_id definitions for particular SoCs.
”h]”(hŒterm”“”)”}”(hŒphy-samsung-usb2.c”h]”hŒphy-samsung-usb2.c”…””}”(hj	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh¶h Khj  ubhŒ
definition”“”)”}”(hhh]”hÉ)”}”(hX  This is the main file of the adaptation layer. This file contains
the probe function and provides two callbacks to the Generic PHY
Framework. This two callbacks are used to power on and power off the
phy. They carry out the common work that has to be done on all version
of the PHY module. Depending on which SoC was chosen they execute SoC
specific callbacks. The specific SoC version is selected by choosing
the appropriate compatible string. In addition, this file contains
struct of_device_id definitions for particular SoCs.”h]”hX  This is the main file of the adaptation layer. This file contains
the probe function and provides two callbacks to the Generic PHY
Framework. This two callbacks are used to power on and power off the
phy. They carry out the common work that has to be done on all version
of the PHY module. Depending on which SoC was chosen they execute SoC
specific callbacks. The specific SoC version is selected by choosing
the appropriate compatible string. In addition, this file contains
struct of_device_id definitions for particular SoCs.”…””}”(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 Khhþubah}”(h]”h ]”h"]”h$]”h&]”uh1hühhøubah}”(h]”h ]”h"]”h$]”h&]”uh1höhhóhžhhŸNh Nubh÷)”}”(hŒÀphy-samsung-usb2.h
 This is the include file. It declares the structures used by this
 driver. In addition it should contain extern declarations for
 structures that describe particular SoCs.
”h]”hý)”}”(hhh]”j  )”}”(hŒ½phy-samsung-usb2.h
This is the include file. It declares the structures used by this
driver. In addition it should contain extern declarations for
structures that describe particular SoCs.
”h]”(j  )”}”(hŒphy-samsung-usb2.h”h]”hŒphy-samsung-usb2.h”…””}”(hjM  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh¶h K!hjI  ubj  )”}”(hhh]”hÉ)”}”(hŒ©This is the include file. It declares the structures used by this
driver. In addition it should contain extern declarations for
structures that describe particular SoCs.”h]”hŒ©This is the include file. It declares the structures used by this
driver. In addition it should contain extern declarations for
structures that describe particular SoCs.”…””}”(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jI  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh¶h K!hjF  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hühjB  ubah}”(h]”h ]”h"]”h$]”h&]”uh1höhhóhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1hñhŸh¶h Khhàhžhubeh}”(h]”Œfiles-description”ah ]”h"]”Œ2. files description”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒ3. Supporting SoCs”h]”hŒ3. Supporting SoCs”…””}”(hj—  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj”  hžhhŸh¶h K$ubhÉ)”}”(hŒ§To support a new SoC a new file should be added to the drivers/phy
directory. Each SoC's configuration is stored in an instance of the
struct samsung_usb2_phy_config::”h]”hŒ¨To support a new SoC a new file should be added to the drivers/phy
directory. Each SoCâ€™s configuration is stored in an instance of the
struct samsung_usb2_phy_config:”…””}”(hj¥  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K&hj”  hžhubhŒliteral_block”“”)”}”(hŒ¾struct samsung_usb2_phy_config {
      const struct samsung_usb2_common_phy *phys;
      int (*rate_to_clk)(unsigned long, u32 *);
      unsigned int num_phys;
      bool has_mode_switch;
};”h]”hŒ¾struct samsung_usb2_phy_config {
      const struct samsung_usb2_common_phy *phys;
      int (*rate_to_clk)(unsigned long, u32 *);
      unsigned int num_phys;
      bool has_mode_switch;
};”…””}”hjµ  sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1j³  hŸh¶h K*hj”  hžhubhÉ)”}”(hX{  The num_phys is the number of phys handled by the driver. `*phys` is an
array that contains the configuration for each phy. The has_mode_switch
property is a boolean flag that determines whether the SoC has USB host
and device on a single pair of pins. If so, a special register has to
be modified to change the internal routing of these pins between a USB
device or host module.”h]”(hŒ:The num_phys is the number of phys handled by the driver. ”…””}”(hjÅ  hžhhŸNh NubhŒtitle_reference”“”)”}”(hŒ`*phys`”h]”hŒ*phys”…””}”(hjÏ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÍ  hjÅ  ubhX:   is an
array that contains the configuration for each phy. The has_mode_switch
property is a boolean flag that determines whether the SoC has USB host
and device on a single pair of pins. If so, a special register has to
be modified to change the internal routing of these pins between a USB
device or host module.”…””}”(hjÅ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K1hj”  hžhubhÉ)”}”(hŒ<For example the configuration for Exynos 4210 is following::”h]”hŒ;For example the configuration for Exynos 4210 is following:”…””}”(hjç  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K8hj”  hžhubj´  )”}”(hX  const struct samsung_usb2_phy_config exynos4210_usb2_phy_config = {
      .has_mode_switch        = 0,
      .num_phys               = EXYNOS4210_NUM_PHYS,
      .phys                   = exynos4210_phys,
      .rate_to_clk            = exynos4210_rate_to_clk,
}”h]”hX  const struct samsung_usb2_phy_config exynos4210_usb2_phy_config = {
      .has_mode_switch        = 0,
      .num_phys               = EXYNOS4210_NUM_PHYS,
      .phys                   = exynos4210_phys,
      .rate_to_clk            = exynos4210_rate_to_clk,
}”…””}”hjõ  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  hŸh¶h K:hj”  hžhubhò)”}”(hhh]”h÷)”}”(hŒè`int (*rate_to_clk)(unsigned long, u32 *)`

      The rate_to_clk callback is to convert the rate of the clock
      used as the reference clock for the PHY module to the value
      that should be written in the hardware register.
”h]”(hÉ)”}”(hŒ*`int (*rate_to_clk)(unsigned long, u32 *)`”h]”jÎ  )”}”(hj  h]”hŒ(int (*rate_to_clk)(unsigned long, u32 *)”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÍ  hj
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KAhj  ubhŒblock_quote”“”)”}”(hŒªThe rate_to_clk callback is to convert the rate of the clock
used as the reference clock for the PHY module to the value
that should be written in the hardware register.
”h]”hÉ)”}”(hŒ©The rate_to_clk callback is to convert the rate of the clock
used as the reference clock for the PHY module to the value
that should be written in the hardware register.”h]”hŒ©The rate_to_clk callback is to convert the rate of the clock
used as the reference clock for the PHY module to the value
that should be written in the hardware register.”…””}”(hj'  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KChj#  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j!  hŸh¶h KChj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1höhj  hžhhŸh¶h Nubah}”(h]”h ]”h"]”h$]”h&]”jŠ  j‹  uh1hñhŸh¶h KAhj”  hžhubhÉ)”}”(hŒ7The exynos4210_phys configuration array is as follows::”h]”hŒ6The exynos4210_phys configuration array is as follows:”…””}”(hjG  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KGhj”  hžhubj´  )”}”(hXª  static const struct samsung_usb2_common_phy exynos4210_phys[] = {
      {
              .label          = "device",
              .id             = EXYNOS4210_DEVICE,
              .power_on       = exynos4210_power_on,
              .power_off      = exynos4210_power_off,
      },
      {
              .label          = "host",
              .id             = EXYNOS4210_HOST,
              .power_on       = exynos4210_power_on,
              .power_off      = exynos4210_power_off,
      },
      {
              .label          = "hsic0",
              .id             = EXYNOS4210_HSIC0,
              .power_on       = exynos4210_power_on,
              .power_off      = exynos4210_power_off,
      },
      {
              .label          = "hsic1",
              .id             = EXYNOS4210_HSIC1,
              .power_on       = exynos4210_power_on,
              .power_off      = exynos4210_power_off,
      },
      {},
};”h]”hXª  static const struct samsung_usb2_common_phy exynos4210_phys[] = {
      {
              .label          = "device",
              .id             = EXYNOS4210_DEVICE,
              .power_on       = exynos4210_power_on,
              .power_off      = exynos4210_power_off,
      },
      {
              .label          = "host",
              .id             = EXYNOS4210_HOST,
              .power_on       = exynos4210_power_on,
              .power_off      = exynos4210_power_off,
      },
      {
              .label          = "hsic0",
              .id             = EXYNOS4210_HSIC0,
              .power_on       = exynos4210_power_on,
              .power_off      = exynos4210_power_off,
      },
      {
              .label          = "hsic1",
              .id             = EXYNOS4210_HSIC1,
              .power_on       = exynos4210_power_on,
              .power_off      = exynos4210_power_off,
      },
      {},
};”…””}”hjU  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  hŸh¶h KIhj”  hžhubhò)”}”(hhh]”h÷)”}”(hŒß`int (*power_on)(struct samsung_usb2_phy_instance *);`
`int (*power_off)(struct samsung_usb2_phy_instance *);`

      These two callbacks are used to power on and power off the phy
      by modifying appropriate registers.
”h]”(hÉ)”}”(hŒn`int (*power_on)(struct samsung_usb2_phy_instance *);`
`int (*power_off)(struct samsung_usb2_phy_instance *);`”h]”(jÎ  )”}”(hŒ6`int (*power_on)(struct samsung_usb2_phy_instance *);`”h]”hŒ4int (*power_on)(struct samsung_usb2_phy_instance *);”…””}”(hjn  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÍ  hjj  ubhŒ
”…””}”(hjj  hžhhŸNh NubjÎ  )”}”(hŒ7`int (*power_off)(struct samsung_usb2_phy_instance *);`”h]”hŒ5int (*power_off)(struct samsung_usb2_phy_instance *);”…””}”(hj€  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÍ  hjj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Kehjf  ubj"  )”}”(hŒcThese two callbacks are used to power on and power off the phy
by modifying appropriate registers.
”h]”hÉ)”}”(hŒbThese two callbacks are used to power on and power off the phy
by modifying appropriate registers.”h]”hŒbThese two callbacks are used to power on and power off the phy
by modifying appropriate registers.”…””}”(hj˜  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khhj”  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j!  hŸh¶h Khhjf  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1höhjc  hžhhŸh¶h Nubah}”(h]”h ]”h"]”h$]”h&]”jŠ  j‹  uh1hñhŸh¶h Kehj”  hžhubhÉ)”}”(hŒÖFinal change to the driver is adding appropriate compatible value to the
phy-samsung-usb2.c file. In case of Exynos 4210 the following lines were
added to the struct of_device_id samsung_usb2_phy_of_match[] array::”h]”hŒÕFinal change to the driver is adding appropriate compatible value to the
phy-samsung-usb2.c file. In case of Exynos 4210 the following lines were
added to the struct of_device_id samsung_usb2_phy_of_match[] array:”…””}”(hj¸  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Kkhj”  hžhubj´  )”}”(hŒ§#ifdef CONFIG_PHY_EXYNOS4210_USB2
      {
              .compatible = "samsung,exynos4210-usb2-phy",
              .data = &exynos4210_usb2_phy_config,
      },
#endif”h]”hŒ§#ifdef CONFIG_PHY_EXYNOS4210_USB2
      {
              .compatible = "samsung,exynos4210-usb2-phy",
              .data = &exynos4210_usb2_phy_config,
      },
#endif”…””}”hjÆ  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  hŸh¶h Kohj”  hžhubhÉ)”}”(hŒ¯To add further flexibility to the driver the Kconfig file enables to
include support for selected SoCs in the compiled driver. The Kconfig
entry for Exynos 4210 is following::”h]”hŒ®To add further flexibility to the driver the Kconfig file enables to
include support for selected SoCs in the compiled driver. The Kconfig
entry for Exynos 4210 is following:”…””}”(hjÔ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Kvhj”  hžhubj´  )”}”(hX®  config PHY_EXYNOS4210_USB2
      bool "Support for Exynos 4210"
      depends on PHY_SAMSUNG_USB2
      depends on CPU_EXYNOS4210
      help
        Enable USB PHY support for Exynos 4210. This option requires that
        Samsung USB 2.0 PHY driver is enabled and means that support for this
        particular SoC is compiled in the driver. In case of Exynos 4210 four
        phys are available - device, host, HSCI0 and HSCI1.”h]”hX®  config PHY_EXYNOS4210_USB2
      bool "Support for Exynos 4210"
      depends on PHY_SAMSUNG_USB2
      depends on CPU_EXYNOS4210
      help
        Enable USB PHY support for Exynos 4210. This option requires that
        Samsung USB 2.0 PHY driver is enabled and means that support for this
        particular SoC is compiled in the driver. In case of Exynos 4210 four
        phys are available - device, host, HSCI0 and HSCI1.”…””}”hjâ  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  hŸh¶h Kzhj”  hžhubhÉ)”}”(hŒ‹The newly created file that supports the new SoC has to be also added to the
Makefile. In case of Exynos 4210 the added line is following::”h]”hŒŠThe newly created file that supports the new SoC has to be also added to the
Makefile. In case of Exynos 4210 the added line is following:”…””}”(hjð  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K„hj”  hžhubj´  )”}”(hŒ@obj-$(CONFIG_PHY_EXYNOS4210_USB2)       += phy-exynos4210-usb2.o”h]”hŒ@obj-$(CONFIG_PHY_EXYNOS4210_USB2)       += phy-exynos4210-usb2.o”…””}”hjþ  sbah}”(h]”h ]”h"]”h$]”h&]”jÃ  jÄ  uh1j³  hŸh¶h K‡hj”  hžhubhÉ)”}”(hŒIAfter completing these steps the support for the new SoC should be ready.”h]”hŒIAfter completing these steps the support for the new SoC should be ready.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K‰hj”  hžhubeh}”(h]”Œsupporting-socs”ah ]”h"]”Œ3. supporting socs”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K$ubeh}”(h]”Œ$samsung-usb-2-0-phy-adaptation-layer”ah ]”h"]”Œ$samsung usb 2.0 phy adaptation layer”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”jM  Œ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$  hÝhÚj‘  jŽ  j  j  uŒ	nametypes”}”(j'  ‰hÝ‰j‘  ‰j  ‰uh}”(j$  h£hÚh·jŽ  hàj  j”  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.