| /linux-6.3-rc2/Documentation/firmware-guide/acpi/ |
| A D | chromeos-acpi-device.rst | 4 Chrome OS ACPI Device
7 Hardware functionality specific to Chrome OS is exposed through a Chrome OS ACPI device.
20 - Chrome OS switch positions
23 - Chrome OS hardware ID
26 - Chrome OS firmware version
32 - Chrome OS boot information
35 - Chrome OS GPIO assignments
38 - Chrome OS NVRAM locations
47 - Chrome OS method list
80 HWID (Chrome OS hardware ID)
[all …]
|
| A D | osi.rst | 77 The idea was on a platform tasked with running multiple OS's,
78 the BIOS could use _OS to enable devices that an OS
84 all the quirks of those OS's. Certainly it would make more sense
85 for the BIOS to ask *specific* things of the OS, such
102 and asks the OS: "YES/NO, are you compatible with this interface?"
104 eg. _OSI("3.0 Thermal Model") would return TRUE if the OS knows how
107 and a new OS may be able to return TRUE.
109 For an OS-specific interface, the ACPI spec said that the BIOS and the OS
114 the OS version, rather than an OS supported interface. Indeed, right
144 were never validated under *any* OS.
[all …]
|
| /linux-6.3-rc2/Documentation/ABI/testing/ |
| A D | sysfs-class-mic | 9 Integrated Core (MIC) architecture that runs a Linux OS.
47 "ready" The MIC device is ready to boot the card OS.
52 "booting" The MIC device has initiated booting a card OS.
54 "shutting_down" The card OS is shutting down.
60 operations depending upon the current state of the card OS.
69 "shutdown" Initiates card OS shutdown.
79 entry provides the status on why the card OS was shutdown.
101 boot the card OS. This entry can be written to change the
124 OS boot can be found. The entry can be written to change
150 file of the card OS.
[all …]
|
| A D | sysfs-driver-ppi | 31 executed in the pre-OS environment. It is the only input from
32 the OS to the pre-OS environment. The request should be an
60 operation to be executed in the pre-OS environment by the BIOS
71 operation to be executed in the pre-OS environment by the BIOS
|
| A D | sysfs-firmware-acpi | 14 loading the OS boot loader into memory.
17 launching the currently loaded OS boot loader
20 point when the OS loader calls the
24 just prior to the OS loader gaining control
29 OS write to SLP_TYP upon entry to S3. In
42 handoff to the OS waking vector. In nanoseconds.
48 The BGRT is an ACPI 5.0 feature that allows the OS
112 OS context. GPE 0x12, for example, would vector
|
| /linux-6.3-rc2/tools/perf/Documentation/ |
| A D | guest-files.txt | 4 Guest OS /proc/kallsyms file copy. perf reads it to get guest
5 kernel symbols. Users copy it out from guest OS.
8 Guest OS /proc/modules file copy. perf reads it to get guest
9 kernel module information. Users copy it out from guest OS.
12 Guest OS kernel vmlinux.
|
| A D | guestmount.txt | 2 Guest OS root file system mount directory. Users mount guest OS
5 For example, start 2 guest OS, one's pid is 8888 and the other's is 9999:
|
| /linux-6.3-rc2/fs/hpfs/ |
| A D | Kconfig | 3 tristate "OS/2 HPFS file system support"
7 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
8 is the file system used for organizing files on OS/2 hard disk
10 write files to an OS/2 HPFS partition on your hard drive. OS/2
|
| /linux-6.3-rc2/Documentation/filesystems/ |
| A D | hpfs.rst | 49 When to mark filesystem dirty so that OS/2 checks it.
63 As in OS/2, filenames are case insensitive. However, shell thinks that names
70 OS/2 ignores dots and spaces at the end of file name, so this driver does as
107 incompatible with OS/2. OS/2 PmShell symlinks are not supported because they are
118 file has a pointer to codepage its name is in. However OS/2 was created in
121 Once I booted English OS/2 working in cp 850 and I created a file on my 852
127 Czech OS/2 another file in that directory, that file was inaccessible too. OS/2
145 HPFS386 on OS/2 server is not supported. HPFS386 installed on normal OS/2 client
204 Bugs in OS/2
211 OS/2, OS/2 marks it as 'long'. chkdsk then removes this flag saying "Minor fs
[all …]
|
| A D | adfs.rst | 25 on a RISC OS Filecore filesystem, but will allow the data within files
45 the RISC OS file type will be added. Default 0.
95 RISC OS file type suffix
98 RISC OS file types are stored in bits 19..8 of the file load address.
100 To enable non-RISC OS systems to be used to store files without losing
104 naming convention is now also used by RISC OS emulators such as RPCEmu.
|
| /linux-6.3-rc2/Documentation/networking/device_drivers/ethernet/toshiba/ |
| A D | spider_net.rst | 31 and is waiting to be emptied and processed by the OS. A "not-in-use"
35 During normal operation, on device startup, the OS (specifically, the
39 buffers, and marks them "full". The OS follows up, taking the full
43 and "tail" pointers, managed by the OS, and a hardware current
54 descr. The OS will process this descr, and then mark it "not-in-use",
59 The OS will then note that the current tail is "empty", and halt
64 a "not-in-use" descr. The OS will perform various housekeeping duties
66 dma-mapping it so as to make it visible to the hardware. The OS will
71 pointer, at which point the OS will notice that the head descr is
134 which, from the OS point of view, is empty; the OS will be waiting for
[all …]
|
| /linux-6.3-rc2/Documentation/PCI/ |
| A D | acpi-info.rst | 8 OS might use unless there's another way for the OS to find it [1, 2].
17 described via ACPI. The OS can discover them via the standard PCI
25 namespace [2]. The _CRS is like a generalized PCI BAR: the OS can read
27 a driver for the device [3]. That's important because it means an old OS
28 can work correctly even on a system with new devices unknown to the OS.
37 OS; a static table does not.
39 If the OS is expected to manage a non-discoverable device described via
40 ACPI, that device will have a specific _HID/_CID that tells the OS what
41 driver to bind to it, and the _CRS tells the OS and the driver where the
82 and (2) should not be assigned by the OS to something else.
[all …]
|
| /linux-6.3-rc2/Documentation/admin-guide/ |
| A D | kernel-per-CPU-kthreads.rst | 2 Reducing OS jitter due to per-cpu kthreads
26 - In order to locate kernel-generated OS jitter on CPU N:
43 To reduce its OS jitter, do any of the following:
62 To reduce its OS jitter, do the following:
73 To reduce its OS jitter, do one of the following:
202 housekeeping CPUs, which can tolerate OS jitter.
228 To reduce its OS jitter, do any of the following:
263 commit prevents OS jitter due to vmstat_update() on
265 to entirely get rid of the OS jitter, but you can
286 CBE_CPUFREQ_SPU_GOVERNOR=n to avoid OS jitter from
[all …]
|
| /linux-6.3-rc2/arch/alpha/include/asm/ |
| A D | jensen.h | 321 #define IOPORT(OS, NS) \ argument
325 return jensen_read##OS(xaddr - 0x100000000ul); \
327 return jensen_in##OS((unsigned long)xaddr); \
332 jensen_write##OS(b, xaddr - 0x100000000ul); \
334 jensen_out##OS(b, (unsigned long)xaddr); \
|
| A D | core_t2.h | 586 #define IOPORT(OS, NS) \ argument
590 return t2_read##OS(xaddr); \
592 return t2_in##OS((unsigned long)xaddr - T2_IO); \
597 t2_write##OS(b, xaddr); \
599 t2_out##OS(b, (unsigned long)xaddr - T2_IO); \
|
| /linux-6.3-rc2/arch/um/ |
| A D | Makefile | 21 OS := $(shell uname -s) macro
28 $(ARCH_DIR)/os-$(OS)/
81 include $(srctree)/$(ARCH_DIR)/Makefile-os-$(OS)
158 export HEADER_ARCH SUBARCH USER_CFLAGS CFLAGS_NO_HARDENING OS DEV_NULL_PATH
|
| /linux-6.3-rc2/Documentation/driver-api/ |
| A D | dcdbas.rst | 11 power off after OS shutdown) on certain Dell systems.
55 to perform a power cycle or power off of the system after the OS has finished
57 a driver perform a SMI after the OS has finished shutting down.
73 4) Initiate OS shutdown.
74 (Driver will perform host control SMI when it is notified that the OS
|
| /linux-6.3-rc2/Documentation/ia64/ |
| A D | mca.rst | 10 the OS is in any state. Including when one of the cpus is already
102 slaves. All the OS INIT handlers are entered at approximately the same
103 time. The OS monarch prints the state of all tasks and returns, after
110 of SAL cannot even cope with returning from the OS, they spin inside
111 SAL on resume. The OS INIT code has workarounds for some of these
112 broken SAL symptoms, but some simply cannot be fixed from the OS side.
154 entry to the OS and are restored from there on return to SAL, so user
156 OS has no idea what unwind data is available for the user space stack,
157 MCA/INIT never tries to backtrace user space. Which means that the OS
159 i.e. the OS does not copy pt_regs and switch_stack to the user space
[all …]
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/arm/ |
| A D | secure.txt | 61 be used to pass data to the Secure OS. Only the properties defined
64 - stdout-path : specifies the device to be used by the Secure OS for
67 present, the Secure OS should not perform any console output. If
68 /secure-chosen does not exist, the Secure OS should use the value of
70 Normal world OS).
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/nvmem/ |
| A D | qcom,qfprom.yaml | 40 # If the QFPROM is read-only OS image then only the corrected region
52 # Clock must be provided if QFPROM is writable from the OS image.
58 # Supply reference must be provided if QFPROM is writable from the OS image.
|
| /linux-6.3-rc2/Documentation/gpu/amdgpu/display/ |
| A D | index.rst | 10 1. **Display Core (DC)** contains the OS-agnostic components. Things like
12 2. **Display Manager (DM)** contains the OS-dependent components. Hooks to the
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/remoteproc/ |
| A D | st-rproc.txt | 6 Co-processors can be controlled from the bootloader or the primary OS. If
7 the bootloader starts a co-processor, the primary OS must detect its state
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/chrome/ |
| A D | google,cros-ec-typec.yaml | 7 title: Google Chrome OS EC(Embedded Controller) Type C port driver.
14 Chrome OS devices have an Embedded Controller(EC) which has access to
|
| /linux-6.3-rc2/Documentation/timers/ |
| A D | no_hz.rst | 8 efficiency and reducing OS jitter. Reducing OS jitter is important for
83 1,500 OS instances might find that half of its CPU time was consumed by
205 So you enable all the OS-jitter features described in this document,
207 your workload isn't affected that much by OS jitter, or is it because
209 by providing a simple OS-jitter test suite, which is available on branch
217 If this trace shows that you have removed OS jitter as much as is
219 sensitive to OS jitter.
222 We do not currently have a good way to remove OS jitter from single-CPU
289 of OS jitter, including interrupts and system-utility tasks
293 * Some sources of OS jitter can currently be eliminated only by
[all …]
|
| /linux-6.3-rc2/Documentation/driver-api/mei/ |
| A D | iamt.rst | 18 - OS updates
79 Intel AMT OS Health Watchdog
82 The Intel AMT Watchdog is an OS Health (Hang/Crash) watchdog.
83 Whenever the OS hangs or crashes, Intel AMT will send an event
|