| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-devices-memory | 1 What: /sys/devices/system/memory
5 The /sys/devices/system/memory contains a snapshot of the
12 What: /sys/devices/system/memory/memoryX/removable
16 The file /sys/devices/system/memory/memoryX/removable
24 What: /sys/devices/system/memory/memoryX/phys_device
28 The file /sys/devices/system/memory/memoryX/phys_device
32 What: /sys/devices/system/memory/memoryX/phys_index
36 The file /sys/devices/system/memory/memoryX/phys_index
41 What: /sys/devices/system/memory/memoryX/state
45 The file /sys/devices/system/memory/memoryX/state
[all …]
|
| D | sysfs-devices-system-cpu | 1 What: /sys/devices/system/cpu/
10 /sys/devices/system/cpu/cpu#/
12 What: /sys/devices/system/cpu/kernel_max
13 /sys/devices/system/cpu/offline
14 /sys/devices/system/cpu/online
15 /sys/devices/system/cpu/possible
16 /sys/devices/system/cpu/present
35 the system.
40 What: /sys/devices/system/cpu/probe
41 /sys/devices/system/cpu/release
[all …]
|
| D | sysfs-devices-edac | 1 What: /sys/devices/system/edac/mc/mc*/reset_counters
12 What: /sys/devices/system/edac/mc/mc*/seconds_since_reset
19 What: /sys/devices/system/edac/mc/mc*/mc_name
25 What: /sys/devices/system/edac/mc/mc*/size_mb
31 What: /sys/devices/system/edac/mc/mc*/ue_count
37 increment, since EDAC will panic the system
39 What: /sys/devices/system/edac/mc/mc*/ue_noinfo_count
46 What: /sys/devices/system/edac/mc/mc*/ce_count
54 such information to the system administrator.
56 What: /sys/devices/system/edac/mc/mc*/ce_noinfo_count
[all …]
|
| D | sysfs-devices-power | 14 space to check if the device is enabled to wake up the system
20 used to activate the system from a sleep state. Such devices
31 For the devices that are not capable of generating system wakeup
33 be enabled to wake up the system from sleep states.
61 with the main suspend/resume thread) during system-wide power
87 the system from sleep states, this attribute is not present.
88 If the device is not enabled to wake up the system from sleep
99 system from sleep states, this attribute is not present. If
100 the device is not enabled to wake up the system from sleep
109 the device might have aborted system transition into a sleep
[all …]
|
| D | sysfs-devices-system-xen_cpu | 1 What: /sys/devices/system/xen_cpu/
9 /sys/devices/system/xen_cpu/xen_cpu#/
12 What: /sys/devices/system/xen_cpu/xen_cpu#/online
|
| D | sysfs-firmware-efi | 5 EFI system table.
12 the EFI system table.
19 system table.
|
| D | sysfs-power | 13 The /sys/power/state file controls system sleep states.
30 Writing to this file one of these strings causes the system to
41 the name of the method by which the system will be put to
45 firmware will handle the system suspend.
47 the system will be put to sleep by the platform driver (e.g.
50 the system will be powered off.
52 the system will be rebooted.
77 It will only change to 'firmware' or 'platform' if the system
118 your system is started up and the kernel modules are loaded.
164 system into a sleep state while taking into account the
[all …]
|
| D | sysfs-driver-intel-rapid-start | 11 indicates that the system will wake to enter hibernation when
19 Description: An integer representing the length of time the system will
|
| D | sysfs-firmware-sgi_uv | 16 of the operating system. Each partition will have a unique
22 A partitioned SGI UV system can have one or more coherence
|
| D | sysfs-firmware-gsmi | 14 is limited to handling the system event log and getting
31 the system eventlog. The binary format is
49 whole of the system event log. Values written
|
| /linux-4.4.14/Documentation/ABI/stable/ |
| D | sysfs-devices-node | 1 What: /sys/devices/system/node/possible
7 What: /sys/devices/system/node/online
13 What: /sys/devices/system/node/has_normal_memory
19 What: /sys/devices/system/node/has_cpu
25 What: /sys/devices/system/node/has_high_memory
32 What: /sys/devices/system/node/nodeX
40 What: /sys/devices/system/node/nodeX/cpumap
46 What: /sys/devices/system/node/nodeX/cpulist
52 What: /sys/devices/system/node/nodeX/meminfo
59 What: /sys/devices/system/node/nodeX/numastat
[all …]
|
| D | sysfs-devices-system-xen_memory | 1 What: /sys/devices/system/xen_memory/xen_memory0/max_retry_count
11 What: /sys/devices/system/xen_memory/xen_memory0/max_schedule_delay
19 What: /sys/devices/system/xen_memory/xen_memory0/retry_count
30 What: /sys/devices/system/xen_memory/xen_memory0/schedule_delay
41 What: /sys/devices/system/xen_memory/xen_memory0/target
49 What: /sys/devices/system/xen_memory/xen_memory0/target_kb
56 What: /sys/devices/system/xen_memory/xen_memory0/info/current_kb
64 What: /sys/devices/system/xen_memory/xen_memory0/info/high_kb
71 What: /sys/devices/system/xen_memory/xen_memory0/info/low_kb
|
| D | sysfs-devices-system-cpu | 1 What: /sys/devices/system/cpu/dscr_default
6 /sys/devices/system/cpu/cpuN/dscr on all CPUs.
12 What: /sys/devices/system/cpu/cpu[0-9]+/dscr
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | mvebu-system-controller.txt | 8 - "marvell,orion-system-controller"
9 - "marvell,armada-370-xp-system-controller"
10 - "marvell,armada-375-system-controller"
11 - reg: Should contain system controller registers location and length.
15 system-controller@d0018200 {
16 compatible = "marvell,armada-370-xp-system-controller";
|
| D | versatile-sysreg.txt | 1 ARM Versatile system registers
4 This is a system control registers block, providing multiple low level
|
| D | topology.txt | 9 In an ARM system, the hierarchy of CPUs is defined through three entities that
10 are used to describe the layout of physical CPUs in the system:
22 For instance in a system where CPUs support SMT, "cpu" nodes represent all
23 threads existing in the system and map to the hierarchy level "thread" above.
25 in the system and map to the hierarchy level "core" above.
28 corresponding to the system hierarchy; syntactically they are defined as device
79 be defined within the cpu-map node and every core/thread in the system
105 per cluster. A system can contain several layers of
122 the cluster. If the system does not support SMT, core
148 in the core if the system supports SMT. Thread nodes are
[all …]
|
| D | arm-boards | 26 system controller node pointing to the control registers,
32 Required properties for the system controller:
33 - regs: the location and size of the system controller registers,
36 Required properties for the AP system controller:
39 <module 1>, <module 2> ... for the CP system controller this
125 system controller node pointing to the control registers,
133 Required properties for the system controller:
134 - regs: the location and size of the system controller registers,
|
| D | marvell,berlin.txt | 71 * Marvell Berlin2 system control binding
73 Marvell Berlin SoCs have a system control register set providing several
80 - reg: address and length of the system control register set
91 sysctrl: system-controller@d000 {
|
| /linux-4.4.14/Documentation/ |
| D | adding-syscalls.txt | 4 This document describes what's involved in adding a new system call to the
12 The first thing to consider when adding a new system call is whether one of
13 the alternatives might be suitable instead. Although system calls are the
29 - If you're just exposing runtime system information, a new node in sysfs
37 fcntl(2) is a multiplexing system call that hides a lot of complexity, so
43 fcntl(2), this system call is a complicated multiplexor so is best reserved
51 A new system call forms part of the API of the kernel, and has to be supported
57 together with the corresponding follow-up system calls -- eventfd/eventfd2,
61 For simpler system calls that only take a couple of arguments, the preferred
63 system call. To make sure that userspace programs can safely use flags
[all …]
|
| D | initrd.txt | 9 This RAM disk can then be mounted as the root file system and programs
10 can be run from it. Afterwards, a new root file system can be mounted
14 initrd is mainly designed to allow system startup to occur in two phases,
25 When using initrd, the system typically boots as follows:
38 6) init mounts the "real" root file system
39 7) init places the root file system at the root directory using the
40 pivot_root system call
43 9) the initrd file system is removed
65 the "normal" root file system is mounted. initrd data can be read
67 in this case and doesn't necessarily have to be a file system image.
[all …]
|
| D | cputopology.txt | 5 1) /sys/devices/system/cpu/cpuX/topology/physical_package_id:
11 2) /sys/devices/system/cpu/cpuX/topology/core_id:
17 3) /sys/devices/system/cpu/cpuX/topology/book_id:
23 4) /sys/devices/system/cpu/cpuX/topology/thread_siblings:
28 5) /sys/devices/system/cpu/cpuX/topology/thread_siblings_list:
33 6) /sys/devices/system/cpu/cpuX/topology/core_siblings:
38 7) /sys/devices/system/cpu/cpuX/topology/core_siblings_list:
43 8) /sys/devices/system/cpu/cpuX/topology/book_siblings:
48 9) /sys/devices/system/cpu/cpuX/topology/book_siblings_list:
83 /sys/devices/system/cpu and includes these files. The internal
[all …]
|
| D | cpu-load.txt | 6 the average time system spent in a particular state, for example:
11 avg-cpu: %user %nice %system %iowait %steal %idle
16 Here the system thinks that over the default sampling period the
17 system spent 10.01% of the time doing work in user space, 2.92% in the
27 kind/state. The problem with this is that the system could have
35 If we imagine the system with one task that periodically burns cycles
45 In the above situation the system will be 0% loaded according to the
47 system is executing the idle handler), but in reality the load is
|
| D | dcdbas.txt | 4 systems management software such as Dell OpenManage to perform system
5 management interrupts and host control actions (system power cycle or
22 management information via a system management interrupt (SMI). The SMI data
27 software to perform these system management interrupts:
38 2) Write system management command to smi_data.
41 4) Read system management command response from smi_data.
48 to perform a power cycle or power off of the system after the OS has finished
54 action after the system has finished shutting down:
|
| D | edac.txt | 12 that occur within the computer system running under linux.
23 CE events only, the system can and will continue to operate as no data
28 and system panics.
74 Controller (MC) driver modules. On a given system, the CORE is loaded
79 Thus, to "report" on what version a system is running, one must report
104 lives in the /sys/devices/system/edac directory.
108 mc memory controller(s) system
109 pci PCI control and status system
164 /sys/devices/system/edac/mc each memory controller will be represented
227 will panic the system.
[all …]
|
| D | unshare.txt | 2 unshare system call:
4 This document describes the new system call, unshare. The document
27 Most legacy operating system kernels support an abstraction of threads
37 threads. On Linux, at the time of thread creation using the clone system
41 unshare system call adds a primitive to the Linux thread model that
74 appropriate by system administrators.
93 changes to copy_* functions utilized by clone/fork system call.
102 unshare reverses sharing that was done using clone(2) system call,
142 If CLONE_FS is set, file system information of the caller
143 is disassociated from the shared file system information.
[all …]
|
| D | memory-hotplug.txt | 72 "probe" operation by system administration is used instead.
82 Logical Memory Hotplug phase is triggered by write of sysfs file by system
104 /sys/devices/system/memory/block_size_bytes
136 is described under /sys/devices/system/memory as
138 /sys/devices/system/memory/memoryXXX
148 0x100000000 is /sys/device/system/memory/memory4
154 /sys/devices/system/memory/memoryXXX/phys_index
155 /sys/devices/system/memory/memoryXXX/phys_device
156 /sys/devices/system/memory/memoryXXX/state
157 /sys/devices/system/memory/memoryXXX/removable
[all …]
|
| D | rtc.txt | 7 works even with system power off. Such clocks will normally not track
13 system call reports, but RTCs also very commonly represent time using
113 than expecting a single battery-backed MC146818 clone on every system.
122 * /proc/driver/rtc ... the system clock RTC may expose itself
123 using a procfs interface. If there is no RTC for the system clock,
128 integrated into embeddable system-on-chip (SOC) processors to discrete chips
133 The new framework also removes the "one RTC per system" restriction. For
135 a high functionality RTC is integrated into the SOC. That system might read
136 the system clock from the discrete RTC, but use the integrated one for all
144 are in the RTC's timezone, rather than in system time.
[all …]
|
| D | SM501.txt | 20 chips via the platform device and driver system.
26 The core re-uses the platform device system as the platform device
27 system provides enough features to support the drivers without the
60 so that there can be support for more than one system carrying
70 lock and hang the whole system. The driver will refuse to
|
| D | highuid.txt | 16 Further investigation is needed to see if the quota system can cope
20 - Decide whether or not to keep backwards compatibility with the system
28 uses the 32-bit UID system calls properly otherwise.
34 (need to support whatever new 32-bit UID system calls are added to
|
| D | SAK.txt | 4 An operating system's Secure Attention Key is a security tool which is
8 this key sequence before they log in to the system.
20 once defined, SAK will kill a running X server. If the system is in
86 delete these lines, but this may cause system management
|
| D | lockup-watchdogs.txt | 11 stack trace is displayed upon detection and, by default, the system
22 upon detection and the system will stay locked up unless the default
30 to cause the system to reboot automatically after a specified amount
43 same name) seconds to check for hardlockups. If any CPU in the system
53 will dump useful debug information to the system log, after which it
|
| D | intel_txt.txt | 62 starting at system reset and requires measurement of all code
63 executed between system reset through the completion of the kernel
82 system configuration and initial state than would be otherwise
95 - If tboot determines that the system does not support Intel TXT
144 o In order to put a system into any of the sleep states after a TXT
146 attempt to crash the system to gain control on reboot and steal
161 In order to preserve system integrity across S3, the kernel
203 system and can also be found on the Trusted Boot site. It is an
205 DRTM process to verify and configure the system. It is signed
206 because it operates at a higher privilege level in the system than
[all …]
|
| /linux-4.4.14/fs/minix/ |
| D | Kconfig | 2 tristate "Minix file system support"
5 Minix is a simple operating system used in many classes about OS's.
6 The minix file system (method to organize files on a hard disk
7 partition or a floppy disk) was the original file system for Linux,
8 but has been superseded by the second extended file system ext2fs.
9 You don't want to use the minix file system on your hard disk
14 To compile this file system support as a module, choose M here: the
15 module will be called minix. Note that the file system of your root
|
| /linux-4.4.14/Documentation/prctl/ |
| D | seccomp_filter.txt | 7 A large number of system calls are exposed to every userland process
9 As system calls change and mature, bugs are found and eradicated. A
11 of available system calls. The resulting set reduces the total kernel
16 incoming system calls. The filter is expressed as a Berkeley Packet
18 operated on is related to the system call being made: system call
19 number and the system call arguments. This allows for expressive
20 filtering of system calls using a filter program language with a long
24 to time-of-check-time-of-use (TOCTOU) attacks that are common in system
26 pointers which constrains all filters to solely evaluating the system
36 other system hardening techniques and, potentially, an LSM of your
[all …]
|
| /linux-4.4.14/kernel/trace/ |
| D | trace_events.c | 45 static inline int system_refcount(struct event_subsystem *system) in system_refcount() argument
47 return system->ref_count; in system_refcount()
50 static int system_refcount_inc(struct event_subsystem *system) in system_refcount_inc() argument
52 return system->ref_count++; in system_refcount_inc()
55 static int system_refcount_dec(struct event_subsystem *system) in system_refcount_dec() argument
57 return --system->ref_count; in system_refcount_dec()
616 static void __put_system(struct event_subsystem *system) in __put_system() argument
618 struct event_filter *filter = system->filter; in __put_system()
620 WARN_ON_ONCE(system_refcount(system) == 0); in __put_system()
621 if (system_refcount_dec(system)) in __put_system()
[all …]
|
| /linux-4.4.14/fs/freevxfs/ |
| D | Kconfig | 2 tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)"
5 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
6 file system format. VERITAS VxFS(TM) is the standard file system
11 NOTE: the file system type as used by mount(1), mount(2) and
12 fstab(5) is 'vxfs' as it describes the file system format, not
|
| /linux-4.4.14/Documentation/devicetree/bindings/power/ |
| D | power-controller.txt | 1 * Generic system power control capability
4 sometimes able to control the system power. The device driver associated with these
6 it can be used to switch off the system. The corresponding device must have the
7 standard property "system-power-controller" in its device node. This property
8 marks the device as able to control the system power. In order to test if this
17 system-power-controller;
|
| /linux-4.4.14/fs/nilfs2/ |
| D | Kconfig | 2 tristate "NILFS2 file system support"
5 NILFS2 is a log-structured file system (LFS) supporting continuous
7 file system, users can even restore files mistakenly overwritten or
8 destroyed just a few seconds ago. Since this file system can keep
10 system crashes.
17 snapshot is mountable as a read-only file system concurrently with
23 To compile this file system support as a module, choose M here: the
|
| /linux-4.4.14/drivers/media/rc/ |
| D | ir-rc5-decoder.c | 129 u8 xdata, command, system; in ir_rc5_decode() local
136 system = (data->bits & 0x1F000) >> 12; in ir_rc5_decode()
139 scancode = system << 16 | command << 8 | xdata; in ir_rc5_decode()
144 u8 command, system; in ir_rc5_decode() local
150 system = (data->bits & 0x007C0) >> 6; in ir_rc5_decode()
153 scancode = system << 8 | command; in ir_rc5_decode()
158 u8 command, system; in ir_rc5_decode() local
164 system = (data->bits & 0x02FC0) >> 6; in ir_rc5_decode()
166 scancode = system << 6 | command; in ir_rc5_decode()
|
| /linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
| D | berlin,pinctrl.txt | 3 Pin control registers are part of both chip controller and system
5 either the chip controller or system controller node. The pins
19 "marvell,berlin2-system-pinctrl",
21 "marvell,berlin2cd-system-pinctrl",
23 "marvell,berlin2q-system-pinctrl",
26 "marvell,berlin4ct-system-pinctrl"
35 compatible = "marvell,berlin2q-system-pinctrl";
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/uniphier/ |
| D | cache-uniphier.txt | 3 UniPhier SoCs are integrated with a full-custom outer cache controller system.
8 - compatible: should be "socionext,uniphier-system-cache"
21 cache should be also compatible with "socionext,uniphier-system-cache".
26 Example 1 (system with L2):
28 compatible = "socionext,uniphier-system-cache";
38 Example 2 (system with L2 and L3):
40 compatible = "socionext,uniphier-system-cache";
52 compatible = "socionext,uniphier-system-cache";
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/hisilicon/ |
| D | hisilicon.txt | 27 Hisilicon system controller
40 - reboot-offset : offset in sysctrl for system reboot
45 sysctrl: system-controller@fc802000 {
54 Hisilicon Hi6220 system controller
62 Hisilicon designs this controller as one of the system controllers,
63 its main functions are the same as Hisilicon system controller, but
83 Hisilicon designs this system controller to control the power always
103 Hisilicon designs this system controller to control the multimedia
123 Hisilicon designs this system controller to control the power management
153 Hisilicon HiP01 system controller
[all …]
|
| /linux-4.4.14/Documentation/power/ |
| D | suspend-and-interrupts.txt | 10 Device interrupt request lines (IRQs) are generally disabled during system
27 Device IRQs are re-enabled during system resume, right before the "early" phase
35 There are interrupts that can legitimately trigger during the entire system
45 interrupt will wake the system from a suspended state -- for such cases it is
59 System wakeup interrupts generally need to be configured to wake up the system
65 during system sleep so as to trigger a system wakeup when needed. For example,
67 handling system wakeup events. Then, if a given interrupt line is supposed to
68 wake up the system from sleep sates, the corresponding input of that interrupt
75 handling the given IRQ as a system wakeup interrupt line and disable_irq_wake()
81 re-enabled by resume_device_irqs() during the subsequent system resume. Also
[all …]
|
| D | states.txt | 5 The kernel supports up to four system sleep states generically, although three
18 because there is at least one non-hibernation sleep state in every system. If
19 the given system supports two non-hibernation sleep states, "standby" is present
20 in /sys/power/state in addition to "mem". If the system supports three
31 This state is a generic, pure software, light-weight, system sleep state.
47 providing a relatively low-latency transition back to a working system. No
48 operating state is lost (the CPU retains power), so the system easily starts up
53 and all low-level system functions are suspended during transitions into this
64 system is put into a low-power state, except for memory, which should be placed
79 system from it. This may be the case on other platforms too.
[all …]
|
| D | userland-swsusp.txt | 10 utilities that will read/write the system memory snapshot from/to the
39 SNAPSHOT_CREATE_IMAGE - create a snapshot of the system memory; the
42 creating the snapshot (1) or after restoring the system memory state
43 from it (0) (after resume the system finds itself finishing the
48 SNAPSHOT_ATOMIC_RESTORE - restore the system memory state from the
50 the system memory snapshot back to the kernel using the write()
86 SNAPSHOT_POWER_OFF - make the kernel transition the system to the hibernation
92 to use the SNAPSHOT_UNFREEZE call after the system wakes up. This call
94 suspend image is first created, as though the system had been suspended
95 to disk, and then the system is suspended to RAM (this makes it possible
[all …]
|
| D | devices.txt | 13 This writeup gives an overview of how drivers interact with system-wide
25 Drivers can enter low-power states as part of entering system-wide
35 Some drivers can manage hardware wakeup events, which make the system
40 system enter low-power states more often.
43 Devices may also be put into low-power states while the system is
50 states at run time may require special handling during system-wide power
55 the PM core are involved in runtime power management. As in the system
61 very system-specific, and often device-specific. Also, that if enough devices
63 to entering some system-wide low-power state (system sleep) ... and that
64 synergies exist, so that several drivers using runtime PM might put the system
[all …]
|
| D | apm-acpi.txt | 3 If you have a relatively recent x86 mobile, desktop, or server system,
7 operating system, allowing for more intelligent power management than
10 The best way to determine which, if either, your system supports is to
27 and be sure that they are started sometime in the system boot process.
29 system the associated daemon will exit gracefully.
|
| D | drivers-testing.txt | 4 1. Preparing the test system
6 Unfortunately, to effectively test the support for the system-wide suspend and
8 functional system with this driver loaded. Moreover, that should be done
14 Of course, for this purpose the test system has to be known to suspend and
16 resolve all suspend/resume-related problems in the test system before you start
22 Once you have resolved the suspend/resume-related problems with your test system
|
| D | notifiers.txt | 5 before hibernation/suspend or after restore/resume, but they require the system
18 PM_HIBERNATION_PREPARE The system is going to hibernate, tasks will be frozen
23 PM_POST_HIBERNATION The system memory state has been restored from a
28 PM_RESTORE_PREPARE The system is going to restore a hibernation image.
36 PM_SUSPEND_PREPARE The system is preparing for suspend.
38 PM_POST_SUSPEND The system has just resumed or an error occurred during
|
| D | pci.txt | 52 delivering the PME from the device to the CPU and the operating system kernel.
138 system-specific. However, if the system in question is compliant with the
151 on the system design in a system-specific fashion.
182 system-wide transition into a sleep state or back into the working state. ACPI
183 defines four system sleep states, S1, S2, S3, and S4, and denotes the system
184 working state as S0. In general, the target system sleep (or working) state
188 If the device is required to wake up the system from the target sleep state, the
190 target state of the system. The kernel is then supposed to use the device's
200 appropriate. If they are sent while the system is in the working state
203 events that triggered them. In turn, if they are sent while the system is
[all …]
|
| D | basic-pm-debugging.txt | 11 and the system should create a hibernation image, reboot, resume and get back to
16 resuming the system.] Moreover, hibernating in the "reboot" and "shutdown"
34 button to make the system resume).
41 To find out why hibernation fails on your system, you can use a special testing
63 platform/system devices
108 or resume its device (in the latter case the system may hang or become unstable
112 (that would probably involve rebooting the system, so always note what drivers
128 platform (eg. ACPI) firmware on your system. In that case the "platform" mode
135 off and on using the /sys/devices/system/cpu/cpu*/online sysfs attributes and
138 If the "core" test fails, which means that suspending of the system/platform
[all …]
|
| D | charger-manager.txt | 12 batteries with their own chargers acting independently in a system,
13 the system may need multiple instances of Charger Manager.
21 A system may have multiple chargers (or power sources) and some of
29 While the battery is being charged and the system is in suspend-to-RAM,
31 battery temperature. We can accomplish this by waking up the system
74 : The name of rtc (e.g., "rtc0") used to wakeup the system from
76 should be able to wake up the system from suspend. Charger Manager
98 callback of the system's platform_suspend_ops can call cm_suspend_again
105 if the system was woken up by Charger Manager and the polling
196 and others critical to chargers, the system should be configured to wake up.
[all …]
|
| D | swsusp-dmcrypt.txt | 14 Now your system is properly set up, your disk is encrypted except for
16 system for crypto setup and/or rescue purposes. You may even have
30 within your running system. The easiest way to achieve this is
62 /dev/hda1 contains an unencrypted mini system that sets up all
66 continues boot with your mini system on /dev/hda1 if resume
132 mini system on /dev/hda1 to set the whole crypto up (it is up to
136 file system and continue booting from there. I prefer to unmount
|
| D | interface.txt | 9 /sys/power/state controls system power state. Reading from this file
14 Writing to this file one of those strings causes the system to
22 few options for putting the system to sleep - using the platform driver
23 (e.g. ACPI or other suspend_ops), powering off the system or rebooting the
24 system (for testing).
|
| D | swsusp.txt | 16 * your hardware while system is suspended... well, it was not good idea;
32 . If you feel ACPI works pretty well on your system, you might try
90 In the meantime while the system is suspended you should not add/remove any
104 echo 5 > /proc/acpi/sleep # for shutdown unfriendly the system
165 kernel threads are controlled during hibernation or system-wide suspend (on some
206 complicated code. (And I have not yet introduce details like system
219 Q: After resuming, system is paging heavily, leading to very bad interactivity.
231 during system suspend?
238 running system, user asks for suspend-to-disk
259 running system, user asks for suspend-to-disk
[all …]
|
| /linux-4.4.14/tools/testing/selftests/cpu-hotplug/ |
| D | cpu-on-off-test.sh | 23 if ! ls $SYSFS/devices/system/cpu/cpu* > /dev/null 2>&1; then
29 online_cpus=`cat $SYSFS/devices/system/cpu/online`
33 offline_cpus=`cat $SYSFS/devices/system/cpu/offline`
49 for cpu in $SYSFS/devices/system/cpu/cpu*; do
68 grep -q 1 $SYSFS/devices/system/cpu/cpu$1/online
73 grep -q 0 $SYSFS/devices/system/cpu/cpu$1/online
78 echo 1 > $SYSFS/devices/system/cpu/cpu$1/online
83 echo 0 > $SYSFS/devices/system/cpu/cpu$1/online
|
| /linux-4.4.14/fs/efs/ |
| D | Kconfig | 2 tristate "EFS file system support (read only)"
5 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
6 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
7 uses the XFS file system for hard disk partitions however).
13 To compile the EFS file system support as a module, choose M here: the
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | max16065 | 33 [From datasheets] The MAX16065/MAX16066 flash-configurable system managers
34 monitor and sequence multiple system voltages. The MAX16065/MAX16066 can also
36 current-sense amplifier. The MAX16065 manages up to twelve system voltages
39 The MAX16067 flash-configurable system manager monitors and sequences multiple
40 system voltages. The MAX16067 manages up to six system voltages simultaneously.
42 The MAX16068 flash-configurable system manager monitors and manages up to six
43 system voltages simultaneously.
45 The MAX16070/MAX16071 flash-configurable system monitors supervise multiple
46 system voltages. The MAX16070/MAX16071 can also accurately monitor (+/-2.5%)
48 MAX16070 monitors up to twelve system voltages simultaneously, and the MAX16071
|
| D | wm8350 | 18 monitor a range of system operating parameters, including the voltages
19 of the major supplies within the system. Currently the driver provides
26 is referenced to the system VRTC.
|
| D | da9055 | 18 Channel 0: VDDOUT - measurement of the system voltage
24 By using sysfs attributes we can measure the system voltage VDDOUT,
33 The system voltage is calculated as:
|
| /linux-4.4.14/include/trace/ |
| D | define_trace.h | 72 # define __TRACE_INCLUDE(system) <trace/events/system.h> argument
75 # define __TRACE_INCLUDE(system) __stringify(TRACE_INCLUDE_PATH/system.h) argument
78 # define TRACE_INCLUDE(system) __TRACE_INCLUDE(system) argument
|
| /linux-4.4.14/arch/s390/kernel/ |
| D | vtime.c | 98 u64 timer, clock, user, system, steal; in do_account_vtime() local
124 system = S390_lowcore.system_timer - ti->system_timer; in do_account_vtime()
125 S390_lowcore.steal_timer -= system; in do_account_vtime()
129 system_scaled = system; in do_account_vtime()
139 account_system_time(tsk, hardirq_offset, system, system_scaled); in do_account_vtime()
147 return virt_timer_forward(user + system); in do_account_vtime()
181 u64 timer, system, system_scaled; in vtime_account_irq_enter() local
192 system = S390_lowcore.system_timer - ti->system_timer; in vtime_account_irq_enter()
193 S390_lowcore.steal_timer -= system; in vtime_account_irq_enter()
195 system_scaled = system; in vtime_account_irq_enter()
[all …]
|
| /linux-4.4.14/drivers/eisa/ |
| D | Kconfig | 9 Activate this option if your system contains a Vesa Local
20 Activate this option if your system contains a PCI to EISA
21 bridge. If your system have both PCI and EISA slots, you
34 Activate this option if your system only have EISA bus
36 a system.
48 image by about 40KB, but it gets freed after the system
51 embedded system where kernel image size really matters, you
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | cpuacct.txt | 17 the system. /sys/fs/cgroup/tasks lists the tasks in this cgroup.
20 in the system.
34 CPU time obtained by the cgroup into user and system times. Currently
38 system: Time spent by tasks of the cgroup in kernel mode.
40 user and system are in USER_HZ unit.
43 system times. This has two side effects:
45 - It is theoretically possible to see wrong values for user and system times.
48 - It is possible to see slightly outdated values for user and system times
|
| D | cgroups.txt | 57 every task in the system is in exactly one of the cgroups in the
58 hierarchy, and a set of subsystems; each subsystem has system-specific
63 cgroups. Each hierarchy is a partition of all tasks in the system.
66 instance of the cgroup virtual file system, specify and query to
69 associated with that instance of the cgroup file system.
91 minimal impact on the system fast paths, and provides hooks for
109 university server with various users - students, professors, system
119 In addition (system tasks) are attached to topcpuset (so
122 Memory : Professors (50%), Students (30%), system (20%)
124 Disk : Professors (50%), Students (30%), system (20%)
[all …]
|
| D | cpusets.txt | 46 hierarchy visible in a virtual file system. These are the essential
53 Requests by a task, using the sched_setaffinity(2) system call to
55 set_mempolicy(2) system calls to include Memory Nodes in its memory
63 virtual file system, manage the attributes and permissions of these
78 efficiency just by letting the operating system automatically share
85 the system.
121 - Each task in the system is attached to a cpuset, via a pointer
141 - in init/main.c, to initialize the root cpuset at system boot.
147 - in the mbind and set_mempolicy system calls, to mask the requested
154 new system calls are added for cpusets - all support for querying and
[all …]
|
| /linux-4.4.14/drivers/media/dvb-frontends/ |
| D | ascot2e.c | 278 enum ascot2e_tv_system_t system = ASCOT2E_DTV_UNKNOWN; in ascot2e_get_tv_system() local
284 system = ASCOT2E_DTV_DVBT_5; in ascot2e_get_tv_system()
286 system = ASCOT2E_DTV_DVBT_6; in ascot2e_get_tv_system()
288 system = ASCOT2E_DTV_DVBT_7; in ascot2e_get_tv_system()
290 system = ASCOT2E_DTV_DVBT_8; in ascot2e_get_tv_system()
292 system = ASCOT2E_DTV_DVBT_8; in ascot2e_get_tv_system()
297 system = ASCOT2E_DTV_DVBT2_5; in ascot2e_get_tv_system()
299 system = ASCOT2E_DTV_DVBT2_6; in ascot2e_get_tv_system()
301 system = ASCOT2E_DTV_DVBT2_7; in ascot2e_get_tv_system()
303 system = ASCOT2E_DTV_DVBT2_8; in ascot2e_get_tv_system()
[all …]
|
| D | cxd2841er.c | 53 u8 system; member
337 u8 system);
340 u8 system, u32 symbol_rate) in cxd2841er_sleep_s_to_active_s() argument
353 if (system == SYS_DVBS) { in cxd2841er_sleep_s_to_active_s()
355 } else if (system == SYS_DVBS2) { in cxd2841er_sleep_s_to_active_s()
359 __func__, system); in cxd2841er_sleep_s_to_active_s()
448 switch (priv->system) { in cxd2841er_retune_active()
461 __func__, priv->system); in cxd2841er_retune_active()
763 u8 system) in cxd2841er_set_ts_clock_mode() argument
799 if (system == SYS_DVBT) { in cxd2841er_set_ts_clock_mode()
[all …]
|
| /linux-4.4.14/Documentation/arm/sunxi/ |
| D | clocks.txt | 1 Frequently asked questions about the sunxi clock system
5 about the sunxi clock system, as well as accompanying ASCII art when adequate.
8 system?
11 carelessly the system would stop functioning, but with the right
12 steps, one can gate it and keep the system running. Consider this
15 While the system is operational, you would see something like
|
| /linux-4.4.14/tools/testing/selftests/timers/ |
| D | change_skew.c | 61 ret = system("./raw_skew"); in change_skew_test()
62 ret |= system("./inconsistency-check"); in change_skew_test()
63 ret |= system("./nanosleep"); in change_skew_test()
77 ret = system("killall -9 ntpd"); in main()
|
| D | set-2038.c | 77 ret = system("date"); in do_tests()
78 ret = system("./inconsistency-check -c 0 -t 20"); in do_tests()
79 ret |= system("./nanosleep"); in do_tests()
80 ret |= system("./nsleep-lat"); in do_tests()
|
| /linux-4.4.14/fs/ufs/ |
| D | Kconfig | 2 tristate "UFS file system support (read only)"
6 OpenBSD and NeXTstep) use a file system called UFS. Some System V
8 this file system as well. Saying Y here will allow you to read from
10 experimental "UFS file system write support", below. Please read the
25 To compile the UFS file system support as a module, choose M here: the
31 bool "UFS file system write support (DANGEROUS)"
43 written to the system log.
|
| /linux-4.4.14/kernel/ |
| D | Kconfig.preempt | 15 scientific/computation system, or if you want to maximize the
30 is in kernel mode executing a system call. This allows
31 applications to run more 'smoothly' even when the system is
34 Select this if you are building a kernel for a desktop system.
45 even if it is in kernel mode executing a system call and would
48 system is under load, at the cost of slightly lower throughput
52 embedded system with latency requirements in the milliseconds
|
| /linux-4.4.14/Documentation/power/regulator/ |
| D | design.txt | 11 for the system, potentially including lasting hardware damage.
13 of the system - software-equivalent variants of the same chip may
19 particular system.
24 - The overwhelming majority of devices in a system will have no
28 - Many of the power supplies in the system will be shared between many
|
| /linux-4.4.14/Documentation/x86/ |
| D | earlyprintk.txt | 12 a.) Host/target system needs to have USB debug port capability.
35 ( If your system does not list a debug port capability then you probably
45 c.) You need a second client/console system with a high speed USB 2.0
49 debug port on the "host/target" system. You cannot use a USB hub in
50 between the physical debug port and the "host/target" system.
58 each physical port on the system and rebooting. Or you can try
61 "host/target" system.
69 device require the "client/console" system to be plugged into the
77 a.) On the host/target system:
99 b.) On the client/console system:
[all …]
|
| /linux-4.4.14/arch/microblaze/boot/dts/ |
| D | Makefile | 6 $(obj)/linked_dtb.o: $(obj)/system.dtb
9 ifneq ($(DTB),system)
10 $(obj)/system.dtb: $(obj)/$(DTB).dtb
|
| /linux-4.4.14/fs/romfs/ |
| D | Kconfig | 2 tristate "ROM file system support"
5 This is a very small read-only file system mainly intended for
10 To compile this file system support as a module, choose M here: the
11 module will be called romfs. Note that the file system of your
29 bool "Block device-backed ROM file system support"
39 bool "MTD-backed ROM file system support"
|
| /linux-4.4.14/drivers/staging/lustre/lustre/ |
| D | Kconfig | 2 tristate "Lustre file system client support"
15 This option enables Lustre file system client support. Choose Y
16 here if you want to access a Lustre file system cluster. To compile
17 this file system support as a module, choose M here: the module will
25 Lustre file system is the most popular cluster file system in high
|
| /linux-4.4.14/Documentation/devicetree/bindings/ |
| D | marvell.txt | 4 The Marvell mv64[345]60 series of system controller chips contain
6 system. In this section, we define device tree nodes to describe
7 the system controller chip itself and each of the peripherals
11 1) The /system-controller node
13 This node is used to represent the system-controller and must be
14 present when the system uses a system controller chip. The top-level
15 system-controller node contains information that is global to all
16 devices within the system controller chip. The node name begins
17 with "system-controller" followed by the unit address, which is
18 the base address of the memory-mapped register set for the system
[all …]
|
| /linux-4.4.14/tools/power/cpupower/bench/ |
| D | cpufreq-bench_script.sh | 43 echo $up_threshold >/sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold
44 echo $sampling_rate >/sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate
45 up_threshold_set=$(cat /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold)
46 sampling_rate_set=$(cat /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate)
|
| /linux-4.4.14/fs/udf/ |
| D | Kconfig | 2 tristate "UDF file system support"
5 This is a file system used on some CD-ROMs and DVDs. Since the
6 file system is supported by multiple operating systems and is more
12 To compile this file system support as a module, choose M here: the
|
| /linux-4.4.14/fs/hpfs/ |
| D | Kconfig | 2 tristate "OS/2 HPFS file system support"
5 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
6 is the file system used for organizing files on OS/2 hard disk
13 To compile this file system support as a module, choose M here: the
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | gfs2.txt | 6 GFS is a cluster file system. It allows a cluster of computers to
9 file system, but also uses a lock module to allow the computers coordinate
10 their I/O so file system consistency is maintained. One of the nifty
11 features of GFS is perfect consistency -- changes made to the file system
17 lock_nolock -- allows gfs to be used as a local file system
25 To use gfs as a local file system, no external clustering systems are
|
| D | exofs.txt | 5 exofs is a file system that uses an OSD and exports the API of a normal Linux
6 file system. Users access exofs like any other local file system, and exofs
21 To use this file system, you need to have an object store to run it on. You
58 As an example, this will create the file system on:
64 performed and a clean file system will be created in the specified pid,
76 6. Mount the file system.
84 do-exofs stop - an example of how to unmount the file system.
97 -t exofs: specifies the exofs file system
102 mount_exofs_directory: The directory to mount the file system on
123 * The file system control block (AKA on-disk superblock) resides in an object
[all …]
|
| D | qnx6.txt | 4 The qnx6fs is used by newer QNX operating system versions. (e.g. Neutrino)
10 mmi_fs Mount filesystem as used for example by Audi MMI 3G system
148 Bitmap system area
152 First the system area, that is split into two halves.
155 The requirement for a static, fixed preallocated system area comes from how
157 Each superblock got it's own half of the system area. So superblock #1
159 blocks represented by the upper half bitmap system area bits.
162 tree structures are treated as system blocks.
165 (system area of the inactive - resp. lower serial numbered superblock) while
167 other half of the system area.
[all …]
|
| D | inotify.txt | 2 a powerful yet simple file change notification system
18 for use on a desktop system with removable media as the media cannot be
59 When you talk about designing a file change notification system that
68 Q: Why the system call approach?
75 device file or a family of new system calls. We decided to implement a
76 family of system calls because that is the preferred approach for new kernel
78 and ioctl(2) or a couple of new system calls. System calls beat ioctls.
|
| D | ceph.txt | 4 Ceph is a distributed network file system designed to provide good
32 system extremely efficient and scalable.
46 The system offers automatic data rebalancing/migration when scaling
50 When the file system approaches full, new nodes can be easily added
55 system. Snapshot creation and deletion are as simple as 'mkdir
60 system will reveal the total number of nested regular files and
63 no 'du' or similar recursive scan of the file system is required.
105 of a non-responsive Ceph file system. The default is 30
147 and the source for the full system is at
|
| D | dlmfs.txt | 4 system.
49 that an OCFS2 file system be in place so that it can automatically
62 Users may access dlmfs via standard file system calls, or they can use
64 system calls and presents a more traditional locking api.
89 domain directory. Locking against them is done via the open(2) system
120 Exclusive modes via the read(2) system call. It can be written via
|
| D | romfs.txt | 7 file system which doesn't take up useful memory from the router
19 To create such a file system, you'll need a user program named
86 The following bytes are now part of the file system; each file header
141 To overcome this limitation, the whole size of the file system must be
144 If you have any problems or suggestions concerning this file system,
147 this file system is the small code. On the other hand, don't be
161 Un*x like system, but romfs does not provide the full possibilities.
164 - The file system is read only, so it can be very small, but in case
165 one would want to write _anything_ to a file system, he still needs
166 a writable file system, thus negating the size advantages. Possible
|
| /linux-4.4.14/tools/testing/selftests/memory-hotplug/ |
| D | mem-on-off-test.sh | 21 if ! ls $SYSFS/devices/system/memory/memory* > /dev/null 2>&1; then
34 for memory in $SYSFS/devices/system/memory/memory*; do
54 grep -q online $SYSFS/devices/system/memory/memory$1/state
59 grep -q offline $SYSFS/devices/system/memory/memory$1/state
64 echo online > $SYSFS/devices/system/memory/memory$1/state
69 echo offline > $SYSFS/devices/system/memory/memory$1/state
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | pnfs-block-server.txt | 10 system needs to support the pNFS block layouts (currently just XFS), and the
11 file system must sit on shared storage (typically iSCSI) that is accessible
12 to the clients in addition to the MDS. As of now the file system needs to
16 On the server, pNFS block volume support is automatically if the file system
19 file system is mounted using the NFSv4.1 protocol version (mount -o vers=4.1).
24 prefix for the file system to be fenced. Below is an example file that shows
|
| D | nfs.txt | 15 special features of the NFS client that can be configured by system
29 the local system's node name. System administrators, however, often do not
31 over the lifetime of a client system. Node names can have other
36 used instead of a system's node name when an NFS client identifies itself to
37 a server. Thus, if the system's node name is not unique, or it changes, its
43 nfs4_unique_id string should be chosen when a client system is installed,
44 just as a system's root file system gets a fresh UUID in its label at
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | imx27-phytec-phycore-rdk.dts | 228 label = "system:red1:user";
233 label = "system:green1:user";
238 label = "system:blue1:user";
243 label = "system:red2:user";
248 label = "system:green2:user";
253 label = "system:blue2:user";
258 label = "system:red3:nand";
264 label = "system:green3:live";
270 label = "system:blue3:cpu";
|
| /linux-4.4.14/fs/proc/ |
| D | Kconfig | 2 bool "/proc file system support" if EXPERT
5 This is a virtual file system providing information about the status
6 of the system. "Virtual" means that it doesn't take up any space on
17 information about your system gathered from the /proc file system.
19 Before you can use the /proc file system, it has to be mounted,
24 The /proc file system is explained in the file
54 a recompile of the kernel or reboot of the system. The primary
62 building a kernel for install/rescue disks or your system is very
|
| D | stat.c | 84 u64 user, nice, system, idle, iowait, irq, softirq, steal; in show_stat() local
91 user = nice = system = idle = iowait = in show_stat()
100 system += kcpustat_cpu(i).cpustat[CPUTIME_SYSTEM]; in show_stat()
123 seq_put_decimal_ull(p, ' ', cputime64_to_clock_t(system)); in show_stat()
137 system = kcpustat_cpu(i).cpustat[CPUTIME_SYSTEM]; in show_stat()
148 seq_put_decimal_ull(p, ' ', cputime64_to_clock_t(system)); in show_stat()
|
| /linux-4.4.14/drivers/ras/ |
| D | Kconfig | 10 Reliability can be defined as the probability that the system will
15 Availability is the probability a system is operational at a given
20 which a system can be repaired or maintained; if the time to repair
21 a failed system increases, then availability will decrease.
24 Reliability is a measure of the ability of a system to function
|
| /linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
| D | twl4030-power.txt | 5 binding only supports the complete shutdown of the system after poweroff.
27 - ti,system-power-controller: This indicates that TWL4030 is the
28 power supply master of the system. With this flag, the chip will
30 system poweroffs.
32 - ti,use_poweroff: Deprecated name for ti,system-power-controller
|
| D | mfd.txt | 14 - A range of memory registers containing "miscellaneous system registers" also
15 known as a system controller "syscon" or any other memory range containing a
20 - compatible : "simple-mfd" - this signifies that the operating system should
26 operating system.
|
| D | max77693.txt | 52 voltage mode. Also vsys (system voltage) will be set to this value when
57 - maxim,min-system-microvolt : Minimal system voltage in uV.
68 in uA (current from battery to system).
103 if chip estimates that system voltage could drop below this level due
169 maxim,min-system-microvolt = <3600000>;
|
| /linux-4.4.14/Documentation/cpuidle/ |
| D | sysfs.txt | 8 /sys/devices/system/cpu/cpuidle
24 /sys/devices/system/cpu/cpuX/cpuidle
28 # ls -lR /sys/devices/system/cpu/cpu0/cpuidle/
29 /sys/devices/system/cpu/cpu0/cpuidle/:
36 /sys/devices/system/cpu/cpu0/cpuidle/state0:
46 /sys/devices/system/cpu/cpu0/cpuidle/state1:
56 /sys/devices/system/cpu/cpu0/cpuidle/state2:
66 /sys/devices/system/cpu/cpu0/cpuidle/state3:
|
| /linux-4.4.14/Documentation/timers/ |
| D | timekeeping.txt | 24 The purpose of the clock source is to provide a timeline for the system that
26 a Linux system will eventually read the clock source to determine exactly
31 It will ideally NEVER stop ticking as long as the system is running. It
32 may stop during system suspend.
47 the user-visible time to RTC clocks in the system or against networked time
49 the clock source, which provides the fundamental timeline for the system.
51 system to the shortcomings of it.
80 compensation code on both sides of the wrap point so that the system timeline
94 fire interrupts, so as to trigger events on the system timeline. On an SMP
95 system, it is ideal (and customary) to have one such event driving timer per
[all …]
|
| /linux-4.4.14/fs/nls/ |
| D | Kconfig | 24 The default NLS used when mounting file system. Note, that this is
26 system (if different) to store data (filenames) on a disk.
42 The Microsoft FAT file system family can deal with filenames in
54 The Microsoft FAT file system family can deal with filenames in
66 The Microsoft FAT file system family can deal with filenames in
79 The Microsoft FAT file system family can deal with filenames in
95 The Microsoft FAT file system family can deal with filenames in
110 The Microsoft FAT file system family can deal with filenames in
121 The Microsoft FAT file system family can deal with filenames in
132 The Microsoft FAT file system family can deal with filenames in
[all …]
|
| /linux-4.4.14/fs/bfs/ |
| D | Kconfig | 2 tristate "BFS file system support"
5 Boot File System (BFS) is a file system used under SCO UnixWare to
12 file system is contained in the file
18 bfs. Note that the file system of your root partition (the one
|
| /linux-4.4.14/drivers/video/fbdev/matrox/ |
| D | matroxfb_misc.c | 543 minfo->values.pll.system = get_unaligned_le16(bd->pins + 28) ? in parse_pins1()
555 minfo->values.pll.system = 50000; in default_pins1()
564 minfo->limits.system.vcomax = (bd->pins[41] == 0xFF) ? 230000 : ((bd->pins[41] + 100) * 1000); in parse_pins2()
569 minfo->values.pll.system = (bd->pins[43] == 0xFF) ? 50000 : ((bd->pins[43] + 100) * 1000); in parse_pins2()
578 minfo->limits.system.vcomax = 230000; in default_pins2()
580 minfo->values.pll.system = 50000; in default_pins2()
588 minfo->limits.system.vcomax = (bd->pins[36] == 0xFF) ? 230000 : ((bd->pins[36] + 100) * 1000); in parse_pins3()
606 minfo->limits.system.vcomax = 230000; in default_pins3()
618 …minfo->limits.system.vcomax = (bd->pins[ 38] == 0xFF) ? minfo->limits.pixel.vcomax : bd->pins[ 38]… in parse_pins4()
628 minfo->values.pll.system = (bd->pins[ 65] == 0xFF) ? 200000 : bd->pins[ 65] * 4000; in parse_pins4()
[all …]
|
| /linux-4.4.14/drivers/pci/hotplug/ |
| D | Kconfig | 35 system configuration options in NVRAM.
55 Say Y here if you have a system that supports PCI Hotplug using
64 Say Y here if you have an IBM system that supports PCI Hotplug using
75 Say Y here if you have a CompactPCI system card with CompactPCI
85 formerly just Ziatech) Ziatech ZT5550 CompactPCI system card.
96 Say Y here if you have a CompactPCI system card that exposes the #ENUM
97 hotswap signal as a bit in a system register that can be read through
120 Say Y here if you have a RPA system that supports PCI Hotplug.
131 Say Y here if your system supports Dynamic Logical Partitioning
|
| /linux-4.4.14/Documentation/cpu-freq/ |
| D | boost.txt | 7 /sys/devices/system/cpu/cpufreq/boost
8 controls the boost setting for the whole system. You can read and write
10 Reading or writing 1 does not mean that the system is boosting at this
37 functionality at least for the benchmark's run-time the system will run
53 /sys/devices/system/cpu/cpufreq/boost
61 whole system (0) or will allow the software or hardware to boost at will
64 Writing a "1" does not explicitly boost the system, but just allows the
76 (/sys/devices/system/cpu[0-9]*/cpufreq) and was called "cpb".
78 actual implementation only supported a system-global switch semantics,
|
| D | cpufreq-stats.txt | 23 in /sysfs (<sysfs root>/devices/system/cpu/cpuX/cpufreq/stats/) for each CPU.
43 <mysystem>:/sys/devices/system/cpu/cpu0/cpufreq/stats # ls -l
60 <mysystem>:/sys/devices/system/cpu/cpu0/cpufreq/stats # cat time_in_state
75 <mysystem>:/sys/devices/system/cpu/cpu0/cpufreq/stats # cat total_trans
88 <mysystem>:/sys/devices/system/cpu/cpu0/cpufreq/stats # cat trans_table
|
| /linux-4.4.14/certs/ |
| D | Kconfig | 18 bool "Provide system-wide ring of trusted keys"
21 Provide a system keyring to which trusted keys can be added. Keys in
30 string "Additional X.509 keys for default system keyring"
35 system keyring. Any certificate used for module signing is implicitly
38 NOTE: If you previously provided keys for the system keyring in the
|
| /linux-4.4.14/fs/qnx4/ |
| D | Kconfig | 2 tristate "QNX4 file system support (read only)"
5 This is the file system used by the real-time operating systems
10 To compile this file system support as a module, choose M here: the
|
| /linux-4.4.14/Documentation/devicetree/bindings/sound/ |
| D | renesas,rsrc-card.txt | 46 - clocks / system-clock-frequency : specify subnode's clock if needed.
47 it can be specified via "clocks" if system has
48 clock node (= common clock), or "system-clock-frequency"
49 (if system doens't support common clock)
72 system-clock-frequency = <11289600>;
|
| /linux-4.4.14/Documentation/gpio/ |
| D | drivers-on-gpio.txt | 41 system by pulling a GPIO line and will register a restart handler so
42 userspace can issue the right system call to restart the system.
44 - poweroff-gpio: drivers/power/gpio-poweroff.c is used to power the system down
46 userspace can issue the right system call to power down the system.
53 appear as any other I2C bus to the system and makes it possible to connect
58 GPIO hammering (bitbang). It will appear as any other SPI bus on the system
68 system, connected to a GPIO line (and optionally a GPIO alarm line),
69 presenting all the right in-kernel and sysfs interfaces to make your system
79 periodically, it will reset the system.
|
| /linux-4.4.14/kernel/time/ |
| D | Kconfig | 79 bool "Idle dynticks system (tickless idle)"
83 This option enables a tickless idle system: timer interrupts
84 will only trigger on an as-needed basis when the system is idle.
90 bool "Full dynticks system (tickless)"
120 bool "Full dynticks system on all CPUs by default (except CPU 0)"
125 CPUs in the system are full dynticks by default.
130 bool "Detect full-system idle state for full dynticks system"
153 int "Number of CPUs above which large-system approach is used"
158 The full-system idle detection mechanism takes a lazy approach
165 system that will be considered to be "small".
|
| /linux-4.4.14/Documentation/networking/ |
| D | iphase.txt | 21 - Multiple adapters in a system are supported.
38 1. Installing the adapters in the system
39 To install the ATM adapters in the system, follow the steps below.
41 b. Shut down the system and power off the system.
42 c. Install one or more ATM adapters in the system.
45 connected to the switch properly when the system is powered up.
46 e. Power on and boot the system.
62 while the driver is loaded in the system.
74 You can also check the system log file /var/log/messages for messages
|
| D | cxgb.txt | 75 This feature, also known as "large send", enables a system's protocol stack
77 thereby reducing system CPU utilization and enhancing performance.
99 The following information is provided as an example of how to change system
101 want to change these system parameters, depending on your server/workstation
110 Making any of the following system changes will only last until you reboot
111 your system. You may want to write a script that runs at boot-up which
112 includes the optimal settings for your system.
132 Set smp_affinity (on a multiprocessor system) to a single CPU:
208 1. Large number of TCP retransmits on a multiprocessor (SMP) system.
210 On a system with multiple CPUs, the interrupt (IRQ) for the network
[all …]
|
| D | lapb-module.txt | 8 the Linux operating system that require a LAPB service. This document
214 system. The value of reason is always LAPB_OK.
225 LAPB_NOTCONNECTED The remote system was not connected.
227 system.
233 system or another event has occurred to terminate the link. This may be
235 system refused the request. The values for reason are:
238 system.
239 LAPB_REFUSED The remote system refused the connect request.
240 LAPB_NOTCONNECTED The remote system was not connected.
242 system.
[all …]
|
| D | e100.txt | 95 Configuring a network driver to load properly when the system is started is
97 an alias line to /etc/modprobe.d/*.conf as well as editing other system
100 proper way to configure a network device for your system, refer to your
140 WoL will be enabled on the system during the next shut down or reboot. For
142 loaded when shutting down or rebooting the system.
155 one system on two IP networks in the same Ethernet broadcast domain
157 will respond to IP traffic for any IP address assigned to the system.
|
| /linux-4.4.14/fs/ntfs/ |
| D | Kconfig | 2 tristate "NTFS file system support"
5 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003.
23 To compile this file system support as a module, choose M here: the
33 If you are experiencing any problems with the NTFS file system, say
36 be written to the system log. Note that debugging messages are
46 slowdown of the system.
73 on top of any DOS/Microsoft Windows system without partitioning your
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/omap/ |
| D | mpu.txt | 18 - For an OMAP5 SMP system:
25 - For an OMAP4 SMP system:
33 - For an OMAP3 monocore system:
|
| /linux-4.4.14/Documentation/thermal/ |
| D | intel_powerclamp.txt | 30 Consider the situation where a system’s power consumption must be
66 If the kernel can also inject idle time to the system, then a
67 closed-loop control system can be established that manages package
69 control system, where the target set point is a user-selected idle
97 on large scale systems (Westmere system with 80 processors).
119 In terms of dynamics of the idle control system, package level idle
120 time is considered largely as a non-causal system where its behavior
127 When used in a causal control system, such as a temperature control,
140 also true for the ability of a system to enter package level C-states.
152 This is to offset the error occurring when the system can
[all …]
|
| /linux-4.4.14/security/integrity/ima/ |
| D | Kconfig | 17 values of executables and other sensitive system files,
19 to change the contents of an important system file
22 If your system has a TPM chip, then IMA also maintains
25 whether or not critical system files have been modified.
116 It requires the system to be labeled with a security extended
132 keyring be signed by a key on the system trusted keyring.
142 .system keyring. This option enables X509 certificate
|
| /linux-4.4.14/arch/powerpc/platforms/pseries/ |
| D | Kconfig | 53 Provides: /sys/devices/system/cpu/pseries_(de)activation_hint_list
54 and /sys/devices/system/cpu/cpuN/pseries_(de)activation_hint
82 Provide system capacity information via human readable
90 debug messages to the system log. Select this if you are having a
103 With this option a system running in an LPAR can be given more
113 to reduce the memory size of the system. This is accomplished
115 makes sense for a system running in an LPAR where the unused pages
|
| /linux-4.4.14/Documentation/console/ |
| D | console.txt | 6 This type will be called 'system driver', and only one system driver is allowed
7 to exist. The system driver is persistent and it can never be unloaded, though
13 the system driver. However, modular drivers cannot take over the console
17 occupied by the system driver. In the same token, if the modular driver is
18 released by the console, the system driver will take over.
32 system which are named vtcon<n> where <n> is an integer from 0 to 15. Thus:
72 When unbinding, the modular driver is detached first, and then the system
75 system driver.
112 1. All drivers, except system drivers, must call either do_register_con_driver()
|
| /linux-4.4.14/arch/nios2/boot/ |
| D | Makefile | 38 extra-$(CONFIG_NIOS2_DTB_SOURCE_BOOL) += system.dtb
40 $(obj)/system.dtb: $(DTB_SRC) FORCE
44 $(obj)/linked_dtb.o: $(obj)/system.dtb
|
| /linux-4.4.14/Documentation/kdump/ |
| D | kdump.txt | 12 dump of the system kernel's memory needs to be taken (for example, when
13 the system panics). The system kernel's memory image is preserved across
18 a remote system.
23 When the system kernel boots, it reserves a small section of memory for
25 (DMA) from the system kernel does not corrupt the dump-capture kernel.
42 All of the necessary information about the system kernel's core image is
105 Build the system and dump-capture kernels
112 2) Or use the system kernel binary itself as dump-capture kernel and there is
123 Following are the configuration setting required for system and
129 1) Enable "kexec system call" in "Processor type and features."
[all …]
|
| /linux-4.4.14/fs/ubifs/ |
| D | Kconfig | 2 tristate "UBIFS file system support"
12 UBIFS is a file system for flash devices which works on top of UBI.
47 which means that file-system read operations will cause writes (inode atime
48 updates). This may affect file-system performance and increase flash device wear,
|
| /linux-4.4.14/fs/qnx6/ |
| D | Kconfig | 2 tristate "QNX6 file system support (read only)"
5 This is the file system used by the real-time operating systems
12 To compile this file system support as a module, choose M here: the
|
| /linux-4.4.14/fs/cramfs/ |
| D | Kconfig | 2 tristate "Compressed ROM file system support (cramfs) (OBSOLETE)"
8 file system for ROM based embedded systems. CramFs is read-only,
16 cramfs. Note that the root file system (the one containing the
|
| /linux-4.4.14/drivers/staging/rtl8723au/ |
| D | Kconfig | 18 This option enables Access Point mode. Unless you know that your system
19 will never be used as an AP, or the target system has limited memory,
27 Unless you know that this driver will never by used with BT, or the target system has
|
| /linux-4.4.14/arch/alpha/kernel/ |
| D | machvec_impl.h | 146 #define ALIAS_MV(system) \
147 struct alpha_machine_vector alpha_mv __attribute__((alias(#system "_mv")));
149 #define ALIAS_MV(system) \ argument
150 asm(".global alpha_mv\nalpha_mv = " #system "_mv");
|
| /linux-4.4.14/Documentation/ia64/ |
| D | fsys.txt | 80 (fsyscall_table). This table contains one entry for each system call.
81 By default, a system call is handled by fsys_fallback_syscall(). This
83 normal Linux system call handler. For performance-critical system
86 of the getpid() system call.
94 - r15 = system call number
96 - r32-r39 = system call arguments
105 - r15 = system call number (as passed into the fsyscall handler)
106 - r32-r39 = system call arguments (as passed into the fsyscall handler)
116 doing a full system call (by calling fsys_fallback_syscall).
120 system call restart. Of course, all "preserved" registers also
[all …]
|
| /linux-4.4.14/arch/ia64/ |
| D | Kconfig | 151 This selects the system type of your hardware. A "generic" kernel
152 will run on any supported IA-64 system. However, if you configure
153 a kernel for your specific system, it will be faster and smaller.
155 generic For any supported IA-64 system
198 types of ia64 systems. If you have an SGI Altix system, it's safe
210 types of ia64 systems. If you have an SGI UV system, it's safe
313 a system with only one CPU, say N. If you have a system with more
317 systems, but will use only one CPU of a multiprocessor system. If
319 single processor systems. On a single processor system, the kernel
333 You should set this to the number of CPUs in your system, but
[all …]
|
| /linux-4.4.14/Documentation/misc-devices/ |
| D | ics932s401 | 18 multiplied to get the real CPU clock), a system clock, a PCI clock, a USB
30 The clocks could be reprogrammed to increase system speed. I will not help you
31 do this, as you risk damaging your system!
|
| D | c2port.txt | 22 C2 Interface used for in-system programming of micro controllers.
24 By using this driver you can reprogram the in-system flash without EC2
41 banging) designed to enable in-system programming, debugging, and
50 info or read/write in-system flash.
71 However, for security reasons, the in-system flash access in not
|
| /linux-4.4.14/drivers/staging/lustre/ |
| D | README.txt | 4 The Lustre file system is an open-source, parallel file system
8 the Lustre file system is a widely-used option in HPC.
9 The Lustre file system provides a POSIX compliant file system interface,
|
| /linux-4.4.14/Documentation/usb/ |
| D | persist.txt | 1 USB device persistence during system suspend
16 If a USB device's power session is interrupted then the system is
21 device plugged into the port. The system must assume the worst.
24 controller loses power during a system suspend, then when the system
31 while the system was asleep and a new keyboard was plugged in when the
32 system woke up, who cares? It'll still work the same when you type on
37 been unplugged while the system was suspended. If you had a mounted
40 root filesystem was located on the device, since your system will
45 even though suspend current may have been maintained while the system
61 the system can't be suspended at all. (All right, it _can_ be
[all …]
|
| D | gadget_serial.txt | 45 no longer statically defined. Your Linux based system should mount
54 side driver. It runs on a Linux system that has USB device side
55 hardware; for example, a PDA, an embedded Linux system, or a PC
81 On the device-side Linux system, the gadget serial driver looks
84 On the host-side system, the gadget serial device looks like a
125 side Linux system. You can add this to the start up scripts, if
128 Your system should use mdev (from busybox) or udev to make the
136 Note that the major number (253, above) is system-specific. If
189 to the Linux host with a USB cable, the host system should recognize
209 If the host side Linux system is configured properly, the ACM driver
[all …]
|
| /linux-4.4.14/Documentation/vm/ |
| D | numa | 8 From the hardware perspective, a NUMA system is a computer platform that
16 of the system--although some components necessary for a stand-alone SMP system
17 may not be populated on any given cell. The cells of the NUMA system are
18 connected together with some sort of system interconnect--e.g., a crossbar or
19 point-to-point link are common types of NUMA system interconnects. Both of
26 is handled in hardware by the processor caches and/or the system interconnect.
37 memory bandwidth. However, to achieve scalable memory bandwidth, system and
42 This leads to the Linux software view of a NUMA system:
44 Linux divides the system's hardware resources into multiple software
61 the existing nodes--or the system memory for non-NUMA platforms--into multiple
[all …]
|
| D | hugetlbpage.txt | 14 system call or standard SYSV shared memory system calls (shmget, shmat).
25 proper alignment and size of the arguments to system calls that map huge page
65 pool, a user with appropriate privilege can use either the mmap system call
66 or shared memory system calls to use the huge pages. See the discussion of
100 physically contiguous memory that is present in system at the time of the
102 some nodes in a NUMA system, it will attempt to make up the difference by
111 distribution of huge pages in a NUMA system, use:
113 cat /sys/devices/system/node/node*/meminfo | fgrep Huge
221 interleaving over all nodes in the system or cpuset.
226 subset of the system nodes to allocate huge pages outside the cpuset
[all …]
|
| /linux-4.4.14/arch/mips/dec/prom/ |
| D | identify.c | 46 static char system[STR_BUF_LEN]; in get_system_type() local
51 snprintf(system, STR_BUF_LEN, "Digital %s", in get_system_type()
55 return system; in get_system_type()
|
| /linux-4.4.14/fs/affs/ |
| D | Kconfig | 2 tristate "Amiga FFS file system support"
5 The Fast File System (FFS) is the common file system used on hard
20 To compile this file system support as a module, choose M here: the
|
| /linux-4.4.14/fs/ceph/ |
| D | Kconfig | 2 tristate "Ceph distributed file system"
11 experimental Ceph distributed file system. Ceph is an extremely
12 scalable file system designed to provide high performance,
|
| /linux-4.4.14/Documentation/devicetree/bindings/input/ |
| D | input-reset.txt | 6 specified) the system is sync'ed and reset.
8 Key sequences are global to the system but all the keys in a set must be coming
19 generating a sysrq. If omitted the system is rebooted immediately when a valid
|
| /linux-4.4.14/Documentation/devicetree/bindings/rtc/ |
| D | rtc-omap.txt | 17 - system-power-controller: whether the rtc is controlling the system power
30 system-power-controller;
|
| /linux-4.4.14/fs/sysv/ |
| D | Kconfig | 2 tristate "System V/Xenix/V7/Coherent file system support"
21 network using NFS, you don't need the System V file system support
22 (but you need NFS file system support obviously).
29 the System V file system in
|
| /linux-4.4.14/fs/isofs/ |
| D | Kconfig | 2 tristate "ISO 9660 CDROM file system support"
4 This is the standard file system used on CD-ROMs. It was previously
14 To compile this file system support as a module, choose M here: the
22 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
|
| /linux-4.4.14/drivers/scsi/arm/ |
| D | Kconfig | 10 Acorn system with one of these, say Y. If unsure, say N.
50 Acorn system with one of these, say Y. If unsure, say N.
57 system with one of these, say Y, otherwise say N.
75 Acorn system with one of these, say Y. If unsure, say N.
83 system with one of these, say Y. If unsure, say N.
|
| /linux-4.4.14/fs/adfs/ |
| D | Kconfig | 2 tristate "ADFS file system support"
5 The Acorn Disc Filing System is the standard file system of the
6 RiscOS operating system which runs on Acorn's ARM-based Risc PC
|
| /linux-4.4.14/fs/exofs/ |
| D | Kconfig | 2 tristate "exofs: OSD based file system support"
5 EXOFS is a file system that uses an OSD storage device,
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ |
| D | pistachio-clock.txt | 48 peripherals. The peripheral system clock ("periph_sys") generated by the core
58 - clock-names: Must include "periph_sys", the peripheral system clock generated
74 The peripheral general control block generates system interface clocks and
76 control registers. The system clock ("sys") generated by the peripheral clock
77 controller is the input clock to the system clock controller.
86 - clock-names: Must include "sys", the system clock generated by the peripheral
|
| /linux-4.4.14/Documentation/watchdog/ |
| D | watchdog-api.txt | 6 Copyright 2002 Christer Weingel <wingel@nano-system.com>
16 computer system in case of a software fault. You probably knew that
24 the system. If userspace fails (RAM error, kernel bug, whatever), the
26 system (causing a reboot) after the timeout occurs.
48 crashes the system will not reboot. Because of this, some of the
52 started. So, if the watchdog daemon crashes, the system will reboot
110 actual time they will reset the system. This can be done with an NMI,
134 before the system will reboot. The WDIOC_GETTIMELEFT is the ioctl
142 All watchdog drivers are required return more information about the system,
144 the reason for the last reboot of the system. The GETSUPPORT ioctl is
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/4xx/ |
| D | reboot.txt | 1 Reboot property to control system reboot on PPC4xx systems:
9 3 - PPC4xx system reset (default)
|
| D | hsta.txt | 6 between the plb4 and plb6 system buses to provide high speed data
7 transfer between memory and system peripherals as well as support for
|
| /linux-4.4.14/Documentation/arm/keystone/ |
| D | knav-qmss.txt | 8 the main hardware sub system which forms the backbone of the Keystone
45 ubifs file system and provide a sym link to k2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin
46 in the file system and boot up the kernel. User would see
53 file system. The driver doesn't acc queues to the supported queue range if
56 to file system before using these queue types.
|
| /linux-4.4.14/drivers/s390/char/ |
| D | Kconfig | 30 Include support for using an IBM 3270 terminal as a Linux system
46 Linux system console.
64 system console.
79 Linux system console.
86 This option enables the hardware console interface for system
88 gives you a nice name for the system on the service element.
165 prompt "Support for the z/VM recording system services (VM only)"
169 by the z/VM recording system services, eg. from *LOGREC, *ACCOUNT or
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | perf-stat.txt | 59 system-wide collection from all CPUs
86 to activate system-wide monitoring. Default is to count on all CPUs.
90 Do not aggregate counts across all monitored CPUs in system-wide mode (-a).
91 This option is only valid in system-wide mode.
144 Aggregate counts per processor socket for system-wide mode measurements. This
146 use --per-socket in addition to -a. (system-wide). The output includes the
151 Aggregate counts per physical processor for system-wide mode measurements. This
153 use --per-core in addition to -a. (system-wide). The output includes the
|
| /linux-4.4.14/fs/nfsd/ |
| D | Kconfig | 12 files residing on this system using Sun's Network File System
26 available to clients mounting the NFS server on this system.
40 This option enables support in your system's NFS server for
57 This option enables support in your system's NFS server for the
59 POSIX ACLs on files exported by your system's NFS server. NFS
77 This option enables support in your system's NFS server for
|
| /linux-4.4.14/Documentation/devicetree/bindings/reserved-memory/ |
| D | reserved-memory.txt | 4 The operating system shall exclude reserved memory from normal usage
52 be used by an operating system to instanciate the necessary pool
56 - Indicates the operating system must not create a virtual mapping
57 of the region as part of its standard mapping of system memory,
61 - The operating system can use the memory in this region with the
64 system can use that region to store volatile or cached data that
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/apm/ |
| D | scu.txt | 3 This system clock unit contain various register that control block resets,
14 scu: system-clk-controller@17000000 {
|
| /linux-4.4.14/fs/hfs/ |
| D | Kconfig | 2 tristate "Apple Macintosh file system support"
11 To compile this file system support as a module, choose M here: the
|
| /linux-4.4.14/Documentation/block/ |
| D | null_blk.txt | 21 All of them have a completion queue for each core in the system.
36 The size of the device reported to the system.
39 The block size reported to the system.
72 queue for each CPU node in the system.
|
| /linux-4.4.14/fs/ocfs2/ |
| D | Kconfig | 2 tristate "OCFS2 file system support"
11 system with many similarities to ext3. It supports 64 bit inode
64 The ocfs2 filesystem has an extensive logging system. The system
|
| /linux-4.4.14/Documentation/kbuild/ |
| D | headers_install.txt | 9 used by the system's C library (such as glibc or uClibc) to define available
10 system calls, as well as constants and structures to be used with these
11 system calls. The C library's header files include the kernel header files
12 from the "linux" subdirectory. The system's libc headers are usually
|
| /linux-4.4.14/Documentation/scsi/ |
| D | FlashPoint.txt | 12 operating system support to its BusLogic brand of FlashPoint Ultra SCSI
14 MultiMaster line, currently support the Linux operating system. Linux
46 and system boards. Through its wide range of RAID controllers and its
51 major distributors, VARs, and system integrators. Mylex Corporation is
77 system like Linux, the FlashPoint LT has been touted by computer system
80 caused grief for many people who inadvertently purchased a system expecting
92 operating system and then later decided to run Linux, or those who had
143 test system provided an ideal environment for testing error recovery
145 are crucial to overall system stability. It was especially convenient
149 embedded system. I am presently working on some performance testing and
|
| /linux-4.4.14/samples/bpf/ |
| D | tracex6_user.c | 43 status = system("ls > /dev/null"); in test_bpf_perf_event()
46 status = system("sleep 2"); in test_bpf_perf_event()
|
| /linux-4.4.14/arch/m68k/ifpsp060/ |
| D | fskeleton.S | 60 | routine. The operating system can do system dependent clean-up or
71 | is present. The routine below should point to the operating system handler
90 | is present. The routine below should point to the operating system handler
108 | is present. The routine below should point to the operating system handler
127 | is present. The routine below should point to the operating system handler
146 | is present. The routine below should point to the operating system handler
165 | is present. The routine below should point to the operating system handler
184 | is present. The routine below should point to the operating system handler
247 | system handler for the trap exception vector number 7.
|
| /linux-4.4.14/Documentation/arm/ |
| D | Booting | 32 kernel will use for volatile data storage in the system. It performs
99 the system memory, and root filesystem location. Therefore, the
110 The tagged list should be stored in system RAM.
119 The boot loader must load a device tree image (dtb) into system ram
127 system memory, and the root filesystem location. The dtb must be
160 The zImage may also be placed in system RAM and called there. The
167 In this case the kernel must be loaded at an offset into system equal
179 r2 = physical address of tagged list in system RAM, or
180 physical address of device tree block (dtb) in system RAM
207 possible. Except for entering in HYP mode, the system configuration
|
| D | Setup | 23 This is the total number of pages of memory in the system. If
25 of pages in the system.
27 If the system contains separate VRAM, this value should not
108 system revision number.
113 system 64-bit serial number
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/can/ |
| D | mpc5xxx-mscan.txt | 26 "sys" for system clock
28 clock source and frequency based on the system
32 - fsl,mscan-clock-divider: for the reference and system clock, an additional
|
| /linux-4.4.14/Documentation/serial/ |
| D | rocket.txt | 60 installed in the system, the mapping of port names to serial ports is displayed
61 in the system log at /var/log/messages.
65 upon system boot, edit a /etc/modprobe.d/*.conf file and add the line
69 This is only required once, the system will retain the names once created. To
116 various Rocketport boards in a system.
119 conflict with any other cards in the system, including other
121 address ranges which may be in use by other devices in your system.
122 On a Linux system, "cat /proc/ioports" will also be helpful in
124 system.
|
| /linux-4.4.14/Documentation/devicetree/bindings/iio/adc/ |
| D | berlin2_adc.txt | 4 It is part of the system controller register set. The ADC node should be a
5 sub-node of the system controller node.
|
| /linux-4.4.14/fs/nfs/ |
| D | Kconfig | 10 this file system support as a module, choose M here: the module
24 To configure a system which mounts its root file system via NFS
27 system on NFS" below. You cannot compile this file system as a
165 bool "Root file system on NFS"
168 If you want your system to mount its root file system via NFS,
|
| /linux-4.4.14/Documentation/pti/ |
| D | pti_intel_mid.txt | 2 system-on-a-chip designs based on the Parallel Trace
14 n_tracerouter.c and n_tracesink.c allow extra system information to
26 An example debugging usage for this driver system:
39 a system. 'Privileged' means the application has enough
60 // the ldiscs loaded in the system.
|
| /linux-4.4.14/arch/um/ |
| D | Kconfig.um | 29 While the User-Mode Linux port uses its own root file system for
54 a full-blown operating system running under every user mode linux
69 If you say Y here, you will have some control over the system even
70 if the system crashes for example during kernel debugging (e.g., you
71 will be able to flush the buffer cache to disk, reboot the system
|
| /linux-4.4.14/drivers/staging/rtl8188eu/ |
| D | Kconfig | 16 This option enables Access Point mode. Unless you know that your system
17 will never be used as an AP, or the target system has limited memory,
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | log-writes.txt | 5 of the write operations to. This is intended for file system developers wishing
6 to verify the integrity of metadata or data as the file system is written to.
36 inconsistent file system.
75 For example say you want to fsck a file system after every
99 Say you want to test fsync on your file system. You would do something like
119 Another option is to do a complicated file system operation and verify the file
120 system is consistent during the entire operation. You could do this with:
|
| /linux-4.4.14/fs/omfs/ |
| D | Kconfig | 6 This is the proprietary file system used by the Rio Karma music
12 To compile this file system support as a module, choose M here: the
|
| /linux-4.4.14/Documentation/devicetree/bindings/regulator/ |
| D | max8907.txt | 21 - maxim,system-power-controller: Boolean property indicating that the PMIC
22 controls the overall system power.
37 maxim,system-power-controller;
|
| /linux-4.4.14/scripts/ |
| D | analyze_suspend.py | 158 os.system('echo 0 > '+self.rtcpath+'/wakealarm')
174 os.system('echo %d > %s/wakealarm' % (alarm, self.rtcpath))
909 os.system('echo 0 > '+tp+'tracing_on')
911 os.system('echo global > '+tp+'trace_clock')
913 os.system('echo nop > '+tp+'current_tracer')
914 os.system('echo 100000 > '+tp+'buffer_size_kb')
918 os.system('echo function_graph > '+tp+'current_tracer')
919 os.system('echo "" > '+tp+'set_ftrace_filter')
921 os.system('echo funcgraph-abstime > '+tp+'trace_options')
922 os.system('echo funcgraph-proc > '+tp+'trace_options')
[all …]
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | firmware-assisted-dump.txt | 7 a crashed system, and to do so from a fully-reset system, and
8 to minimize the total elapsed time until the system is back
30 -- Unlike kdump, the system has been reset, and loaded
37 the system to the production configuration.
48 -- When a system crashes, the Power firmware will save
49 the low memory (boot memory of size larger of 5% of system RAM
51 also save system registers, and hardware PTE's.
56 size will be the larger of 5% of system RAM or 256MB.
172 Firmware-assisted dump feature uses sysfs file system to hold
191 1 = fadump is registered and ready to handle system crash.
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/timer/ |
| D | brcm,bcm2835-system-timer.txt | 10 - compatible : should be "brcm,bcm2835-system-timer"
18 compatible = "brcm,bcm2835-system-timer";
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | timestamping.txt | 1 The ALSA API can provide two different system timestamps:
3 - Trigger_tstamp is the system time snapshot taken when the .trigger
13 - tstamp is the current system timestamp updated during the last
18 and delay, which combined with the trigger and current system
30 along with a snapshot of system time. Applications can select from
74 time with dedicated hardware, possibly synchronized with system time,
96 and system time using the (tstamp-trigger_tstamp)/audio_tstamp
126 are. To avoid any interpretation issues, a single (system, audio)
131 In some hardware-specific configuration, the system timestamp is
139 this driver_timestamp will be identical to the regular system tstamp.
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
| D | arm,vic.txt | 4 system for interrupt routing. For multiple controllers they can either be
26 configured as wake up source for the system. Order of bits is the same as for
28 configured as a wake up source for the system. If unspecied, defaults to all
|
| /linux-4.4.14/drivers/vfio/platform/ |
| D | Kconfig | 7 use of platform devices present on the system using the VFIO
17 use of ARM AMBA devices present on the system using the VFIO
|
| /linux-4.4.14/drivers/zorro/ |
| D | Kconfig | 11 15KB, but it gets freed after the system boots up, so it doesn't
13 floppy or kernel for an embedded system where kernel image size
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | README | 25 screwed up your system because of wrong documentation, I won't
28 But of course, if you _do_ manage to screw up your system using
47 - a running Linux system
73 These are the subdirs I have on my system. There might be more
|
| /linux-4.4.14/arch/m68k/ |
| D | Kconfig | 96 bool "kexec system call"
100 kexec is a system call that implements the ability to shutdown your
102 but it is independent of the system firmware. And like a reboot
105 The name comes from the similarity to the exec system call.
|
| /linux-4.4.14/Documentation/security/ |
| D | LSM.txt | 16 specific changes to system operation when these tweaks are not available
20 Linux capabilities system. Most LSMs choose to extend the capabilities
21 system, building their checks on top of the defined capability hooks.
|
| /linux-4.4.14/drivers/input/mouse/ |
| D | Kconfig | 23 Say Y here if you have a PS/2 mouse connected to your system. This
47 your system.
57 your system.
67 your system.
77 your system.
87 TouchScreen connected to your system.
97 to your system.
106 to your system.
128 connected to your system.
148 your system.
[all …]
|
| /linux-4.4.14/drivers/tty/serial/ |
| D | Kconfig | 37 Say Y here if you wish to use an AMBA PrimeCell UART as the system
38 console (the system console is the device which receives all kernel
42 (/dev/tty0) will still be used as the system console by default, but
65 Say Y here if you wish to use an AMBA PrimeCell UART as the system
66 console (the system console is the device which receives all kernel
70 (/dev/tty0) will still be used as the system console by default, but
110 system console (the system console is the device which receives all
131 AT91 or AT32 processor as the system console (the system
199 system console (the system console is the device which
217 system console (the system console is the device which
[all …]
|
| /linux-4.4.14/drivers/ntb/ |
| D | Kconfig | 7 mapped memory will be mirrored to a buffer on the remote system. The
9 transfer data from one system to the other.
|
| /linux-4.4.14/drivers/staging/iio/Documentation/ |
| D | sysfs-bus-iio-ad7192 | 18 system. To minimize the current consumption of the system,
|
| /linux-4.4.14/fs/notify/fanotify/ |
| D | Kconfig | 8 notification system which differs from inotify in that it sends
22 listeners which need to scan files before allowing the system access to
|
| /linux-4.4.14/sound/oss/dmasound/ |
| D | Kconfig | 8 compatible with the Linux/i386 sound system. Otherwise, say N.
22 compatible with the Linux/i386 sound system. Otherwise, say N.
36 compatible with the Linux/i386 sound system. Otherwise, say N.
|
| /linux-4.4.14/Documentation/tpm/ |
| D | xen-tpmfront.txt | 12 operating system (in Xen terms, a DomU). This allows programs to interact with
13 a TPM in a virtual system the same way they interact with a TPM on the physical
14 system. Each guest gets its own unique, emulated, software TPM. However, each
79 logical vtpms on the system. The vTPM Platform Configuration
90 access to the physical TPM on the system and secures the
|
| /linux-4.4.14/drivers/input/misc/ |
| D | keyspan_remote.c | 95 u16 system; member
256 message.system = 0; in keyspan_check_data()
261 message.system = message.system << 1; in keyspan_check_data()
265 message.system = (message.system << 1) + 1; in keyspan_check_data()
326 __func__, message.system, message.button, message.toggle); in keyspan_check_data()
|
| /linux-4.4.14/drivers/media/usb/dvb-usb/ |
| D | dib0700_core.c | 660 u8 system; member
667 u8 system; member
707 poll_reply->nec.system, poll_reply->nec.not_system, in dib0700_rc_urb_completion()
717 if (poll_reply->nec.system == 0x00 && in dib0700_rc_urb_completion()
727 keycode = RC_SCANCODE_NEC32(poll_reply->nec.system << 24 | in dib0700_rc_urb_completion()
731 } else if ((poll_reply->nec.system ^ poll_reply->nec.not_system) != 0xff) { in dib0700_rc_urb_completion()
733 keycode = RC_SCANCODE_NECX(poll_reply->nec.system << 8 | in dib0700_rc_urb_completion()
739 keycode = RC_SCANCODE_NEC(poll_reply->nec.system, in dib0700_rc_urb_completion()
748 keycode = RC_SCANCODE_RC5(poll_reply->rc5.system, poll_reply->rc5.data); in dib0700_rc_urb_completion()
753 poll_reply->rc5.not_used, poll_reply->rc5.system, in dib0700_rc_urb_completion()
|
| /linux-4.4.14/Documentation/driver-model/ |
| D | platform.txt | 6 like those used to integrate peripherals on many system-on-chip
14 entities in the system. This includes legacy port-based devices and
16 into system-on-chip platforms. What they usually have in common
98 only way for system setup code to set up the correct devices is to build
117 leaving that for system infrastructure. Such drivers can't be hotplugged
119 different system component than the driver.
121 The only "good" reason for this is to handle older system designs which, like
127 an operating system will be wrong often enough to make trouble.
175 early during system boot.
190 drivers early on during the system boot. The code is built on top of the
|
| /linux-4.4.14/Documentation/devicetree/bindings/thermal/ |
| D | imx-thermal.txt | 7 is higher than panic threshold, system will auto reboot by SRC module.
8 - fsl,tempmon : phandle pointer to system controller that contains TEMPMON
|
| /linux-4.4.14/Documentation/devicetree/bindings/mtd/ |
| D | flctl-nand.txt | 35 system@0 {
36 label = "system";
|
| /linux-4.4.14/drivers/input/touchscreen/ |
| D | Kconfig | 98 chip in your system.
111 such as AT42QT602240/ATMXT224, connected to your system.
136 your system.
174 to your system. You will also need to select appropriate
260 your system.
272 your system.
317 system.
330 system. It also supports 5-finger chip models, which can be
358 controller to your system.
382 your system.
[all …]
|