€•g>      Œ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”Œ2/translations/zh_CN/networking/pse-pd/introduction”Œ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”Œ2/translations/zh_TW/networking/pse-pd/introduction”Œ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”Œ2/translations/it_IT/networking/pse-pd/introduction”Œ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”Œ2/translations/ja_JP/networking/pse-pd/introduction”Œ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”Œ2/translations/ko_KR/networking/pse-pd/introduction”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒPortuguese (Brazilian)”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ2/translations/pt_BR/networking/pse-pd/introduction”Œ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”Œ2/translations/sp_SP/networking/pse-pd/introduction”Œ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Œcomment”“”)”}”(hŒ SPDX-License-Identifier: GPL-2.0”h]”hŒ SPDX-License-Identifier: GPL-2.0”…””}”hh·sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1hµhhh²hh³ŒL/var/lib/git/docbuild/linux/Documentation/networking/pse-pd/introduction.rst”h´KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ5Power Sourcing Equipment (PSE) in IEEE 802.3 Standard”h]”hŒ5Power Sourcing Equipment (PSE) in IEEE 802.3 Standard”…””}”(hhÏh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhhÊh²hh³hÇh´KubhÉ)”}”(hhh]”(hÎ)”}”(hŒOverview”h]”hŒOverview”…””}”(hhàh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhhÝh²hh³hÇh´KubhŒ	paragraph”“”)”}”(hX  Power Sourcing Equipment (PSE) is essential in networks for delivering power
along with data over Ethernet cables. It usually refers to devices like
switches and hubs that supply power to Powered Devices (PDs) such as IP
cameras, VoIP phones, and wireless access points.”h]”hX  Power Sourcing Equipment (PSE) is essential in networks for delivering power
along with data over Ethernet cables. It usually refers to devices like
switches and hubs that supply power to Powered Devices (PDs) such as IP
cameras, VoIP phones, and wireless access points.”…””}”(hhðh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´K	hhÝh²hubeh}”(h]”Œoverview”ah ]”h"]”Œoverview”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´KubhÉ)”}”(hhh]”(hÎ)”}”(hŒPSE vs. PoDL PSE”h]”hŒPSE vs. PoDL PSE”…””}”(hj	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj  h²hh³hÇh´Kubhï)”}”(hŒªPSE in the IEEE 802.3 standard generally refers to equipment that provides
power alongside data over Ethernet cables, typically associated with Power over
Ethernet (PoE).”h]”hŒªPSE in the IEEE 802.3 standard generally refers to equipment that provides
power alongside data over Ethernet cables, typically associated with Power over
Ethernet (PoE).”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´Khj  h²hubhï)”}”(hX  PoDL PSE, or Power over Data Lines PSE, specifically denotes PSEs operating
with single balanced twisted-pair PHYs, as per Clause 104 of IEEE 802.3. PoDL
is significant in contexts like automotive and industrial controls where power
and data delivery over a single pair is advantageous.”h]”hX  PoDL PSE, or Power over Data Lines PSE, specifically denotes PSEs operating
with single balanced twisted-pair PHYs, as per Clause 104 of IEEE 802.3. PoDL
is significant in contexts like automotive and industrial controls where power
and data delivery over a single pair is advantageous.”…””}”(hj%  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´Khj  h²hubeh}”(h]”Œpse-vs-podl-pse”ah ]”h"]”Œpse vs. podl pse”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´KubhÉ)”}”(hhh]”(hÎ)”}”(hŒ-IEEE 802.3-2018 Addendums and Related Clauses”h]”hŒ-IEEE 802.3-2018 Addendums and Related Clauses”…””}”(hj>  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj;  h²hh³hÇh´Kubhï)”}”(hŒdKey addenda to the IEEE 802.3-2018 standard relevant to power delivery over
Ethernet are as follows:”h]”hŒdKey addenda to the IEEE 802.3-2018 standard relevant to power delivery over
Ethernet are as follows:”…””}”(hjL  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´Khj;  h²hubhŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒy**802.3af (Approved in 2003-06-12)**: Known as PoE in the market, detailed in
Clause 33, delivering up to 15.4W of power.”h]”hï)”}”(hŒy**802.3af (Approved in 2003-06-12)**: Known as PoE in the market, detailed in
Clause 33, delivering up to 15.4W of power.”h]”(hŒstrong”“”)”}”(hŒ$**802.3af (Approved in 2003-06-12)**”h]”hŒ 802.3af (Approved in 2003-06-12)”…””}”(hjk  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1ji  hje  ubhŒU: Known as PoE in the market, detailed in
Clause 33, delivering up to 15.4W of power.”…””}”(hje  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´K hja  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j_  hj\  h²hh³hÇh´Nubj`  )”}”(hŒ†**802.3at (Approved in 2009-09-11)**: Marketed as PoE+, enhancing PoE as
covered in Clause 33, increasing power delivery to up to 30W.”h]”hï)”}”(hŒ†**802.3at (Approved in 2009-09-11)**: Marketed as PoE+, enhancing PoE as
covered in Clause 33, increasing power delivery to up to 30W.”h]”(jj  )”}”(hŒ$**802.3at (Approved in 2009-09-11)**”h]”hŒ 802.3at (Approved in 2009-09-11)”…””}”(hj‘  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1ji  hj  ubhŒb: Marketed as PoE+, enhancing PoE as
covered in Clause 33, increasing power delivery to up to 30W.”…””}”(hj  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´K"hj‰  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j_  hj\  h²hh³hÇh´Nubj`  )”}”(hŒŒ**802.3bt (Approved in 2018-09-27)**: Known as 4PPoE in the market, outlined
in Clause 33. Type 3 delivers up to 60W, and Type 4 up to 100W.”h]”hï)”}”(hŒŒ**802.3bt (Approved in 2018-09-27)**: Known as 4PPoE in the market, outlined
in Clause 33. Type 3 delivers up to 60W, and Type 4 up to 100W.”h]”(jj  )”}”(hŒ$**802.3bt (Approved in 2018-09-27)**”h]”hŒ 802.3bt (Approved in 2018-09-27)”…””}”(hj·  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1ji  hj³  ubhŒh: Known as 4PPoE in the market, outlined
in Clause 33. Type 3 delivers up to 60W, and Type 4 up to 100W.”…””}”(hj³  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´K$hj¯  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j_  hj\  h²hh³hÇh´Nubj`  )”}”(hŒ›**802.3bu (Approved in 2016-12-07)**: Formerly referred to as PoDL, detailed
in Clause 104. Introduces Classes 0 - 9. Class 9 PoDL PSE delivers up to ~65W
”h]”hï)”}”(hŒš**802.3bu (Approved in 2016-12-07)**: Formerly referred to as PoDL, detailed
in Clause 104. Introduces Classes 0 - 9. Class 9 PoDL PSE delivers up to ~65W”h]”(jj  )”}”(hŒ$**802.3bu (Approved in 2016-12-07)**”h]”hŒ 802.3bu (Approved in 2016-12-07)”…””}”(hjÝ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1ji  hjÙ  ubhŒv: Formerly referred to as PoDL, detailed
in Clause 104. Introduces Classes 0 - 9. Class 9 PoDL PSE delivers up to ~65W”…””}”(hjÙ  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´K&hjÕ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j_  hj\  h²hh³hÇh´Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1jZ  h³hÇh´K hj;  h²hubeh}”(h]”Œ-ieee-802-3-2018-addendums-and-related-clauses”ah ]”h"]”Œ-ieee 802.3-2018 addendums and related clauses”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´KubhÉ)”}”(hhh]”(hÎ)”}”(hŒ(Kernel Naming Convention Recommendations”h]”hŒ(Kernel Naming Convention Recommendations”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj  h²hh³hÇh´K*ubhï)”}”(hŒ}For clarity and consistency within the Linux kernel's networking subsystem, the
following naming conventions are recommended:”h]”hŒFor clarity and consistency within the Linux kernelâ€™s networking subsystem, the
following naming conventions are recommended:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´K,hj  h²hubj[  )”}”(hhh]”(j`  )”}”(hŒ·For general PSE (PoE) code, use "c33_pse" key words. For example:
``enum ethtool_c33_pse_admin_state c33_admin_control;``.
This aligns with Clause 33, encompassing various PoE forms.
”h]”hï)”}”(hŒ¶For general PSE (PoE) code, use "c33_pse" key words. For example:
``enum ethtool_c33_pse_admin_state c33_admin_control;``.
This aligns with Clause 33, encompassing various PoE forms.”h]”(hŒFFor general PSE (PoE) code, use â€œc33_pseâ€ key words. For example:
”…””}”(hj1  h²hh³Nh´NubhŒliteral”“”)”}”(hŒ7``enum ethtool_c33_pse_admin_state c33_admin_control;``”h]”hŒ3enum ethtool_c33_pse_admin_state c33_admin_control;”…””}”(hj;  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j9  hj1  ubhŒ=.
This aligns with Clause 33, encompassing various PoE forms.”…””}”(hj1  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´K/hj-  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j_  hj*  h²hh³hÇh´Nubj`  )”}”(hŒ±For PoDL PSE - specific code, use "podl_pse". For example:
``enum ethtool_podl_pse_admin_state podl_admin_control;`` to differentiate
PoDL PSE settings according to Clause 104.
”h]”hï)”}”(hŒ°For PoDL PSE - specific code, use "podl_pse". For example:
``enum ethtool_podl_pse_admin_state podl_admin_control;`` to differentiate
PoDL PSE settings according to Clause 104.”h]”(hŒ?For PoDL PSE - specific code, use â€œpodl_pseâ€. For example:
”…””}”(hj]  h²hh³Nh´Nubj:  )”}”(hŒ9``enum ethtool_podl_pse_admin_state podl_admin_control;``”h]”hŒ5enum ethtool_podl_pse_admin_state podl_admin_control;”…””}”(hje  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j9  hj]  ubhŒ< to differentiate
PoDL PSE settings according to Clause 104.”…””}”(hj]  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´K3hjY  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j_  hj*  h²hh³hÇh´Nubeh}”(h]”h ]”h"]”h$]”h&]”j  j  uh1jZ  h³hÇh´K/hj  h²hubeh}”(h]”Œ(kernel-naming-convention-recommendations”ah ]”h"]”Œ(kernel naming convention recommendations”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´K*ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ]Summary of Clause 33: Data Terminal Equipment (DTE) Power via Media Dependent Interface (MDI)”h]”hŒ]Summary of Clause 33: Data Terminal Equipment (DTE) Power via Media Dependent Interface (MDI)”…””}”(hj”  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj‘  h²hh³hÇh´K8ubhï)”}”(hXV  Clause 33 of the IEEE 802.3 standard defines the functional and electrical
characteristics of Powered Device (PD) and Power Sourcing Equipment (PSE).
These entities enable power delivery using the same generic cabling as for data
transmission, integrating power with data communication for devices such as
10BASE-T, 100BASE-TX, or 1000BASE-T.”h]”hXV  Clause 33 of the IEEE 802.3 standard defines the functional and electrical
characteristics of Powered Device (PD) and Power Sourcing Equipment (PSE).
These entities enable power delivery using the same generic cabling as for data
transmission, integrating power with data communication for devices such as
10BASE-T, 100BASE-TX, or 1000BASE-T.”…””}”(hj¢  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´K:hj‘  h²hubeh}”(h]”ŒXsummary-of-clause-33-data-terminal-equipment-dte-power-via-media-dependent-interface-mdi”ah ]”h"]”Œ]summary of clause 33: data terminal equipment (dte) power via media dependent interface (mdi)”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´K8ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ\Summary of Clause 104: Power over Data Lines (PoDL) of Single Balanced Twisted-Pair Ethernet”h]”hŒ\Summary of Clause 104: Power over Data Lines (PoDL) of Single Balanced Twisted-Pair Ethernet”…””}”(hj»  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj¸  h²hh³hÇh´KAubhï)”}”(hXú  Clause 104 of the IEEE 802.3 standard delineates the functional and electrical
characteristics of PoDL Powered Devices (PDs) and PoDL Power Sourcing Equipment
(PSEs). These are designed for use with single balanced twisted-pair Ethernet
Physical Layers. In this clause, 'PSE' refers specifically to PoDL PSE, and
'PD' to PoDL PD. The key intent is to provide devices with a unified interface
for both data and the power required to process this data over a single
balanced twisted-pair Ethernet connection.”h]”hX  Clause 104 of the IEEE 802.3 standard delineates the functional and electrical
characteristics of PoDL Powered Devices (PDs) and PoDL Power Sourcing Equipment
(PSEs). These are designed for use with single balanced twisted-pair Ethernet
Physical Layers. In this clause, â€˜PSEâ€™ refers specifically to PoDL PSE, and
â€˜PDâ€™ to PoDL PD. The key intent is to provide devices with a unified interface
for both data and the power required to process this data over a single
balanced twisted-pair Ethernet connection.”…””}”(hjÉ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hîh³hÇh´KChj¸  h²hubeh}”(h]”ŒYsummary-of-clause-104-power-over-data-lines-podl-of-single-balanced-twisted-pair-ethernet”ah ]”h"]”Œ\summary of clause 104: power over data lines (podl) of single balanced twisted-pair ethernet”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´KAubeh}”(h]”Œ3power-sourcing-equipment-pse-in-ieee-802-3-standard”ah ]”h"]”Œ5power sourcing equipment (pse) in ieee 802.3 standard”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á  j  j   j8  j5  j  j  jŽ  j‹  jµ  j²  jÜ  jÙ  uŒ	nametypes”}”(jä  ‰j  ‰j8  ‰j  ‰jŽ  ‰jµ  ‰jÜ  ‰uh}”(já  hÊj   hÝj5  j  j  j;  j‹  j  j²  j‘  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.