summaryrefslogtreecommitdiff
path: root/data/adults.sto
blob: 66e200257327e40f8ce8fc3fcae33e956ac55d96 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
control
version=1
nRows=35
nColumns=2
endheader
time	ercspn_r
0.0	6.09756
2.54237	7.31707
4.23729	9.7561
7.62712	9.7561
11.0169	7.31707
12.7119	7.31707
14.4068	6.09756
17.7966	6.09756
19.4915	4.87805
21.1864	4.87805
22.8814	3.65854
29.661	3.65854
31.3559	2.43902
35.5932	2.43902
43.2203	2.43902
47.4576	6.09756
50.8475	10.9756
55.0847	17.0732
58.4746	17.0732
60.1695	14.6341
61.8644	13.4146
65.2542	9.7561
68.6441	8.53659
72.0339	7.31707
73.7288	6.09756
77.1186	4.87805
79.661	4.87805
81.3559	3.65854
85.5932	3.65854
89.8305	3.65854
91.5254	2.43902
94.9153	3.65854
98.3051	4.87805
100	4.87805
74cc7187e6f088942c8e74daa7baff7b44b33c9 (patch) tree1e120c495fbee3aa883b697b2cc6c4d0c8734379 /Documentation/devicetree parent5a6e7ec3bfef2ea518061d8d5d77367952770efb (diff)
ACPICA: Tables: Back port acpi_get_table_with_size() and early_acpi_os_unmap_memory() from Linux kernel
ACPICA commit cac6790954d4d752a083e6122220b8a22febcd07 This patch back ports Linux acpi_get_table_with_size() and early_acpi_os_unmap_memory() into ACPICA upstream to reduce divergences. The 2 APIs are used by Linux as table management APIs for long time, it contains a hidden logic that during the early stage, the mapped tables should be unmapped before the early stage ends. During the early stage, tables are handled by the following sequence: acpi_get_table_with_size(); parse the table early_acpi_os_unmap_memory(); During the late stage, tables are handled by the following sequence: acpi_get_table(); parse the table Linux uses acpi_gbl_permanent_mmap to distinguish the early stage and the late stage. The reasoning of introducing acpi_get_table_with_size() is: ACPICA will remember the early mapped pointer in acpi_get_table() and Linux isn't able to prevent ACPICA from using the wrong early mapped pointer during the late stage as there is no API provided from ACPICA to be an inverse of acpi_get_table() to forget the early mapped pointer. But how ACPICA can work with the early/late stage requirement? Inside of ACPICA, tables are ensured to be remained in "INSTALLED" state during the early stage, and they are carefully not transitioned to "VALIDATED" state until the late stage. So the same logic is in fact implemented inside of ACPICA in a different way. The gap is only that the feature is not provided to the OSPMs in an accessible external API style. It then is possible to fix the gap by providing an inverse of acpi_get_table() from ACPICA, so that the two Linux sequences can be combined: acpi_get_table(); parse the table acpi_put_table(); In order to work easier with the current Linux code, acpi_get_table() and acpi_put_table() is implemented in a usage counting based style: 1. When the usage count of the table is increased from 0 to 1, table is mapped and .Pointer is set with the mapping address (VALIDATED); 2. When the usage count of the table is decreased from 1 to 0, .Pointer is unset and the mapping address is unmapped (INVALIDATED). So that we can deploy the new APIs to Linux with minimal effort by just invoking acpi_get_table() in acpi_get_table_with_size() and invoking acpi_put_table() in early_acpi_os_unmap_memory(). Lv Zheng. Link: https://github.com/acpica/acpica/commit/cac67909 Signed-off-by: Lv Zheng <lv.zheng@intel.com> Signed-off-by: Bob Moore <robert.moore@intel.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'Documentation/devicetree')