€•Àq Œ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”Œ0/translations/zh_CN/driver-api/acpi/acpi-drivers”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah }”(h ]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/zh_TW/driver-api/acpi/acpi-drivers”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒItalian”…””}”hhFsbah }”(h ]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/it_IT/driver-api/acpi/acpi-drivers”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah }”(h ]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/ja_JP/driver-api/acpi/acpi-drivers”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒKorean”…””}”hhnsbah }”(h ]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/ko_KR/driver-api/acpi/acpi-drivers”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒPortuguese (Brazilian)”…””}”hh‚sbah }”(h ]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/pt_BR/driver-api/acpi/acpi-drivers”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒSpanish”…””}”hh–sbah }”(h ]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/sp_SP/driver-api/acpi/acpi-drivers”Œ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³ŒJ/var/lib/git/docbuild/linux/Documentation/driver-api/acpi/acpi-drivers.rst”h´Kubh¶)”}”(hŒ4This data file has been placed in the public domain.”h]”hŒ4This data file has been placed in the public domain.”…””}”hhÈsbah }”(h ]”h ]”h"]”h$]”h&]”hÅhÆuh1hµhhh²hh³Œo/srv/docbuild/lib/venvs/build-kernel-docs/lib64/python3.9/site-packages/docutils/parsers/rst/include/isonum.txt”h´Kubh¶)”}”(hŒ¸Derived from the Unicode character mappings available from
.
Processed by unicode2rstsubs.py, part of Docutils:
.”h]”hŒ¸Derived from the Unicode character mappings available from
.
Processed by unicode2rstsubs.py, part of Docutils:
.”…””}”hh×sbah }”(h ]”h ]”h"]”h$]”h&]”hÅhÆuh1hµhhh²hh³hÖh´KubhŒsubstitution_definition”“”)”}”(hŒ*.. |amp| unicode:: U+00026 .. AMPERSAND”h]”hŒ&”…””}”hhçsbah }”(h ]”h ]”h"]”Œamp”ah$]”h&]”uh1håh³hÖh´Khhh²hubhæ)”}”(hŒ+.. |apos| unicode:: U+00027 .. APOSTROPHE”h]”hŒ'”…””}”hhösbah }”(h ]”h ]”h"]”Œapos”ah$]”h&]”uh1håh³hÖh´Khhh²hubhæ)”}”(hŒ).. |ast| unicode:: U+0002A .. ASTERISK”h]”hŒ*”…””}”hj sbah }”(h ]”h ]”h"]”Œast”ah$]”h&]”uh1håh³hÖh´K hhh²hubhæ)”}”(hŒ+.. |brvbar| unicode:: U+000A6 .. BROKEN BAR”h]”hŒÂ¦”…””}”hj sbah }”(h ]”h ]”h"]”Œbrvbar”ah$]”h&]”uh1håh³hÖh´K
hhh²hubhæ)”}”(hŒ0.. |bsol| unicode:: U+0005C .. REVERSE SOLIDUS”h]”hŒ\”…””}”hj# sbah }”(h ]”h ]”h"]”Œbsol”ah$]”h&]”uh1håh³hÖh´K hhh²hubhæ)”}”(hŒ*.. |cent| unicode:: U+000A2 .. CENT SIGN”h]”hŒÂ¢”…””}”hj2 sbah }”(h ]”h ]”h"]”Œcent”ah$]”h&]”uh1håh³hÖh´K hhh²hubhæ)”}”(hŒ&.. |colon| unicode:: U+0003A .. COLON”h]”hŒ:”…””}”hjA sbah }”(h ]”h ]”h"]”Œcolon”ah$]”h&]”uh1håh³hÖh´K
hhh²hubhæ)”}”(hŒ&.. |comma| unicode:: U+0002C .. COMMA”h]”hŒ,”…””}”hjP sbah }”(h ]”h ]”h"]”Œcomma”ah$]”h&]”uh1håh³hÖh´Khhh²hubhæ)”}”(hŒ... |commat| unicode:: U+00040 .. COMMERCIAL AT”h]”hŒ@”…””}”hj_ sbah }”(h ]”h ]”h"]”Œcommat”ah$]”h&]”uh1håh³hÖh´Khhh²hubhæ)”}”(hŒ/.. |copy| unicode:: U+000A9 .. COPYRIGHT SIGN”h]”hŒÂ©”…””}”hjn sbah }”(h ]”h ]”h"]”Œcopy”ah$]”h&]”uh1håh³hÖh´Khhh²hubhæ)”}”(hŒ... |curren| unicode:: U+000A4 .. CURRENCY SIGN”h]”hŒÂ¤”…””}”hj} sbah }”(h ]”h ]”h"]”Œcurren”ah$]”h&]”uh1håh³hÖh´Khhh²hubhæ)”}”(hŒ0.. |darr| unicode:: U+02193 .. DOWNWARDS ARROW”h]”hŒâ†“”…””}”hjŒ sbah }”(h ]”h ]”h"]”Œdarr”ah$]”h&]”uh1håh³hÖh´Khhh²hubhæ)”}”(hŒ,.. |deg| unicode:: U+000B0 .. DEGREE SIGN”h]”hŒÂ°”…””}”hj› sbah }”(h ]”h ]”h"]”Œdeg”ah$]”h&]”uh1håh³hÖh´Khhh²hubhæ)”}”(hŒ... |divide| unicode:: U+000F7 .. DIVISION SIGN”h]”hŒÃ·”…””}”hjª sbah }”(h ]”h ]”h"]”Œdivide”ah$]”h&]”uh1håh³hÖh´Khhh²hubhæ)”}”(hŒ,.. |dollar| unicode:: U+00024 .. DOLLAR SIGN”h]”hŒ$”…””}”hj¹ sbah }”(h ]”h ]”h"]”Œdollar”ah$]”h&]”uh1håh³hÖh´Khhh²hubhæ)”}”(hŒ,.. |equals| unicode:: U+0003D .. EQUALS SIGN”h]”hŒ=”…””}”hjÈ sbah }”(h ]”h ]”h"]”Œequals”ah$]”h&]”uh1håh³hÖh´Khhh²hubhæ)”}”(hŒ1.. |excl| unicode:: U+00021 .. EXCLAMATION MARK”h]”hŒ!”…””}”hj× sbah }”(h ]”h ]”h"]”Œexcl”ah$]”h&]”uh1håh³hÖh´Khhh²hubhæ)”}”(hŒ9.. |frac12| unicode:: U+000BD .. VULGAR FRACTION ONE HALF”h]”hŒÂ½”…””}”hjæ sbah }”(h ]”h ]”h"]”Œfrac12”ah$]”h&]”uh1håh³hÖh´Khhh²hubhæ)”}”(hŒ<.. |frac14| unicode:: U+000BC .. VULGAR FRACTION ONE QUARTER”h]”hŒÂ¼”…””}”hjõ sbah }”(h ]”h ]”h"]”Œfrac14”ah$]”h&]”uh1håh³hÖh´Khhh²hubhæ)”}”(hŒ;.. |frac18| unicode:: U+0215B .. VULGAR FRACTION ONE EIGHTH”h]”hŒâ…›”…””}”hj sbah }”(h ]”h ]”h"]”Œfrac18”ah$]”h&]”uh1håh³hÖh´Khhh²hubhæ)”}”(hŒ?.. |frac34| unicode:: U+000BE .. VULGAR FRACTION THREE QUARTERS”h]”hŒÂ¾”…””}”hj sbah }”(h ]”h ]”h"]”Œfrac34”ah$]”h&]”uh1håh³hÖh´Khhh²hubhæ)”}”(hŒ>.. |frac38| unicode:: U+0215C .. VULGAR FRACTION THREE EIGHTHS”h]”hŒâ…œ”…””}”hj" sbah }”(h ]”h ]”h"]”Œfrac38”ah$]”h&]”uh1håh³hÖh´K hhh²hubhæ)”}”(hŒ=.. |frac58| unicode:: U+0215D .. VULGAR FRACTION FIVE EIGHTHS”h]”hŒâ…”…””}”hj1 sbah }”(h ]”h ]”h"]”Œfrac58”ah$]”h&]”uh1håh³hÖh´K hhh²hubhæ)”}”(hŒ>.. |frac78| unicode:: U+0215E .. VULGAR FRACTION SEVEN EIGHTHS”h]”hŒâ…ž”…””}”hj@ sbah }”(h ]”h ]”h"]”Œfrac78”ah$]”h&]”uh1håh³hÖh´K hhh²hubhæ)”}”(hŒ2.. |gt| unicode:: U+0003E .. GREATER-THAN SIGN”h]”hŒ>”…””}”hjO sbah }”(h ]”h ]”h"]”Œgt”ah$]”h&]”uh1håh³hÖh´K hhh²hubhæ)”}”(hŒ9.. |half| unicode:: U+000BD .. VULGAR FRACTION ONE HALF”h]”hŒÂ½”…””}”hj^ sbah }”(h ]”h ]”h"]”Œhalf”ah$]”h&]”uh1håh³hÖh´K hhh²hubhæ)”}”(hŒ/.. |horbar| unicode:: U+02015 .. HORIZONTAL BAR”h]”hŒâ€•”…””}”hjm sbah }”(h ]”h ]”h"]”Œhorbar”ah$]”h&]”uh1håh³hÖh´K!hhh²hubhæ)”}”(hŒ'.. |hyphen| unicode:: U+02010 .. HYPHEN”h]”hŒâ€”…””}”hj| sbah }”(h ]”h ]”h"]”Œhyphen”ah$]”h&]”uh1håh³hÖh´K"hhh²hubhæ)”}”(hŒ:.. |iexcl| unicode:: U+000A1 .. INVERTED EXCLAMATION MARK”h]”hŒÂ¡”…””}”hj‹ sbah }”(h ]”h ]”h"]”Œiexcl”ah$]”h&]”uh1håh³hÖh´K#hhh²hubhæ)”}”(hŒ7.. |iquest| unicode:: U+000BF .. INVERTED QUESTION MARK”h]”hŒÂ¿”…””}”hjš sbah }”(h ]”h ]”h"]”Œiquest”ah$]”h&]”uh1håh³hÖh´K$hhh²hubhæ)”}”(hŒJ.. |laquo| unicode:: U+000AB .. LEFT-POINTING DOUBLE ANGLE QUOTATION MARK”h]”hŒÂ«”…””}”hj© sbah }”(h ]”h ]”h"]”Œlaquo”ah$]”h&]”uh1håh³hÖh´K%hhh²hubhæ)”}”(hŒ0.. |larr| unicode:: U+02190 .. LEFTWARDS ARROW”h]”hŒâ†”…””}”hj¸ sbah }”(h ]”h ]”h"]”Œlarr”ah$]”h&]”uh1håh³hÖh´K&hhh²hubhæ)”}”(hŒ3.. |lcub| unicode:: U+0007B .. LEFT CURLY BRACKET”h]”hŒ{”…””}”hjÇ sbah }”(h ]”h ]”h"]”Œlcub”ah$]”h&]”uh1håh³hÖh´K'hhh²hubhæ)”}”(hŒ;.. |ldquo| unicode:: U+0201C .. LEFT DOUBLE QUOTATION MARK”h]”hŒâ€œ”…””}”hjÖ sbah }”(h ]”h ]”h"]”Œldquo”ah$]”h&]”uh1håh³hÖh´K(hhh²hubhæ)”}”(hŒ).. |lowbar| unicode:: U+0005F .. LOW LINE”h]”hŒ_”…””}”hjå sbah }”(h ]”h ]”h"]”Œlowbar”ah$]”h&]”uh1håh³hÖh´K)hhh²hubhæ)”}”(hŒ1.. |lpar| unicode:: U+00028 .. LEFT PARENTHESIS”h]”hŒ(”…””}”hjô sbah }”(h ]”h ]”h"]”Œlpar”ah$]”h&]”uh1håh³hÖh´K*hhh²hubhæ)”}”(hŒ4.. |lsqb| unicode:: U+0005B .. LEFT SQUARE BRACKET”h]”hŒ[”…””}”hj sbah }”(h ]”h ]”h"]”Œlsqb”ah$]”h&]”uh1håh³hÖh´K+hhh²hubhæ)”}”(hŒ;.. |lsquo| unicode:: U+02018 .. LEFT SINGLE QUOTATION MARK”h]”hŒâ€˜”…””}”hj sbah }”(h ]”h ]”h"]”Œlsquo”ah$]”h&]”uh1håh³hÖh´K,hhh²hubhæ)”}”(hŒ/.. |lt| unicode:: U+0003C .. LESS-THAN SIGN”h]”hŒ<”…””}”hj! sbah }”(h ]”h ]”h"]”Œlt”ah$]”h&]”uh1håh³hÖh´K-hhh²hubhæ)”}”(hŒ+.. |micro| unicode:: U+000B5 .. MICRO SIGN”h]”hŒÂµ”…””}”hj0 sbah }”(h ]”h ]”h"]”Œmicro”ah$]”h&]”uh1håh³hÖh´K.hhh²hubhæ)”}”(hŒ+.. |middot| unicode:: U+000B7 .. MIDDLE DOT”h]”hŒÂ·”…””}”hj? sbah }”(h ]”h ]”h"]”Œmiddot”ah$]”h&]”uh1håh³hÖh´K/hhh²hubhæ)”}”(hŒ/.. |nbsp| unicode:: U+000A0 .. NO-BREAK SPACE”h]”hŒÂ ”…””}”hjN sbah }”(h ]”h ]”h"]”Œnbsp”ah$]”h&]”uh1håh³hÖh´K0hhh²hubhæ)”}”(hŒ).. |not| unicode:: U+000AC .. NOT SIGN”h]”hŒÂ¬”…””}”hj] sbah }”(h ]”h ]”h"]”Œnot”ah$]”h&]”uh1håh³hÖh´K1hhh²hubhæ)”}”(hŒ,.. |num| unicode:: U+00023 .. NUMBER SIGN”h]”hŒ#”…””}”hjl sbah }”(h ]”h ]”h"]”Œnum”ah$]”h&]”uh1håh³hÖh´K2hhh²hubhæ)”}”(hŒ).. |ohm| unicode:: U+02126 .. OHM SIGN”h]”hŒâ„¦”…””}”hj{ sbah }”(h ]”h ]”h"]”Œohm”ah$]”h&]”uh1håh³hÖh´K3hhh²hubhæ)”}”(hŒ;.. |ordf| unicode:: U+000AA .. FEMININE ORDINAL INDICATOR”h]”hŒÂª”…””}”hjŠ sbah }”(h ]”h ]”h"]”Œordf”ah$]”h&]”uh1håh³hÖh´K4hhh²hubhæ)”}”(hŒ<.. |ordm| unicode:: U+000BA .. MASCULINE ORDINAL INDICATOR”h]”hŒÂº”…””}”hj™ sbah }”(h ]”h ]”h"]”Œordm”ah$]”h&]”uh1håh³hÖh´K5hhh²hubhæ)”}”(hŒ-.. |para| unicode:: U+000B6 .. PILCROW SIGN”h]”hŒÂ¶”…””}”hj¨ sbah }”(h ]”h ]”h"]”Œpara”ah$]”h&]”uh1håh³hÖh´K6hhh²hubhæ)”}”(hŒ-.. |percnt| unicode:: U+00025 .. PERCENT SIGN”h]”hŒ%”…””}”hj· sbah }”(h ]”h ]”h"]”Œpercnt”ah$]”h&]”uh1håh³hÖh´K7hhh²hubhæ)”}”(hŒ*.. |period| unicode:: U+0002E .. FULL STOP”h]”hŒ.”…””}”hjÆ sbah }”(h ]”h ]”h"]”Œperiod”ah$]”h&]”uh1håh³hÖh´K8hhh²hubhæ)”}”(hŒ*.. |plus| unicode:: U+0002B .. PLUS SIGN”h]”hŒ+”…””}”hjÕ sbah }”(h ]”h ]”h"]”Œplus”ah$]”h&]”uh1håh³hÖh´K9hhh²hubhæ)”}”(hŒ0.. |plusmn| unicode:: U+000B1 .. PLUS-MINUS SIGN”h]”hŒÂ±”…””}”hjä sbah }”(h ]”h ]”h"]”Œplusmn”ah$]”h&]”uh1håh³hÖh´K:hhh²hubhæ)”}”(hŒ+.. |pound| unicode:: U+000A3 .. POUND SIGN”h]”hŒÂ£”…””}”hjó sbah }”(h ]”h ]”h"]”Œpound”ah$]”h&]”uh1håh³hÖh´K;hhh²hubhæ)”}”(hŒ... |quest| unicode:: U+0003F .. QUESTION MARK”h]”hŒ?”…””}”hj sbah }”(h ]”h ]”h"]”Œquest”ah$]”h&]”uh1håh³hÖh´Khhh²hubhæ)”}”(hŒ1.. |rarr| unicode:: U+02192 .. RIGHTWARDS ARROW”h]”hŒâ†’”…””}”hj/ sbah }”(h ]”h ]”h"]”Œrarr”ah$]”h&]”uh1håh³hÖh´K?hhh²hubhæ)”}”(hŒ4.. |rcub| unicode:: U+0007D .. RIGHT CURLY BRACKET”h]”hŒ}”…””}”hj> sbah }”(h ]”h ]”h"]”Œrcub”ah$]”h&]”uh1håh³hÖh´K@hhh²hubhæ)”}”(hŒ<.. |rdquo| unicode:: U+0201D .. RIGHT DOUBLE QUOTATION MARK”h]”hŒâ€”…””}”hjM sbah }”(h ]”h ]”h"]”Œrdquo”ah$]”h&]”uh1håh³hÖh´KAhhh²hubhæ)”}”(hŒ0.. |reg| unicode:: U+000AE .. REGISTERED SIGN”h]”hŒÂ®”…””}”hj\ sbah }”(h ]”h ]”h"]”Œreg”ah$]”h&]”uh1håh³hÖh´KBhhh²hubhæ)”}”(hŒ2.. |rpar| unicode:: U+00029 .. RIGHT PARENTHESIS”h]”hŒ)”…””}”hjk sbah }”(h ]”h ]”h"]”Œrpar”ah$]”h&]”uh1håh³hÖh´KChhh²hubhæ)”}”(hŒ5.. |rsqb| unicode:: U+0005D .. RIGHT SQUARE BRACKET”h]”hŒ]”…””}”hjz sbah }”(h ]”h ]”h"]”Œrsqb”ah$]”h&]”uh1håh³hÖh´KDhhh²hubhæ)”}”(hŒ<.. |rsquo| unicode:: U+02019 .. RIGHT SINGLE QUOTATION MARK”h]”hŒâ€™”…””}”hj‰ sbah }”(h ]”h ]”h"]”Œrsquo”ah$]”h&]”uh1håh³hÖh´KEhhh²hubhæ)”}”(hŒ-.. |sect| unicode:: U+000A7 .. SECTION SIGN”h]”hŒÂ§”…””}”hj˜ sbah }”(h ]”h ]”h"]”Œsect”ah$]”h&]”uh1håh³hÖh´KFhhh²hubhæ)”}”(hŒ*.. |semi| unicode:: U+0003B .. SEMICOLON”h]”hŒ;”…””}”hj§ sbah }”(h ]”h ]”h"]”Œsemi”ah$]”h&]”uh1håh³hÖh´KGhhh²hubhæ)”}”(hŒ,.. |shy| unicode:: U+000AD .. SOFT HYPHEN”h]”hŒÂ”…””}”hj¶ sbah }”(h ]”h ]”h"]”Œshy”ah$]”h&]”uh1håh³hÖh´KHhhh²hubhæ)”}”(hŒ(.. |sol| unicode:: U+0002F .. SOLIDUS”h]”hŒ/”…””}”hjÅ sbah }”(h ]”h ]”h"]”Œsol”ah$]”h&]”uh1håh³hÖh´KIhhh²hubhæ)”}”(hŒ,.. |sung| unicode:: U+0266A .. EIGHTH NOTE”h]”hŒâ™ª”…””}”hjÔ sbah }”(h ]”h ]”h"]”Œsung”ah$]”h&]”uh1håh³hÖh´KJhhh²hubhæ)”}”(hŒ0.. |sup1| unicode:: U+000B9 .. SUPERSCRIPT ONE”h]”hŒÂ¹”…””}”hjã sbah }”(h ]”h ]”h"]”Œsup1”ah$]”h&]”uh1håh³hÖh´KKhhh²hubhæ)”}”(hŒ0.. |sup2| unicode:: U+000B2 .. SUPERSCRIPT TWO”h]”hŒÂ²”…””}”hjò sbah }”(h ]”h ]”h"]”Œsup2”ah$]”h&]”uh1håh³hÖh´KLhhh²hubhæ)”}”(hŒ2.. |sup3| unicode:: U+000B3 .. SUPERSCRIPT THREE”h]”hŒÂ³”…””}”hj sbah }”(h ]”h ]”h"]”Œsup3”ah$]”h&]”uh1håh³hÖh´KMhhh²hubhæ)”}”(hŒ4.. |times| unicode:: U+000D7 .. MULTIPLICATION SIGN”h]”hŒÃ—”…””}”hj sbah }”(h ]”h ]”h"]”Œtimes”ah$]”h&]”uh1håh³hÖh´KNhhh²hubhæ)”}”(hŒ0.. |trade| unicode:: U+02122 .. TRADE MARK SIGN”h]”hŒâ„¢”…””}”hj sbah }”(h ]”h ]”h"]”Œtrade”ah$]”h&]”uh1håh³hÖh´KOhhh²hubhæ)”}”(hŒ... |uarr| unicode:: U+02191 .. UPWARDS ARROW”h]”hŒâ†‘”…””}”hj. sbah }”(h ]”h ]”h"]”Œuarr”ah$]”h&]”uh1håh³hÖh´KPhhh²hubhæ)”}”(hŒ... |verbar| unicode:: U+0007C .. VERTICAL LINE”h]”hŒ|”…””}”hj= sbah }”(h ]”h ]”h"]”Œverbar”ah$]”h&]”uh1håh³hÖh´KQhhh²hubhæ)”}”(hŒ*.. |yen| unicode:: U+000A5 .. YEN SIGN
”h]”hŒÂ¥”…””}”hjL sbah }”(h ]”h ]”h"]”Œyen”ah$]”h&]”uh1håh³hÖh´KRhhh²hubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ)Why using ACPI drivers is not a good idea”h]”hŒ)Why using ACPI drivers is not a good idea”…””}”(hjb h²hh³Nh´Nubah }”(h ]”h ]”h"]”h$]”h&]”uh1j` hj] h²hh³hÇh´KubhŒ
field_list”“”)”}”(hhh]”(hŒfield”“”)”}”(hhh]”(hŒ
field_name”“”)”}”(hŒ Copyright”h]”hŒ Copyright”…””}”(hj| h²hh³Nh´Nubah }”(h ]”h ]”h"]”h$]”h&]”uh1jz hjw h³hÇh´K ubhŒ
field_body”“”)”}”(hŒ |copy| 2026, Intel Corporation
”h]”hŒ paragraph”“”)”}”(hŒ |copy| 2026, Intel Corporation”h]”(hŒÂ©”…””}”(hj’ h²hh³Nh´NubhŒ 2026, Intel Corporation”…””}”(hj’ h²hh³Nh´Nubeh }”(h ]”h ]”h"]”h$]”h&]”uh1j h³hÇh´KhjŒ ubah }”(h ]”h ]”h"]”h$]”h&]”uh1jŠ hjw ubeh }”(h ]”h ]”h"]”h$]”h&]”uh1ju h³hÇh´Khjr h²hubjv )”}”(hhh]”(j{ )”}”(hŒAuthor”h]”hŒAuthor”…””}”(hj³ h²hh³Nh´Nubah }”(h ]”h ]”h"]”h$]”h&]”uh1jz hj° h³hÇh´K ubj‹ )”}”(hŒ/Rafael J. Wysocki
”h]”j‘ )”}”(hŒ.Rafael J. Wysocki ”h]”(hŒRafael J. Wysocki <”…””}”(hjÅ h²hh³Nh´NubhŒ reference”“”)”}”(hŒrafael.j.wysocki@intel.com”h]”hŒrafael.j.wysocki@intel.com”…””}”(hjÏ h²hh³Nh´Nubah }”(h ]”h ]”h"]”h$]”h&]”Œrefuri”Œ!mailto:rafael.j.wysocki@intel.com”uh1jÍ hjÅ ubhŒ>”…””}”(hjÅ h²hh³Nh´Nubeh }”(h ]”h ]”h"]”h$]”h&]”uh1j h³hÇh´K
hjÁ ubah }”(h ]”h ]”h"]”h$]”h&]”uh1jŠ hj° ubeh }”(h ]”h ]”h"]”h$]”h&]”uh1ju h³hÇh´K
hjr h²hubeh }”(h ]”h ]”h"]”h$]”h&]”uh1jp hj] h²hh³hÇh´Kubj‘ )”}”(hX3 Even though binding drivers directly to struct acpi_device objects, also
referred to as "ACPI device nodes", allows basic functionality to be provided
at least in some cases, there are problems with it, related to general
consistency, sysfs layout, power management operation ordering, and code
cleanliness.”h]”hX7 Even though binding drivers directly to struct acpi_device objects, also
referred to as “ACPI device nodesâ€, allows basic functionality to be provided
at least in some cases, there are problems with it, related to general
consistency, sysfs layout, power management operation ordering, and code
cleanliness.”…””}”(hjû h²hh³Nh´Nubah }”(h ]”h ]”h"]”h$]”h&]”uh1j h³hÇh´K hj] h²hubj‘ )”}”(hX» First of all, ACPI device nodes represent firmware entities rather than
hardware and in many cases they provide auxiliary information on devices
enumerated independently (like PCI devices or CPUs). It is therefore generally
questionable to assign resources to them because the entities represented by
them do not decode addresses in the memory or I/O address spaces and do not
generate interrupts or similar (all of that is done by hardware).”h]”hX» First of all, ACPI device nodes represent firmware entities rather than
hardware and in many cases they provide auxiliary information on devices
enumerated independently (like PCI devices or CPUs). It is therefore generally
questionable to assign resources to them because the entities represented by
them do not decode addresses in the memory or I/O address spaces and do not
generate interrupts or similar (all of that is done by hardware).”…””}”(hj h²hh³Nh´Nubah }”(h ]”h ]”h"]”h$]”h&]”uh1j h³hÇh´Khj] h²hubj‘ )”}”(hXã Second, as a general rule, a struct acpi_device can only be a parent of another
struct acpi_device. If that is not the case, the location of the child device
in the device hierarchy is at least confusing and it may not be straightforward
to identify the piece of hardware providing functionality represented by it.
However, binding a driver directly to an ACPI device node may cause that to
happen if the given driver registers input devices or wakeup sources under it,
for example.”h]”hXã Second, as a general rule, a struct acpi_device can only be a parent of another
struct acpi_device. If that is not the case, the location of the child device
in the device hierarchy is at least confusing and it may not be straightforward
to identify the piece of hardware providing functionality represented by it.
However, binding a driver directly to an ACPI device node may cause that to
happen if the given driver registers input devices or wakeup sources under it,
for example.”…””}”(hj h²hh³Nh´Nubah }”(h ]”h ]”h"]”h$]”h&]”uh1j h³hÇh´Khj] h²hubj‘ )”}”(hXÀ Next, using system suspend and resume callbacks directly on ACPI device nodes
is also questionable because it may cause ordering problems to appear. Namely,
ACPI device nodes are registered before enumerating hardware corresponding to
them and they land on the PM list in front of the majority of other device
objects. Consequently, the execution ordering of their PM callbacks may be
different from what is generally expected. Also, in general, dependencies
returned by _DEP objects do not affect ACPI device nodes themselves, but the
"physical" devices associated with them, which potentially is one more source
of inconsistency related to treating ACPI device nodes as "real" device
representation.”h]”hXÈ Next, using system suspend and resume callbacks directly on ACPI device nodes
is also questionable because it may cause ordering problems to appear. Namely,
ACPI device nodes are registered before enumerating hardware corresponding to
them and they land on the PM list in front of the majority of other device
objects. Consequently, the execution ordering of their PM callbacks may be
different from what is generally expected. Also, in general, dependencies
returned by _DEP objects do not affect ACPI device nodes themselves, but the
“physical†devices associated with them, which potentially is one more source
of inconsistency related to treating ACPI device nodes as “real†device
representation.”…””}”(hj% h²hh³Nh´Nubah }”(h ]”h ]”h"]”h$]”h&]”uh1j h³hÇh´K!hj] h²hubj‘ )”}”(hŒ’All of the above means that binding drivers to ACPI device nodes should
generally be avoided and so struct acpi_driver objects should not be used.”h]”hŒ’All of the above means that binding drivers to ACPI device nodes should
generally be avoided and so struct acpi_driver objects should not be used.”…””}”(hj3 h²hh³Nh´Nubah }”(h ]”h ]”h"]”h$]”h&]”uh1j h³hÇh´K,hj] h²hubj‘ )”}”(hXÏ Moreover, a device ID is necessary to bind a driver directly to an ACPI device
node, but device IDs are not generally associated with all of them. Some of
them contain alternative information allowing the corresponding pieces of
hardware to be identified, for example represented by an _ADR object return
value, and device IDs are not used in those cases. In consequence, confusingly
enough, binding an ACPI driver to an ACPI device node may even be impossible.”h]”hXÏ Moreover, a device ID is necessary to bind a driver directly to an ACPI device
node, but device IDs are not generally associated with all of them. Some of
them contain alternative information allowing the corresponding pieces of
hardware to be identified, for example represented by an _ADR object return
value, and device IDs are not used in those cases. In consequence, confusingly
enough, binding an ACPI driver to an ACPI device node may even be impossible.”…””}”(hjA h²hh³Nh´Nubah }”(h ]”h ]”h"]”h$]”h&]”uh1j h³hÇh´K/hj] h²hubj‘ )”}”(hXŒ When that happens, the piece of hardware corresponding to the given ACPI device
node is represented by another device object, like a struct pci_dev, and the
ACPI device node is the "ACPI companion" of that device, accessible through its
fwnode pointer used by the ACPI_COMPANION() macro. The ACPI companion holds
additional information on the device configuration and possibly some "recipes"
on device manipulation in the form of AML (ACPI Machine Language) bytecode
provided by the platform firmware. Thus the role of the ACPI device node is
similar to the role of a struct device_node on a system where Device Tree is
used for platform description.”h]”hX” When that happens, the piece of hardware corresponding to the given ACPI device
node is represented by another device object, like a struct pci_dev, and the
ACPI device node is the “ACPI companion†of that device, accessible through its
fwnode pointer used by the ACPI_COMPANION() macro. The ACPI companion holds
additional information on the device configuration and possibly some “recipesâ€
on device manipulation in the form of AML (ACPI Machine Language) bytecode
provided by the platform firmware. Thus the role of the ACPI device node is
similar to the role of a struct device_node on a system where Device Tree is
used for platform description.”…””}”(hjO h²hh³Nh´Nubah }”(h ]”h ]”h"]”h$]”h&]”uh1j h³hÇh´K6hj] h²hubj‘ )”}”(hX¢ For consistency, this approach has been extended to the cases in which ACPI
device IDs are used. Namely, in those cases, an additional device object is
created to represent the piece of hardware corresponding to a given ACPI device
node. By default, it is a platform device, but it may also be a PNP device, a
CPU device, or another type of device, depending on what the given piece of
hardware actually is. There are even cases in which multiple devices are
"backed" or "accompanied" by one ACPI device node (e.g. ACPI device nodes
corresponding to GPUs that may provide firmware interfaces for backlight
brightness control in addition to GPU configuration information).”h]”hXª For consistency, this approach has been extended to the cases in which ACPI
device IDs are used. Namely, in those cases, an additional device object is
created to represent the piece of hardware corresponding to a given ACPI device
node. By default, it is a platform device, but it may also be a PNP device, a
CPU device, or another type of device, depending on what the given piece of
hardware actually is. There are even cases in which multiple devices are
“backed†or “accompanied†by one ACPI device node (e.g. ACPI device nodes
corresponding to GPUs that may provide firmware interfaces for backlight
brightness control in addition to GPU configuration information).”…””}”(hj] h²hh³Nh´Nubah }”(h ]”h ]”h"]”h$]”h&]”uh1j h³hÇh´K@hj] h²hubj‘ )”}”(hXû This means that it really should never be necessary to bind a driver directly to
an ACPI device node because there is a "proper" device object representing the
corresponding piece of hardware that can be bound to by a "proper" driver using
the given ACPI device node as the device's ACPI companion. Thus, in principle,
there is no reason to use ACPI drivers and if they all were replaced with other
driver types (for example, platform drivers), some code could be dropped and
some complexity would go away.”h]”hX This means that it really should never be necessary to bind a driver directly to
an ACPI device node because there is a “proper†device object representing the
corresponding piece of hardware that can be bound to by a “proper†driver using
the given ACPI device node as the device’s ACPI companion. Thus, in principle,
there is no reason to use ACPI drivers and if they all were replaced with other
driver types (for example, platform drivers), some code could be dropped and
some complexity would go away.”…””}”(hjk h²hh³Nh´Nubah }”(h ]”h ]”h"]”h$]”h&]”uh1j h³hÇh´KJhj] h²hubeh }”(h ]”Œ)why-using-acpi-drivers-is-not-a-good-idea”ah ]”h"]”Œ)why using acpi drivers is not a good idea”ah$]”h&]”uh1j[ hhh²hh³hÇh´Kubeh }”(h ]”h ]”h"]”h$]”h&]”Œsource”hÇuh1hŒcurrent_source”NŒ current_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(j` 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”}”(hóhçj höj j j j j/ j# j> j2 jM jA j\ jP jk j_ jz jn j‰ j} j˜ jŒ j§ j› j¶ jª jÅ j¹ jÔ jÈ jã j× jò jæ j jõ j j j j j. j" j= j1 jL j@ j[ jO jj j^ jy jm jˆ j| j— j‹ j¦ jš jµ j© jÄ j¸ jÓ jÇ jâ jÖ jñ jå j jô j j j j j- j! j< j0 jK j? jZ jN ji j] jx jl j‡ j{ j– jŠ j¥ j™ j´ j¨ jà j· jÒ jÆ já jÕ jð jä jÿ jó j j j j j, j j; j/ jJ j> jY jM jh j\ jw jk j† jz j• j‰ j¤ j˜ j³ j§ j j¶ jÑ jÅ jà jÔ jï jã jþ jò j
j j j j+ j j: j. jI j= jX jL uŒsubstitution_names”}”(Œamp”hóŒapos”j Œast”j Œbrvbar”j Œbsol”j/ Œcent”j> Œcolon”jM Œcomma”j\ Œcommat”jk Œcopy”jz Œcurren”j‰ Œdarr”j˜ Œdeg”j§ Œdivide”j¶ Œdollar”jÅ Œequals”jÔ Œexcl”jã Œfrac12”jò Œfrac14”j Œfrac18”j Œfrac34”j Œfrac38”j. Œfrac58”j= Œfrac78”jL Œgt”j[ Œhalf”jj Œhorbar”jy Œhyphen”jˆ Œiexcl”j— Œiquest”j¦ Œlaquo”jµ Œlarr”jÄ Œlcub”jÓ Œldquo”jâ Œlowbar”jñ Œlpar”j Œlsqb”j Œlsquo”j Œlt”j- Œmicro”j< Œmiddot”jK Œnbsp”jZ Œnot”ji Œnum”jx Œohm”j‡ Œordf”j– Œordm”j¥ Œpara”j´ Œpercnt”jà Œperiod”jÒ Œplus”já Œplusmn”jð Œpound”jÿ Œquest”j Œquot”j Œraquo”j, Œrarr”j; Œrcub”jJ Œrdquo”jY Œreg”jh Œrpar”jw Œrsqb”j† Œrsquo”j• Œsect”j¤ Œsemi”j³ Œshy”j Œsol”jÑ Œsung”jà Œsup1”jï Œsup2”jþ Œsup3”j
Œtimes”j Œtrade”j+ Œuarr”j: Œverbar”jI Œyen”jX uŒrefnames”}”Œrefids”}”Œnameids”}”j~ j{ sŒ nametypes”}”j~ ‰sh }”j{ j] sŒ
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”]”Œ.Documentation/driver-api/acpi/acpi-drivers.rst”(NNNNt”†”aŒ
decoration”Nh²hub.