sphinx.addnodesdocument)}( rawsourcechildren]( translations LanguagesNode)}(hhh](h pending_xref)}(hhh]docutils.nodesTextChinese (Simplified)}parenthsba attributes}(ids]classes]names]dupnames]backrefs] refdomainstdreftypedoc reftarget4/translations/zh_CN/driver-api/acpi/linuxized-acpicamodnameN classnameN refexplicitutagnamehhh ubh)}(hhh]hChinese (Traditional)}hh2sbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget4/translations/zh_TW/driver-api/acpi/linuxized-acpicamodnameN classnameN refexplicituh1hhh ubh)}(hhh]hItalian}hhFsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget4/translations/it_IT/driver-api/acpi/linuxized-acpicamodnameN classnameN refexplicituh1hhh ubh)}(hhh]hJapanese}hhZsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget4/translations/ja_JP/driver-api/acpi/linuxized-acpicamodnameN classnameN refexplicituh1hhh ubh)}(hhh]hKorean}hhnsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget4/translations/ko_KR/driver-api/acpi/linuxized-acpicamodnameN classnameN refexplicituh1hhh ubh)}(hhh]hPortuguese (Brazilian)}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget4/translations/pt_BR/driver-api/acpi/linuxized-acpicamodnameN classnameN refexplicituh1hhh ubh)}(hhh]hSpanish}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget4/translations/sp_SP/driver-api/acpi/linuxized-acpicamodnameN classnameN refexplicituh1hhh ubeh}(h]h ]h"]h$]h&]current_languageEnglishuh1h hh _documenthsourceNlineNubhcomment)}(h SPDX-License-Identifier: GPL-2.0h]h SPDX-License-Identifier: GPL-2.0}hhsbah}(h]h ]h"]h$]h&] xml:spacepreserveuh1hhhhhhN/var/lib/git/docbuild/linux/Documentation/driver-api/acpi/linuxized-acpica.rsthKubh)}(h4This data file has been placed in the public domain.h]h4This data file has been placed in the public domain.}hhsbah}(h]h ]h"]h$]h&]hhuh1hhhhhho/srv/docbuild/lib/venvs/build-kernel-docs/lib64/python3.9/site-packages/docutils/parsers/rst/include/isonum.txthKubh)}(hDerived from the Unicode character mappings available from . Processed by unicode2rstsubs.py, part of Docutils: .h]hDerived from the Unicode character mappings available from . Processed by unicode2rstsubs.py, part of Docutils: .}hhsbah}(h]h ]h"]h$]h&]hhuh1hhhhhhhhKubhsubstitution_definition)}(h*.. |amp| unicode:: U+00026 .. AMPERSANDh]h&}hhsbah}(h]h ]h"]ampah$]h&]uh1hhhhKhhhhubh)}(h+.. |apos| unicode:: U+00027 .. APOSTROPHEh]h'}hhsbah}(h]h ]h"]aposah$]h&]uh1hhhhKhhhhubh)}(h).. |ast| unicode:: U+0002A .. ASTERISKh]h*}hjsbah}(h]h ]h"]astah$]h&]uh1hhhhK hhhhubh)}(h+.. |brvbar| unicode:: U+000A6 .. BROKEN BARh]h¦}hjsbah}(h]h ]h"]brvbarah$]h&]uh1hhhhK hhhhubh)}(h0.. |bsol| unicode:: U+0005C .. REVERSE SOLIDUSh]h\}hj#sbah}(h]h ]h"]bsolah$]h&]uh1hhhhK hhhhubh)}(h*.. |cent| unicode:: U+000A2 .. CENT SIGNh]h¢}hj2sbah}(h]h ]h"]centah$]h&]uh1hhhhK hhhhubh)}(h&.. |colon| unicode:: U+0003A .. COLONh]h:}hjAsbah}(h]h ]h"]colonah$]h&]uh1hhhhK hhhhubh)}(h&.. |comma| unicode:: U+0002C .. COMMAh]h,}hjPsbah}(h]h ]h"]commaah$]h&]uh1hhhhKhhhhubh)}(h... |commat| unicode:: U+00040 .. COMMERCIAL ATh]h@}hj_sbah}(h]h ]h"]commatah$]h&]uh1hhhhKhhhhubh)}(h/.. |copy| unicode:: U+000A9 .. COPYRIGHT SIGNh]h©}hjnsbah}(h]h ]h"]copyah$]h&]uh1hhhhKhhhhubh)}(h... |curren| unicode:: U+000A4 .. CURRENCY SIGNh]h¤}hj}sbah}(h]h ]h"]currenah$]h&]uh1hhhhKhhhhubh)}(h0.. |darr| unicode:: U+02193 .. DOWNWARDS ARROWh]h↓}hjsbah}(h]h ]h"]darrah$]h&]uh1hhhhKhhhhubh)}(h,.. |deg| unicode:: U+000B0 .. DEGREE SIGNh]h°}hjsbah}(h]h ]h"]degah$]h&]uh1hhhhKhhhhubh)}(h... |divide| unicode:: U+000F7 .. DIVISION SIGNh]h÷}hjsbah}(h]h ]h"]divideah$]h&]uh1hhhhKhhhhubh)}(h,.. |dollar| unicode:: U+00024 .. DOLLAR SIGNh]h$}hjsbah}(h]h ]h"]dollarah$]h&]uh1hhhhKhhhhubh)}(h,.. |equals| unicode:: U+0003D .. EQUALS SIGNh]h=}hjsbah}(h]h ]h"]equalsah$]h&]uh1hhhhKhhhhubh)}(h1.. |excl| unicode:: U+00021 .. EXCLAMATION MARKh]h!}hjsbah}(h]h ]h"]exclah$]h&]uh1hhhhKhhhhubh)}(h9.. |frac12| unicode:: U+000BD .. VULGAR FRACTION ONE HALFh]h½}hjsbah}(h]h ]h"]frac12ah$]h&]uh1hhhhKhhhhubh)}(h<.. |frac14| unicode:: U+000BC .. VULGAR FRACTION ONE QUARTERh]h¼}hjsbah}(h]h ]h"]frac14ah$]h&]uh1hhhhKhhhhubh)}(h;.. |frac18| unicode:: U+0215B .. VULGAR FRACTION ONE EIGHTHh]h⅛}hjsbah}(h]h ]h"]frac18ah$]h&]uh1hhhhKhhhhubh)}(h?.. |frac34| unicode:: U+000BE .. VULGAR FRACTION THREE QUARTERSh]h¾}hjsbah}(h]h ]h"]frac34ah$]h&]uh1hhhhKhhhhubh)}(h>.. |frac38| unicode:: U+0215C .. VULGAR FRACTION THREE EIGHTHSh]h⅜}hj"sbah}(h]h ]h"]frac38ah$]h&]uh1hhhhKhhhhubh)}(h=.. |frac58| unicode:: U+0215D .. VULGAR FRACTION FIVE EIGHTHSh]h⅝}hj1sbah}(h]h ]h"]frac58ah$]h&]uh1hhhhKhhhhubh)}(h>.. |frac78| unicode:: U+0215E .. VULGAR FRACTION SEVEN EIGHTHSh]h⅞}hj@sbah}(h]h ]h"]frac78ah$]h&]uh1hhhhKhhhhubh)}(h2.. |gt| unicode:: U+0003E .. GREATER-THAN SIGNh]h>}hjOsbah}(h]h ]h"]gtah$]h&]uh1hhhhKhhhhubh)}(h9.. |half| unicode:: U+000BD .. VULGAR FRACTION ONE HALFh]h½}hj^sbah}(h]h ]h"]halfah$]h&]uh1hhhhK hhhhubh)}(h/.. |horbar| unicode:: U+02015 .. HORIZONTAL BARh]h―}hjmsbah}(h]h ]h"]horbarah$]h&]uh1hhhhK!hhhhubh)}(h'.. |hyphen| unicode:: U+02010 .. HYPHENh]h‐}hj|sbah}(h]h ]h"]hyphenah$]h&]uh1hhhhK"hhhhubh)}(h:.. |iexcl| unicode:: U+000A1 .. INVERTED EXCLAMATION MARKh]h¡}hjsbah}(h]h ]h"]iexclah$]h&]uh1hhhhK#hhhhubh)}(h7.. |iquest| unicode:: U+000BF .. INVERTED QUESTION MARKh]h¿}hjsbah}(h]h ]h"]iquestah$]h&]uh1hhhhK$hhhhubh)}(hJ.. |laquo| unicode:: U+000AB .. LEFT-POINTING DOUBLE ANGLE QUOTATION MARKh]h«}hjsbah}(h]h ]h"]laquoah$]h&]uh1hhhhK%hhhhubh)}(h0.. |larr| unicode:: U+02190 .. LEFTWARDS ARROWh]h←}hjsbah}(h]h ]h"]larrah$]h&]uh1hhhhK&hhhhubh)}(h3.. |lcub| unicode:: U+0007B .. LEFT CURLY BRACKETh]h{}hjsbah}(h]h ]h"]lcubah$]h&]uh1hhhhK'hhhhubh)}(h;.. |ldquo| unicode:: U+0201C .. LEFT DOUBLE QUOTATION MARKh]h“}hjsbah}(h]h ]h"]ldquoah$]h&]uh1hhhhK(hhhhubh)}(h).. |lowbar| unicode:: U+0005F .. LOW LINEh]h_}hjsbah}(h]h ]h"]lowbarah$]h&]uh1hhhhK)hhhhubh)}(h1.. |lpar| unicode:: U+00028 .. LEFT PARENTHESISh]h(}hjsbah}(h]h ]h"]lparah$]h&]uh1hhhhK*hhhhubh)}(h4.. |lsqb| unicode:: U+0005B .. LEFT SQUARE BRACKETh]h[}hjsbah}(h]h ]h"]lsqbah$]h&]uh1hhhhK+hhhhubh)}(h;.. |lsquo| unicode:: U+02018 .. LEFT SINGLE QUOTATION MARKh]h‘}hjsbah}(h]h ]h"]lsquoah$]h&]uh1hhhhK,hhhhubh)}(h/.. |lt| unicode:: U+0003C .. LESS-THAN SIGNh]h<}hj!sbah}(h]h ]h"]ltah$]h&]uh1hhhhK-hhhhubh)}(h+.. |micro| unicode:: U+000B5 .. MICRO SIGNh]hµ}hj0sbah}(h]h ]h"]microah$]h&]uh1hhhhK.hhhhubh)}(h+.. |middot| unicode:: U+000B7 .. MIDDLE DOTh]h·}hj?sbah}(h]h ]h"]middotah$]h&]uh1hhhhK/hhhhubh)}(h/.. |nbsp| unicode:: U+000A0 .. NO-BREAK SPACEh]h }hjNsbah}(h]h ]h"]nbspah$]h&]uh1hhhhK0hhhhubh)}(h).. |not| unicode:: U+000AC .. NOT SIGNh]h¬}hj]sbah}(h]h ]h"]notah$]h&]uh1hhhhK1hhhhubh)}(h,.. |num| unicode:: U+00023 .. NUMBER SIGNh]h#}hjlsbah}(h]h ]h"]numah$]h&]uh1hhhhK2hhhhubh)}(h).. |ohm| unicode:: U+02126 .. OHM SIGNh]hΩ}hj{sbah}(h]h ]h"]ohmah$]h&]uh1hhhhK3hhhhubh)}(h;.. |ordf| unicode:: U+000AA .. FEMININE ORDINAL INDICATORh]hª}hjsbah}(h]h ]h"]ordfah$]h&]uh1hhhhK4hhhhubh)}(h<.. |ordm| unicode:: U+000BA .. MASCULINE ORDINAL INDICATORh]hº}hjsbah}(h]h ]h"]ordmah$]h&]uh1hhhhK5hhhhubh)}(h-.. |para| unicode:: U+000B6 .. PILCROW SIGNh]h¶}hjsbah}(h]h ]h"]paraah$]h&]uh1hhhhK6hhhhubh)}(h-.. |percnt| unicode:: U+00025 .. PERCENT SIGNh]h%}hjsbah}(h]h ]h"]percntah$]h&]uh1hhhhK7hhhhubh)}(h*.. |period| unicode:: U+0002E .. FULL STOPh]h.}hjsbah}(h]h ]h"]periodah$]h&]uh1hhhhK8hhhhubh)}(h*.. |plus| unicode:: U+0002B .. PLUS SIGNh]h+}hjsbah}(h]h ]h"]plusah$]h&]uh1hhhhK9hhhhubh)}(h0.. |plusmn| unicode:: U+000B1 .. PLUS-MINUS SIGNh]h±}hjsbah}(h]h ]h"]plusmnah$]h&]uh1hhhhK:hhhhubh)}(h+.. |pound| unicode:: U+000A3 .. POUND SIGNh]h£}hjsbah}(h]h ]h"]poundah$]h&]uh1hhhhK;hhhhubh)}(h... |quest| unicode:: U+0003F .. QUESTION MARKh]h?}hjsbah}(h]h ]h"]questah$]h&]uh1hhhhKhhhhubh)}(h1.. |rarr| unicode:: U+02192 .. RIGHTWARDS ARROWh]h→}hj/sbah}(h]h ]h"]rarrah$]h&]uh1hhhhK?hhhhubh)}(h4.. |rcub| unicode:: U+0007D .. RIGHT CURLY BRACKETh]h}}hj>sbah}(h]h ]h"]rcubah$]h&]uh1hhhhK@hhhhubh)}(h<.. |rdquo| unicode:: U+0201D .. RIGHT DOUBLE QUOTATION MARKh]h”}hjMsbah}(h]h ]h"]rdquoah$]h&]uh1hhhhKAhhhhubh)}(h0.. |reg| unicode:: U+000AE .. REGISTERED SIGNh]h®}hj\sbah}(h]h ]h"]regah$]h&]uh1hhhhKBhhhhubh)}(h2.. |rpar| unicode:: U+00029 .. RIGHT PARENTHESISh]h)}hjksbah}(h]h ]h"]rparah$]h&]uh1hhhhKChhhhubh)}(h5.. |rsqb| unicode:: U+0005D .. RIGHT SQUARE BRACKETh]h]}hjzsbah}(h]h ]h"]rsqbah$]h&]uh1hhhhKDhhhhubh)}(h<.. |rsquo| unicode:: U+02019 .. RIGHT SINGLE QUOTATION MARKh]h’}hjsbah}(h]h ]h"]rsquoah$]h&]uh1hhhhKEhhhhubh)}(h-.. |sect| unicode:: U+000A7 .. SECTION SIGNh]h§}hjsbah}(h]h ]h"]sectah$]h&]uh1hhhhKFhhhhubh)}(h*.. |semi| unicode:: U+0003B .. SEMICOLONh]h;}hjsbah}(h]h ]h"]semiah$]h&]uh1hhhhKGhhhhubh)}(h,.. |shy| unicode:: U+000AD .. SOFT HYPHENh]h­}hjsbah}(h]h ]h"]shyah$]h&]uh1hhhhKHhhhhubh)}(h(.. |sol| unicode:: U+0002F .. SOLIDUSh]h/}hjsbah}(h]h ]h"]solah$]h&]uh1hhhhKIhhhhubh)}(h,.. |sung| unicode:: U+0266A .. EIGHTH NOTEh]h♪}hjsbah}(h]h ]h"]sungah$]h&]uh1hhhhKJhhhhubh)}(h0.. |sup1| unicode:: U+000B9 .. SUPERSCRIPT ONEh]h¹}hjsbah}(h]h ]h"]sup1ah$]h&]uh1hhhhKKhhhhubh)}(h0.. |sup2| unicode:: U+000B2 .. SUPERSCRIPT TWOh]h²}hjsbah}(h]h ]h"]sup2ah$]h&]uh1hhhhKLhhhhubh)}(h2.. |sup3| unicode:: U+000B3 .. SUPERSCRIPT THREEh]h³}hjsbah}(h]h ]h"]sup3ah$]h&]uh1hhhhKMhhhhubh)}(h4.. |times| unicode:: U+000D7 .. MULTIPLICATION SIGNh]h×}hjsbah}(h]h ]h"]timesah$]h&]uh1hhhhKNhhhhubh)}(h0.. |trade| unicode:: U+02122 .. TRADE MARK SIGNh]h™}hjsbah}(h]h ]h"]tradeah$]h&]uh1hhhhKOhhhhubh)}(h... |uarr| unicode:: U+02191 .. UPWARDS ARROWh]h↑}hj.sbah}(h]h ]h"]uarrah$]h&]uh1hhhhKPhhhhubh)}(h... |verbar| unicode:: U+0007C .. VERTICAL LINEh]h|}hj=sbah}(h]h ]h"]verbarah$]h&]uh1hhhhKQhhhhubh)}(h*.. |yen| unicode:: U+000A5 .. YEN SIGN h]h¥}hjLsbah}(h]h ]h"]yenah$]h&]uh1hhhhKRhhhhubhsection)}(hhh](htitle)}(h h]j)}(hLv Zheng h](h Lv Zheng <}(hjhhhNhNubh reference)}(hlv.zheng@intel.comh]hlv.zheng@intel.com}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurimailto:lv.zheng@intel.comuh1jhjubh>}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1jhhhK hjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1juhhhK hjrhhubeh}(h]h ]h"]h$]h&]uh1jphj]hhhhhKubj\)}(hhh](ja)}(hAbstracth]hAbstract}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1j`hjhhhhhKubj)}(hThis document describes the ACPICA project and the relationship between ACPICA and Linux. It also describes how ACPICA code in drivers/acpi/acpica, include/acpi and tools/power/acpi is automatically updated to follow the upstream.h]hThis document describes the ACPICA project and the relationship between ACPICA and Linux. It also describes how ACPICA code in drivers/acpi/acpica, include/acpi and tools/power/acpi is automatically updated to follow the upstream.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjhhubeh}(h]abstractah ]h"]abstractah$]h&]uh1j[hj]hhhhhKubj\)}(hhh](ja)}(hACPICA Projecth]hACPICA Project}(hj%hhhNhNubah}(h]h ]h"]h$]h&]uh1j`hj"hhhhhKubj)}(hXcThe ACPI Component Architecture (ACPICA) project provides an operating system (OS)-independent reference implementation of the Advanced Configuration and Power Interface Specification (ACPI). It has been adapted by various host OSes. By directly integrating ACPICA, Linux can also benefit from the application experiences of ACPICA from other host OSes.h]hXcThe ACPI Component Architecture (ACPICA) project provides an operating system (OS)-independent reference implementation of the Advanced Configuration and Power Interface Specification (ACPI). It has been adapted by various host OSes. By directly integrating ACPICA, Linux can also benefit from the application experiences of ACPICA from other host OSes.}(hj3hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhj"hhubj)}(hgThe homepage of ACPICA project is: www.acpica.org, it is maintained and supported by Intel Corporation.h]hgThe homepage of ACPICA project is: www.acpica.org, it is maintained and supported by Intel Corporation.}(hjAhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhj"hhubj)}(h_The following figure depicts the Linux ACPI subsystem where the ACPICA adaptation is included::h]h^The following figure depicts the Linux ACPI subsystem where the ACPICA adaptation is included:}(hjOhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhK!hj"hhubh literal_block)}(hX +---------------------------------------------------------+ | | | +---------------------------------------------------+ | | | +------------------+ | | | | | Table Management | | | | | +------------------+ | | | | +----------------------+ | | | | | Namespace Management | | | | | +----------------------+ | | | | +------------------+ ACPICA Components | | | | | Event Management | | | | | +------------------+ | | | | +---------------------+ | | | | | Resource Management | | | | | +---------------------+ | | | | +---------------------+ | | | | | Hardware Management | | | | | +---------------------+ | | | +---------------------------------------------------+ | | | | | +------------------+ | | | | | | | OS Service Layer | | | | | | | +------------------+ | | | | | +-------------------------------------------------|-+ | | | +--------------------+ | | | | | Device Enumeration | | | | | +--------------------+ | | | | +------------------+ | | | | | Power Management | | | | | +------------------+ Linux/ACPI Components | | | | +--------------------+ | | | | | Thermal Management | | | | | +--------------------+ | | | | +--------------------------+ | | | | | Drivers for ACPI Devices | | | | | +--------------------------+ | | | | +--------+ | | | | | ...... | | | | | +--------+ | | | +---------------------------------------------------+ | | | +---------------------------------------------------------+ Figure 1. Linux ACPI Software Componentsh]hX +---------------------------------------------------------+ | | | +---------------------------------------------------+ | | | +------------------+ | | | | | Table Management | | | | | +------------------+ | | | | +----------------------+ | | | | | Namespace Management | | | | | +----------------------+ | | | | +------------------+ ACPICA Components | | | | | Event Management | | | | | +------------------+ | | | | +---------------------+ | | | | | Resource Management | | | | | +---------------------+ | | | | +---------------------+ | | | | | Hardware Management | | | | | +---------------------+ | | | +---------------------------------------------------+ | | | | | +------------------+ | | | | | | | OS Service Layer | | | | | | | +------------------+ | | | | | +-------------------------------------------------|-+ | | | +--------------------+ | | | | | Device Enumeration | | | | | +--------------------+ | | | | +------------------+ | | | | | Power Management | | | | | +------------------+ Linux/ACPI Components | | | | +--------------------+ | | | | | Thermal Management | | | | | +--------------------+ | | | | +--------------------------+ | | | | | Drivers for ACPI Devices | | | | | +--------------------------+ | | | | +--------+ | | | | | ...... | | | | | +--------+ | | | +---------------------------------------------------+ | | | +---------------------------------------------------------+ Figure 1. Linux ACPI Software Components}hj_sbah}(h]h ]h"]h$]h&]hhuh1j]hhhK$hj"hhubhnote)}(hXA. OS Service Layer - Provided by Linux to offer OS dependent implementation of the predefined ACPICA interfaces (acpi_os_*). :: include/acpi/acpiosxf.h drivers/acpi/osl.c include/acpi/platform include/asm/acenv.h B. ACPICA Functionality - Released from ACPICA code base to offer OS independent implementation of the ACPICA interfaces (acpi_*). :: drivers/acpi/acpica include/acpi/ac*.h tools/power/acpi C. Linux/ACPI Functionality - Providing Linux specific ACPI functionality to the other Linux kernel subsystems and user space programs. :: drivers/acpi include/linux/acpi.h include/linux/acpi*.h include/acpi tools/power/acpi D. Architecture Specific ACPICA/ACPI Functionalities - Provided by the ACPI subsystem to offer architecture specific implementation of the ACPI interfaces. They are Linux specific components and are out of the scope of this document. :: include/asm/acpi.h include/asm/acpi*.h arch/*/acpih]henumerated_list)}(hhh](h list_item)}(hOS Service Layer - Provided by Linux to offer OS dependent implementation of the predefined ACPICA interfaces (acpi_os_*). :: include/acpi/acpiosxf.h drivers/acpi/osl.c include/acpi/platform include/asm/acenv.hh](j)}(h}OS Service Layer - Provided by Linux to offer OS dependent implementation of the predefined ACPICA interfaces (acpi_os_*). ::h]hzOS Service Layer - Provided by Linux to offer OS dependent implementation of the predefined ACPICA interfaces (acpi_os_*).}(hj~hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKQhjzubj^)}(hTinclude/acpi/acpiosxf.h drivers/acpi/osl.c include/acpi/platform include/asm/acenv.hh]hTinclude/acpi/acpiosxf.h drivers/acpi/osl.c include/acpi/platform include/asm/acenv.h}hjsbah}(h]h ]h"]h$]h&]hhuh1j]hhhKUhjzubeh}(h]h ]h"]h$]h&]uh1jxhjuubjy)}(hACPICA Functionality - Released from ACPICA code base to offer OS independent implementation of the ACPICA interfaces (acpi_*). :: drivers/acpi/acpica include/acpi/ac*.h tools/power/acpih](j)}(hACPICA Functionality - Released from ACPICA code base to offer OS independent implementation of the ACPICA interfaces (acpi_*). ::h]hACPICA Functionality - Released from ACPICA code base to offer OS independent implementation of the ACPICA interfaces (acpi_*).}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKYhjubj^)}(h7drivers/acpi/acpica include/acpi/ac*.h tools/power/acpih]h7drivers/acpi/acpica include/acpi/ac*.h tools/power/acpi}hjsbah}(h]h ]h"]h$]h&]hhuh1j]hhhK]hjubeh}(h]h ]h"]h$]h&]uh1jxhjuubjy)}(hLinux/ACPI Functionality - Providing Linux specific ACPI functionality to the other Linux kernel subsystems and user space programs. :: drivers/acpi include/linux/acpi.h include/linux/acpi*.h include/acpi tools/power/acpih](j)}(hLinux/ACPI Functionality - Providing Linux specific ACPI functionality to the other Linux kernel subsystems and user space programs. ::h]hLinux/ACPI Functionality - Providing Linux specific ACPI functionality to the other Linux kernel subsystems and user space programs.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhK`hjubj^)}(hUdrivers/acpi include/linux/acpi.h include/linux/acpi*.h include/acpi tools/power/acpih]hUdrivers/acpi include/linux/acpi.h include/linux/acpi*.h include/acpi tools/power/acpi}hjsbah}(h]h ]h"]h$]h&]hhuh1j]hhhKehjubeh}(h]h ]h"]h$]h&]uh1jxhjuubjy)}(hX$Architecture Specific ACPICA/ACPI Functionalities - Provided by the ACPI subsystem to offer architecture specific implementation of the ACPI interfaces. They are Linux specific components and are out of the scope of this document. :: include/asm/acpi.h include/asm/acpi*.h arch/*/acpih](j)}(hArchitecture Specific ACPICA/ACPI Functionalities - Provided by the ACPI subsystem to offer architecture specific implementation of the ACPI interfaces. They are Linux specific components and are out of the scope of this document. ::h]hArchitecture Specific ACPICA/ACPI Functionalities - Provided by the ACPI subsystem to offer architecture specific implementation of the ACPI interfaces. They are Linux specific components and are out of the scope of this document.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKjhjubj^)}(h2include/asm/acpi.h include/asm/acpi*.h arch/*/acpih]h2include/asm/acpi.h include/asm/acpi*.h arch/*/acpi}hjsbah}(h]h ]h"]h$]h&]hhuh1j]hhhKphjubeh}(h]h ]h"]h$]h&]uh1jxhjuubeh}(h]h ]h"]h$]h&]enumtype upperalphaprefixhsuffix.uh1jshjoubah}(h]h ]h"]h$]h&]uh1jmhj"hhhNhNubeh}(h]acpica-projectah ]h"]acpica projectah$]h&]uh1j[hj]hhhhhKubj\)}(hhh](ja)}(hACPICA Releaseh]hACPICA Release}(hj.hhhNhNubah}(h]h ]h"]h$]h&]uh1j`hj+hhhhhKuubj)}(hThe ACPICA project maintains its code base at the following repository URL: https://github.com/open-acpica/acpica.git. As a rule, a release is made every month.h](hLThe ACPICA project maintains its code base at the following repository URL: }(hj<hhhNhNubj)}(h)https://github.com/open-acpica/acpica.gith]h)https://github.com/open-acpica/acpica.git}(hjDhhhNhNubah}(h]h ]h"]h$]h&]refurijFuh1jhj<ubh+. As a rule, a release is made every month.}(hj<hhhNhNubeh}(h]h ]h"]h$]h&]uh1jhhhKwhj+hhubj)}(hX!As the coding style adopted by the ACPICA project is not acceptable by Linux, there is a release process to convert the ACPICA git commits into Linux patches. The patches generated by this process are referred to as "linuxized ACPICA patches". The release process is carried out on a local copy the ACPICA git repository. Each commit in the monthly release is converted into a linuxized ACPICA patch. Together, they form the monthly ACPICA release patchset for the Linux ACPI community. This process is illustrated in the following figure::h]hX$As the coding style adopted by the ACPICA project is not acceptable by Linux, there is a release process to convert the ACPICA git commits into Linux patches. The patches generated by this process are referred to as “linuxized ACPICA patches”. The release process is carried out on a local copy the ACPICA git repository. Each commit in the monthly release is converted into a linuxized ACPICA patch. Together, they form the monthly ACPICA release patchset for the Linux ACPI community. This process is illustrated in the following figure:}(hj]hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhK{hj+hhubj^)}(hX+-----------------------------+ | acpica / master (-) commits | +-----------------------------+ /|\ | | \|/ | /---------------------\ +----------------------+ | < Linuxize repo Utility >-->| old linuxized acpica |--+ | \---------------------/ +----------------------+ | | | /---------\ | < git reset > \ \---------/ \ /|\ /+-+ | / | +-----------------------------+ | | | acpica / master (+) commits | | | +-----------------------------+ | | | | | \|/ | | /-----------------------\ +----------------------+ | | < Linuxize repo Utilities >-->| new linuxized acpica |--+ | \-----------------------/ +----------------------+ | \|/ +--------------------------+ /----------------------\ | Linuxized ACPICA Patches |<----------------< Linuxize patch Utility > +--------------------------+ \----------------------/ | \|/ /---------------------------\ < Linux ACPI Community Review > \---------------------------/ | \|/ +-----------------------+ /------------------\ +----------------+ | linux-pm / linux-next |-->< Linux Merge Window >-->| linux / master | +-----------------------+ \------------------/ +----------------+ Figure 2. ACPICA -> Linux Upstream Processh]hX+-----------------------------+ | acpica / master (-) commits | +-----------------------------+ /|\ | | \|/ | /---------------------\ +----------------------+ | < Linuxize repo Utility >-->| old linuxized acpica |--+ | \---------------------/ +----------------------+ | | | /---------\ | < git reset > \ \---------/ \ /|\ /+-+ | / | +-----------------------------+ | | | acpica / master (+) commits | | | +-----------------------------+ | | | | | \|/ | | /-----------------------\ +----------------------+ | | < Linuxize repo Utilities >-->| new linuxized acpica |--+ | \-----------------------/ +----------------------+ | \|/ +--------------------------+ /----------------------\ | Linuxized ACPICA Patches |<----------------< Linuxize patch Utility > +--------------------------+ \----------------------/ | \|/ /---------------------------\ < Linux ACPI Community Review > \---------------------------/ | \|/ +-----------------------+ /------------------\ +----------------+ | linux-pm / linux-next |-->< Linux Merge Window >-->| linux / master | +-----------------------+ \------------------/ +----------------+ Figure 2. ACPICA -> Linux Upstream Process}hjksbah}(h]h ]h"]h$]h&]hhuh1j]hhhKhj+hhubjn)}(hXt A. Linuxize Utilities - Provided by the ACPICA repository, including a utility located in source/tools/acpisrc folder and a number of scripts located in generate/linux folder. B. acpica / master - "master" branch of the git repository at . C. linux-pm / linux-next - "linux-next" branch of the git repository at . D. linux / master - "master" branch of the git repository at . Before the linuxized ACPICA patches are sent to the Linux ACPI community for review, there is a quality assurance build test process to reduce porting issues. Currently this build process only takes care of the following kernel configuration options: CONFIG_ACPI/CONFIG_ACPI_DEBUG/CONFIG_ACPI_DEBUGGERh](h block_quote)}(hX<A. Linuxize Utilities - Provided by the ACPICA repository, including a utility located in source/tools/acpisrc folder and a number of scripts located in generate/linux folder. B. acpica / master - "master" branch of the git repository at . C. linux-pm / linux-next - "linux-next" branch of the git repository at . D. linux / master - "master" branch of the git repository at . h]jt)}(hhh](jy)}(hLinuxize Utilities - Provided by the ACPICA repository, including a utility located in source/tools/acpisrc folder and a number of scripts located in generate/linux folder.h]j)}(hLinuxize Utilities - Provided by the ACPICA repository, including a utility located in source/tools/acpisrc folder and a number of scripts located in generate/linux folder.h]hLinuxize Utilities - Provided by the ACPICA repository, including a utility located in source/tools/acpisrc folder and a number of scripts located in generate/linux folder.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjubah}(h]h ]h"]h$]h&]uh1jxhjubjy)}(hgacpica / master - "master" branch of the git repository at .h]j)}(hgacpica / master - "master" branch of the git repository at .h](h@acpica / master - “master” branch of the git repository at <}(hjhhhNhNubj)}(h)https://github.com/open-acpica/acpica.gith]h)https://github.com/open-acpica/acpica.git}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurijuh1jhjubh>.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1jhhhKhjubah}(h]h ]h"]h$]h&]uh1jxhjubjy)}(hlinux-pm / linux-next - "linux-next" branch of the git repository at .h]j)}(hlinux-pm / linux-next - "linux-next" branch of the git repository at .h](hJlinux-pm / linux-next - “linux-next” branch of the git repository at <}(hjhhhNhNubj)}(hChttps://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.gith]hChttps://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurijuh1jhjubh>.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1jhhhKhjubah}(h]h ]h"]h$]h&]uh1jxhjubjy)}(hlinux / master - "master" branch of the git repository at . h]j)}(hlinux / master - "master" branch of the git repository at .h](h?linux / master - “master” branch of the git repository at <}(hjhhhNhNubj)}(hBhttps://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.gith]hBhttps://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurijuh1jhjubh>.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1jhhhKhjubah}(h]h ]h"]h$]h&]uh1jxhjubeh}(h]h ]h"]h$]h&]jjjhjjuh1jshjubah}(h]h ]h"]h$]h&]uh1j}hhhKhjyubj)}(hX.Before the linuxized ACPICA patches are sent to the Linux ACPI community for review, there is a quality assurance build test process to reduce porting issues. Currently this build process only takes care of the following kernel configuration options: CONFIG_ACPI/CONFIG_ACPI_DEBUG/CONFIG_ACPI_DEBUGGERh]hX.Before the linuxized ACPICA patches are sent to the Linux ACPI community for review, there is a quality assurance build test process to reduce porting issues. Currently this build process only takes care of the following kernel configuration options: CONFIG_ACPI/CONFIG_ACPI_DEBUG/CONFIG_ACPI_DEBUGGER}(hj+hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjyubeh}(h]h ]h"]h$]h&]uh1jmhj+hhhhhNubeh}(h]acpica-releaseah ]h"]acpica releaseah$]h&]uh1j[hj]hhhhhKuubj\)}(hhh](ja)}(hACPICA Divergencesh]hACPICA Divergences}(hjJhhhNhNubah}(h]h ]h"]h$]h&]uh1j`hjGhhhhhKubj)}(hXMIdeally, all of the ACPICA commits should be converted into Linux patches automatically without manual modifications, the "linux / master" tree should contain the ACPICA code that exactly corresponds to the ACPICA code contained in "new linuxized acpica" tree and it should be possible to run the release process fully automatically.h]hXUIdeally, all of the ACPICA commits should be converted into Linux patches automatically without manual modifications, the “linux / master” tree should contain the ACPICA code that exactly corresponds to the ACPICA code contained in “new linuxized acpica” tree and it should be possible to run the release process fully automatically.}(hjXhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjGhhubj)}(hAs a matter of fact, however, there are source code differences between the ACPICA code in Linux and the upstream ACPICA code, referred to as "ACPICA Divergences".h]hAs a matter of fact, however, there are source code differences between the ACPICA code in Linux and the upstream ACPICA code, referred to as “ACPICA Divergences”.}(hjfhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjGhhubhdefinition_list)}(hhh]hdefinition_list_item)}(hXThe various sources of ACPICA divergences include: 1. Legacy divergences - Before the current ACPICA release process was established, there already had been divergences between Linux and ACPICA. Over the past several years those divergences have been greatly reduced, but there still are several ones and it takes time to figure out the underlying reasons for their existence. 2. Manual modifications - Any manual modification (eg. coding style fixes) made directly in the Linux sources obviously hurts the ACPICA release automation. Thus it is recommended to fix such issues in the ACPICA upstream source code and generate the linuxized fix using the ACPICA release utilities (please refer to Section 4 below for the details). 3. Linux specific features - Sometimes it's impossible to use the current ACPICA APIs to implement features required by the Linux kernel, so Linux developers occasionally have to change ACPICA code directly. Those changes may not be acceptable by ACPICA upstream and in such cases they are left as committed ACPICA divergences unless the ACPICA side can implement new mechanisms as replacements for them. 4. ACPICA release fixups - ACPICA only tests commits using a set of the user space simulation utilities, thus the linuxized ACPICA patches may break the Linux kernel, leaving us build/boot failures. In order to avoid breaking Linux bisection, fixes are applied directly to the linuxized ACPICA patches during the release process. When the release fixups are backported to the upstream ACPICA sources, they must follow the upstream ACPICA rules and so further modifications may appear. That may result in the appearance of new divergences. 5. Fast tracking of ACPICA commits - Some ACPICA commits are regression fixes or stable-candidate material, so they are applied in advance with respect to the ACPICA release process. If such commits are reverted or rebased on the ACPICA side in order to offer better solutions, new ACPICA divergences are generated. h](hterm)}(h2The various sources of ACPICA divergences include:h]h2The various sources of ACPICA divergences include:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhj{ubh definition)}(hhh]jt)}(hhh](jy)}(hXBLegacy divergences - Before the current ACPICA release process was established, there already had been divergences between Linux and ACPICA. Over the past several years those divergences have been greatly reduced, but there still are several ones and it takes time to figure out the underlying reasons for their existence.h]j)}(hXBLegacy divergences - Before the current ACPICA release process was established, there already had been divergences between Linux and ACPICA. Over the past several years those divergences have been greatly reduced, but there still are several ones and it takes time to figure out the underlying reasons for their existence.h]hXBLegacy divergences - Before the current ACPICA release process was established, there already had been divergences between Linux and ACPICA. Over the past several years those divergences have been greatly reduced, but there still are several ones and it takes time to figure out the underlying reasons for their existence.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjubah}(h]h ]h"]h$]h&]uh1jxhjubjy)}(hX\Manual modifications - Any manual modification (eg. coding style fixes) made directly in the Linux sources obviously hurts the ACPICA release automation. Thus it is recommended to fix such issues in the ACPICA upstream source code and generate the linuxized fix using the ACPICA release utilities (please refer to Section 4 below for the details).h]j)}(hX\Manual modifications - Any manual modification (eg. coding style fixes) made directly in the Linux sources obviously hurts the ACPICA release automation. Thus it is recommended to fix such issues in the ACPICA upstream source code and generate the linuxized fix using the ACPICA release utilities (please refer to Section 4 below for the details).h]hX\Manual modifications - Any manual modification (eg. coding style fixes) made directly in the Linux sources obviously hurts the ACPICA release automation. Thus it is recommended to fix such issues in the ACPICA upstream source code and generate the linuxized fix using the ACPICA release utilities (please refer to Section 4 below for the details).}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjubah}(h]h ]h"]h$]h&]uh1jxhjubjy)}(hXLinux specific features - Sometimes it's impossible to use the current ACPICA APIs to implement features required by the Linux kernel, so Linux developers occasionally have to change ACPICA code directly. Those changes may not be acceptable by ACPICA upstream and in such cases they are left as committed ACPICA divergences unless the ACPICA side can implement new mechanisms as replacements for them.h]j)}(hXLinux specific features - Sometimes it's impossible to use the current ACPICA APIs to implement features required by the Linux kernel, so Linux developers occasionally have to change ACPICA code directly. Those changes may not be acceptable by ACPICA upstream and in such cases they are left as committed ACPICA divergences unless the ACPICA side can implement new mechanisms as replacements for them.h]hXLinux specific features - Sometimes it’s impossible to use the current ACPICA APIs to implement features required by the Linux kernel, so Linux developers occasionally have to change ACPICA code directly. Those changes may not be acceptable by ACPICA upstream and in such cases they are left as committed ACPICA divergences unless the ACPICA side can implement new mechanisms as replacements for them.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjubah}(h]h ]h"]h$]h&]uh1jxhjubjy)}(hXACPICA release fixups - ACPICA only tests commits using a set of the user space simulation utilities, thus the linuxized ACPICA patches may break the Linux kernel, leaving us build/boot failures. In order to avoid breaking Linux bisection, fixes are applied directly to the linuxized ACPICA patches during the release process. When the release fixups are backported to the upstream ACPICA sources, they must follow the upstream ACPICA rules and so further modifications may appear. That may result in the appearance of new divergences.h]j)}(hXACPICA release fixups - ACPICA only tests commits using a set of the user space simulation utilities, thus the linuxized ACPICA patches may break the Linux kernel, leaving us build/boot failures. In order to avoid breaking Linux bisection, fixes are applied directly to the linuxized ACPICA patches during the release process. When the release fixups are backported to the upstream ACPICA sources, they must follow the upstream ACPICA rules and so further modifications may appear. That may result in the appearance of new divergences.h]hXACPICA release fixups - ACPICA only tests commits using a set of the user space simulation utilities, thus the linuxized ACPICA patches may break the Linux kernel, leaving us build/boot failures. In order to avoid breaking Linux bisection, fixes are applied directly to the linuxized ACPICA patches during the release process. When the release fixups are backported to the upstream ACPICA sources, they must follow the upstream ACPICA rules and so further modifications may appear. That may result in the appearance of new divergences.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjubah}(h]h ]h"]h$]h&]uh1jxhjubjy)}(hX:Fast tracking of ACPICA commits - Some ACPICA commits are regression fixes or stable-candidate material, so they are applied in advance with respect to the ACPICA release process. If such commits are reverted or rebased on the ACPICA side in order to offer better solutions, new ACPICA divergences are generated. h]j)}(hX9Fast tracking of ACPICA commits - Some ACPICA commits are regression fixes or stable-candidate material, so they are applied in advance with respect to the ACPICA release process. If such commits are reverted or rebased on the ACPICA side in order to offer better solutions, new ACPICA divergences are generated.h]hX9Fast tracking of ACPICA commits - Some ACPICA commits are regression fixes or stable-candidate material, so they are applied in advance with respect to the ACPICA release process. If such commits are reverted or rebased on the ACPICA side in order to offer better solutions, new ACPICA divergences are generated.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjubah}(h]h ]h"]h$]h&]uh1jxhjubeh}(h]h ]h"]h$]h&]jarabicjhjjuh1jshjubah}(h]h ]h"]h$]h&]uh1jhj{ubeh}(h]h ]h"]h$]h&]uh1jyhhhKhjvubah}(h]h ]h"]h$]h&]uh1jthjGhhhNhNubeh}(h]acpica-divergencesah ]h"]acpica divergencesah$]h&]uh1j[hj]hhhhhKubj\)}(hhh](ja)}(hACPICA Developmenth]hACPICA Development}(hj3 hhhNhNubah}(h]h ]h"]h$]h&]uh1j`hj0 hhhhhKubj)}(hThis paragraph guides Linux developers to use the ACPICA upstream release utilities to obtain Linux patches corresponding to upstream ACPICA commits before they become available from the ACPICA release process.h]hThis paragraph guides Linux developers to use the ACPICA upstream release utilities to obtain Linux patches corresponding to upstream ACPICA commits before they become available from the ACPICA release process.}(hjA hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhj0 hhubj~)}(hX1. Cherry-pick an ACPICA commit First you need to git clone the ACPICA repository and the ACPICA change you want to cherry pick must be committed into the local repository. Then the gen-patch.sh command can help to cherry-pick an ACPICA commit from the ACPICA local repository:: $ git clone https://github.com/open-acpica/acpica $ cd acpica $ generate/linux/gen-patch.sh -u [commit ID] Here the commit ID is the ACPICA local repository commit ID you want to cherry pick. It can be omitted if the commit is "HEAD". 2. Cherry-pick recent ACPICA commits Sometimes you need to rebase your code on top of the most recent ACPICA changes that haven't been applied to Linux yet. You can generate the ACPICA release series yourself and rebase your code on top of the generated ACPICA release patches:: $ git clone https://github.com/open-acpica/acpica $ cd acpica $ generate/linux/make-patches.sh -u [commit ID] The commit ID should be the last ACPICA commit accepted by Linux. Usually, it is the commit modifying ACPI_CA_VERSION. It can be found by executing "git blame source/include/acpixf.h" and referencing the line that contains "ACPI_CA_VERSION". 3. Inspect the current divergences If you have local copies of both Linux and upstream ACPICA, you can generate a diff file indicating the state of the current divergences:: # git clone https://github.com/open-acpica/acpica # git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git # cd acpica # generate/linux/divergence.sh -s ../linuxh](jt)}(hhh]jy)}(hCherry-pick an ACPICA commit h]j)}(hCherry-pick an ACPICA commith]hCherry-pick an ACPICA commit}(hjZ hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjV ubah}(h]h ]h"]h$]h&]uh1jxhjS ubah}(h]h ]h"]h$]h&]jj jhjjuh1jshjO ubj)}(hFirst you need to git clone the ACPICA repository and the ACPICA change you want to cherry pick must be committed into the local repository.h]hFirst you need to git clone the ACPICA repository and the ACPICA change you want to cherry pick must be committed into the local repository.}(hjt hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjO ubj)}(hiThen the gen-patch.sh command can help to cherry-pick an ACPICA commit from the ACPICA local repository::h]hhThen the gen-patch.sh command can help to cherry-pick an ACPICA commit from the ACPICA local repository:}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjO ubj^)}(hj$ git clone https://github.com/open-acpica/acpica $ cd acpica $ generate/linux/gen-patch.sh -u [commit ID]h]hj$ git clone https://github.com/open-acpica/acpica $ cd acpica $ generate/linux/gen-patch.sh -u [commit ID]}hj sbah}(h]h ]h"]h$]h&]hhuh1j]hhhKhjO ubj)}(hHere the commit ID is the ACPICA local repository commit ID you want to cherry pick. It can be omitted if the commit is "HEAD".h]hHere the commit ID is the ACPICA local repository commit ID you want to cherry pick. It can be omitted if the commit is “HEAD”.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjO ubjt)}(hhh]jy)}(h"Cherry-pick recent ACPICA commits h]j)}(h!Cherry-pick recent ACPICA commitsh]h!Cherry-pick recent ACPICA commits}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhj ubah}(h]h ]h"]h$]h&]uh1jxhj ubah}(h]h ]h"]h$]h&]jj jhjjstartKuh1jshjO ubj)}(hwSometimes you need to rebase your code on top of the most recent ACPICA changes that haven't been applied to Linux yet.h]hySometimes you need to rebase your code on top of the most recent ACPICA changes that haven’t been applied to Linux yet.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhjO ubj)}(hyYou can generate the ACPICA release series yourself and rebase your code on top of the generated ACPICA release patches::h]hxYou can generate the ACPICA release series yourself and rebase your code on top of the generated ACPICA release patches:}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhjO ubj^)}(hm$ git clone https://github.com/open-acpica/acpica $ cd acpica $ generate/linux/make-patches.sh -u [commit ID]h]hm$ git clone https://github.com/open-acpica/acpica $ cd acpica $ generate/linux/make-patches.sh -u [commit ID]}hj sbah}(h]h ]h"]h$]h&]hhuh1j]hhhMhjO ubj)}(hThe commit ID should be the last ACPICA commit accepted by Linux. Usually, it is the commit modifying ACPI_CA_VERSION. It can be found by executing "git blame source/include/acpixf.h" and referencing the line that contains "ACPI_CA_VERSION".h]hThe commit ID should be the last ACPICA commit accepted by Linux. Usually, it is the commit modifying ACPI_CA_VERSION. It can be found by executing “git blame source/include/acpixf.h” and referencing the line that contains “ACPI_CA_VERSION”.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhM hjO ubjt)}(hhh]jy)}(h Inspect the current divergences h]j)}(hInspect the current divergencesh]hInspect the current divergences}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhj ubah}(h]h ]h"]h$]h&]uh1jxhj ubah}(h]h ]h"]h$]h&]jj jhjjj Kuh1jshjO ubj)}(hIf you have local copies of both Linux and upstream ACPICA, you can generate a diff file indicating the state of the current divergences::h]hIf you have local copies of both Linux and upstream ACPICA, you can generate a diff file indicating the state of the current divergences:}(hj' hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhMhjO ubj^)}(h# git clone https://github.com/open-acpica/acpica # git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git # cd acpica # generate/linux/divergence.sh -s ../linuxh]h# git clone https://github.com/open-acpica/acpica # git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git # cd acpica # generate/linux/divergence.sh -s ../linux}hj5 sbah}(h]h ]h"]h$]h&]hhuh1j]hhhMhjO ubeh}(h]h ]h"]h$]h&]uh1j}hhhKhj0 hhubeh}(h]acpica-developmentah ]h"]acpica developmentah$]h&]uh1j[hj]hhhhhKubeh}(h]:linuxized-acpica-introduction-to-acpica-release-automationah ]h"]j2jMjAj\jPjkj_jzjnjj}jjjjjjjjjjjjjjjjjjjjj.j"j=j1jLj@j[jOjjj^jyjmjj|jjjjjjjjjjjjjjjjjjjjj-j!j<j0jKj?jZjNjij]jxjljj{jjjjjjjjjjjjjjjjjjjjj,j j;j/jJj>jYjMjhj\jwjkjjzjjjjjjjjjjjjjjjjj jjjj+jj:j.jIj=jXjLusubstitution_names}(amphaposjastjbrvbarj bsolj/centj>colonjMcommaj\commatjkcopyjzcurrenjdarrjdegjdividejdollarjequalsjexcljfrac12jfrac14jfrac18jfrac34jfrac38j.frac58j=frac78jLgtj[halfjjhorbarjyhyphenjiexcljiquestjlaquojlarrjlcubjldquojlowbarjlparjlsqbjlsquojltj-microj<middotjKnbspjZnotjinumjxohmjordfjordmjparajpercntjperiodjplusjplusmnjpoundjquestjquotjraquoj,rarrj;rcubjJrdquojYregjhrparjwrsqbjrsquojsectjsemijshyjsoljsungjsup1jsup2jsup3j timesjtradej+uarrj:verbarjIyenjXurefnames}refids}nameids}(jV jS jjj(j%jDjAj- j* jN jK u nametypes}(jV jj(jDj- jN uh}(jS j]jjj%j"jAj+j* jGjK j0 u footnote_refs} citation_refs} autofootnotes]autofootnote_refs]symbol_footnotes]symbol_footnote_refs] footnotes] citations]autofootnote_startKsymbol_footnote_startK id_counter collectionsCounter}Rparse_messages](hsystem_message)}(hhh]j)}(h:Enumerated list start value not ordinal-1: "2" (ordinal 2)h]h>Enumerated list start value not ordinal-1: “2” (ordinal 2)}(hj/ hhhNhNubah}(h]h ]h"]h$]h&]uh1jhj, ubah}(h]h ]h"]h$]h&]levelKtypeINFOsourcehnjlineKuh1j* hjO ubj+ )}(hhh]j)}(h:Enumerated list start value not ordinal-1: "3" (ordinal 3)h]h>Enumerated list start value not ordinal-1: “3” (ordinal 3)}(hjK hhhNhNubah}(h]h ]h"]h$]h&]uh1jhjH ubah}(h]h ]h"]h$]h&]levelKtypejE sourcehnjlineKuh1j* hjO ubetransform_messages] transformerN include_log]2Documentation/driver-api/acpi/linuxized-acpica.rst(NNNNta decorationNhhub.