Lines Matching +full:quality +full:- +full:of +full:- +full:service
1 .. SPDX-License-Identifier: GPL-2.0
5 Linuxized ACPICA - Introduction to ACPICA Release Automation
8 :Copyright: |copy| 2013-2016, Intel Corporation
24 system (OS)-independent reference implementation of the Advanced
27 also benefit from the application experiences of ACPICA from other host
30 The homepage of ACPICA project is: www.acpica.org, it is maintained and
36 +---------------------------------------------------------+
38 | +---------------------------------------------------+ |
39 | | +------------------+ | |
41 | | +------------------+ | |
42 | | +----------------------+ | |
44 | | +----------------------+ | |
45 | | +------------------+ ACPICA Components | |
47 | | +------------------+ | |
48 | | +---------------------+ | |
50 | | +---------------------+ | |
51 | | +---------------------+ | |
53 | | +---------------------+ | |
54 | +---------------------------------------------------+ | |
55 | | | +------------------+ | | |
56 | | | | OS Service Layer | | | |
57 | | | +------------------+ | | |
58 | | +-------------------------------------------------|-+ |
59 | | +--------------------+ | |
61 | | +--------------------+ | |
62 | | +------------------+ | |
64 | | +------------------+ Linux/ACPI Components | |
65 | | +--------------------+ | |
67 | | +--------------------+ | |
68 | | +--------------------------+ | |
70 | | +--------------------------+ | |
71 | | +--------+ | |
73 | | +--------+ | |
74 | +---------------------------------------------------+ |
76 +---------------------------------------------------------+
81 A. OS Service Layer - Provided by Linux to offer OS dependent
82 implementation of the predefined ACPICA interfaces (acpi_os_*).
89 B. ACPICA Functionality - Released from ACPICA code base to offer
90 OS independent implementation of the ACPICA interfaces (acpi_*).
96 C. Linux/ACPI Functionality - Providing Linux specific ACPI
106 D. Architecture Specific ACPICA/ACPI Functionalities - Provided by the
107 ACPI subsystem to offer architecture specific implementation of the
108 ACPI interfaces. They are Linux specific components and are out of
109 the scope of this document.
132 +-----------------------------+
133 | acpica / master (-) commits |
134 +-----------------------------+
137 | /---------------------\ +----------------------+
138 | < Linuxize repo Utility >-->| old linuxized acpica |--+
139 | \---------------------/ +----------------------+ |
141 /---------\ |
143 \---------/ \
144 /|\ /+-+
146 +-----------------------------+ | |
148 +-----------------------------+ | |
151 /-----------------------\ +----------------------+ | |
152 < Linuxize repo Utilities >-->| new linuxized acpica |--+ |
153 \-----------------------/ +----------------------+ |
155 +--------------------------+ /----------------------\
156 | Linuxized ACPICA Patches |<----------------< Linuxize patch Utility >
157 +--------------------------+ \----------------------/
160 /---------------------------\
162 \---------------------------/
165 +-----------------------+ /------------------\ +----------------+
166 | linux-pm / linux-next |-->< Linux Merge Window >-->| linux / master |
167 +-----------------------+ \------------------/ +----------------+
169 Figure 2. ACPICA -> Linux Upstream Process
172 A. Linuxize Utilities - Provided by the ACPICA repository, including a
173 utility located in source/tools/acpisrc folder and a number of
175 B. acpica / master - "master" branch of the git repository at
177 C. linux-pm / linux-next - "linux-next" branch of the git repository at
178 <https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git>.
179 D. linux / master - "master" branch of the git repository at
183 for review, there is a quality assurance build test process to reduce
184 porting issues. Currently this build process only takes care of the
191 Ideally, all of the ACPICA commits should be converted into Linux patches
197 As a matter of fact, however, there are source code differences between
201 The various sources of ACPICA divergences include:
202 1. Legacy divergences - Before the current ACPICA release process was
207 2. Manual modifications - Any manual modification (eg. coding style fixes)
212 3. Linux specific features - Sometimes it's impossible to use the
218 4. ACPICA release fixups - ACPICA only tests commits using a set of the
225 That may result in the appearance of new divergences.
226 5. Fast tracking of ACPICA commits - Some ACPICA commits are regression
227 fixes or stable-candidate material, so they are applied in advance with
239 1. Cherry-pick an ACPICA commit
244 Then the gen-patch.sh command can help to cherry-pick an ACPICA commit
249 $ generate/linux/gen-patch.sh -u [commit ID]
254 2. Cherry-pick recent ACPICA commits
256 Sometimes you need to rebase your code on top of the most recent ACPICA
260 top of the generated ACPICA release patches::
264 $ generate/linux/make-patches.sh -u [commit ID]
273 If you have local copies of both Linux and upstream ACPICA, you can generate
274 a diff file indicating the state of the current divergences::
279 # generate/linux/divergence.sh -s ../linux