| /linux-3.3/drivers/eisa/ |
| D | eisa.ids | 18 ACE1010 "ACME Super Fast System Board"
26 ACR1201 "Acer 1200 486/25 EISA System Board"
27 ACR1211 "AcerFrame 3000SP33 486/33 EISA System Board"
39 ACR1711 "AcerFrame 1000 486/33 SYSTEM-2"
40 ACR1801 "Acer P43WE EISA System Board"
41 ACR3211 "AcerFrame 3000MP 486 SYSTEM-1"
42 ACR3221 "AcerFrame 486 Series SYSTEM-2"
43 ACR3231 "AcerFrame 486 Series SYSTEM-3"
44 ACR3241 "AcerFrame 486 Series SYSTEM-4"
45 ACR3261 "AcerFrame 3000MP 486 SYSTEM-1"
[all …]
|
| /linux-3.3/arch/s390/kernel/ |
| D | compat_wrapper.S | 3 * wrapper for 31 bit compatible system calls.
26 jg sys32_write # branch to system call
32 jg sys_open # branch to system call
36 jg sys_close # branch to system call
41 jg sys_creat # branch to system call
46 jg sys_link # branch to system call
50 jg sys_unlink # branch to system call
54 jg sys_chdir # branch to system call
58 jg compat_sys_time # branch to system call
64 jg sys_mknod # branch to system call
[all …]
|
| /linux-3.3/arch/powerpc/include/asm/ |
| D | ipic.h | 30 #define IPIC_SICFR 0x00 /* System Global Interrupt Configuration Register */
31 #define IPIC_SIVCR 0x04 /* System Global Interrupt Vector Register */
32 #define IPIC_SIPNR_H 0x08 /* System Internal Interrupt Pending Register (HIGH) */
33 #define IPIC_SIPNR_L 0x0C /* System Internal Interrupt Pending Register (LOW) */
34 #define IPIC_SIPRR_A 0x10 /* System Internal Interrupt group A Priority Register */
35 #define IPIC_SIPRR_B 0x14 /* System Internal Interrupt group B Priority Register */
36 #define IPIC_SIPRR_C 0x18 /* System Internal Interrupt group C Priority Register */
37 #define IPIC_SIPRR_D 0x1C /* System Internal Interrupt group D Priority Register */
38 #define IPIC_SIMSR_H 0x20 /* System Internal Interrupt Mask Register (HIGH) */
39 #define IPIC_SIMSR_L 0x24 /* System Internal Interrupt Mask Register (LOW) */
[all …]
|
| /linux-3.3/include/asm-generic/ |
| D | syscall.h | 2 * Access to user system call parameters and results
26 * syscall_get_nr - find what system call a task is executing
30 * If @task is executing a system call or is at system call
31 * tracing about to attempt one, returns the system call number.
32 * If @task is not executing a system call, i.e. it's blocked
36 * system call number can be meaningful. If the actual arch value
44 * syscall_rollback - roll back registers after an aborted system call
45 * @task: task of interest, must be in system call exit tracing
48 * It's only valid to call this when @task is stopped for system
51 * the system call from taking place.
[all …]
|
| /linux-3.3/Documentation/ABI/testing/ |
| D | sysfs-devices-system-cpu | 1 What: /sys/devices/system/cpu/
10 /sys/devices/system/cpu/cpu#/
12 What: /sys/devices/system/cpu/sched_mc_power_savings
13 /sys/devices/system/cpu/sched_smt_power_savings
37 What: /sys/devices/system/cpu/kernel_max
38 /sys/devices/system/cpu/offline
39 /sys/devices/system/cpu/online
40 /sys/devices/system/cpu/possible
41 /sys/devices/system/cpu/present
60 the system.
[all …]
|
| 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 …]
|
| /linux-3.3/arch/arm/plat-samsung/include/plat/ |
| D | sysmmu.h | 6 * Samsung System MMU driver for S5P platform
33 * s5p_sysmmu_enable() - enable system mmu of ip
34 * @ips: The ip connected system mmu.
37 * This function enable system mmu to transfer address
44 * @ips: The ip connected system mmu.
46 * This function disable system mmu to transfer address
53 * @ips: The ip connected system mmu.
57 * When system mmu transfer address from virtaul address to physical address,
58 * system mmu refer address information from page table
63 * s5p_sysmmu_tlb_invalidate() - flush all TLB entry in system mmu
[all …]
|
| /linux-3.3/kernel/trace/ |
| D | trace_events.c | 247 static void __put_system(struct event_subsystem *system) in __put_system() argument
249 struct event_filter *filter = system->filter; in __put_system()
251 WARN_ON_ONCE(system->ref_count == 0); in __put_system()
252 if (--system->ref_count) in __put_system()
259 kfree(system->name); in __put_system()
260 kfree(system); in __put_system()
263 static void __get_system(struct event_subsystem *system) in __get_system() argument
265 WARN_ON_ONCE(system->ref_count == 0); in __get_system()
266 system->ref_count++; in __get_system()
269 static void put_system(struct event_subsystem *system) in put_system() argument
[all …]
|
| /linux-3.3/Documentation/ |
| 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 …]
|
| /linux-3.3/arch/m68k/include/asm/ |
| D | mcfpit.h | 24 #define MCFPIT_PCSR_CLK1 0x0000 /* System clock divisor */
25 #define MCFPIT_PCSR_CLK2 0x0100 /* System clock divisor */
26 #define MCFPIT_PCSR_CLK4 0x0200 /* System clock divisor */
27 #define MCFPIT_PCSR_CLK8 0x0300 /* System clock divisor */
28 #define MCFPIT_PCSR_CLK16 0x0400 /* System clock divisor */
29 #define MCFPIT_PCSR_CLK32 0x0500 /* System clock divisor */
30 #define MCFPIT_PCSR_CLK64 0x0600 /* System clock divisor */
31 #define MCFPIT_PCSR_CLK128 0x0700 /* System clock divisor */
32 #define MCFPIT_PCSR_CLK256 0x0800 /* System clock divisor */
33 #define MCFPIT_PCSR_CLK512 0x0900 /* System clock divisor */
[all …]
|
| /linux-3.3/Documentation/power/ |
| D | devices.txt | 12 This writeup gives an overview of how drivers interact with system-wide
23 System Sleep model:
24 Drivers can enter low-power states as part of entering system-wide
34 Some drivers can manage hardware wakeup events, which make the system
39 system enter low-power states more often.
42 Devices may also be put into low-power states while the system is
49 states at run time may require special handling during system-wide power
54 the PM core are involved in runtime power management. As in the system
60 very system-specific, and often device-specific. Also, that if enough devices
62 to entering some system-wide low-power state (system sleep) ... and that
[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 | 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 …]
|
| /linux-3.3/arch/mn10300/include/asm/ |
| D | exceptions.h | 37 /* system exceptions */
72 /* system calls */
73 EXCEP_SYSCALL0 = 0x000300, /* system call 0 */
74 EXCEP_SYSCALL1 = 0x000308, /* system call 1 */
75 EXCEP_SYSCALL2 = 0x000310, /* system call 2 */
76 EXCEP_SYSCALL3 = 0x000318, /* system call 3 */
77 EXCEP_SYSCALL4 = 0x000320, /* system call 4 */
78 EXCEP_SYSCALL5 = 0x000328, /* system call 5 */
79 EXCEP_SYSCALL6 = 0x000330, /* system call 6 */
80 EXCEP_SYSCALL7 = 0x000338, /* system call 7 */
[all …]
|
| /linux-3.3/include/linux/ |
| D | reboot.h | 5 * Magic values required to use _reboot() system call.
16 * Commands accepted by the _reboot() system call.
18 * RESTART Restart system using default command and mode.
19 * HALT Stop OS and give system control to ROM monitor, if any.
22 * POWER_OFF Stop OS and remove all power from system, if possible.
23 * RESTART2 Restart system using given command string.
24 * SW_SUSPEND Suspend system using software suspend if compiled in.
25 * KEXEC Restart system using a previously loaded Linux kernel
42 #define SYS_DOWN 0x0001 /* Notify of system down */
44 #define SYS_HALT 0x0002 /* Notify of system halt */
[all …]
|
| D | sysv_fs.h | 46 char s_fname[6]; /* file system volume name */
47 char s_fpack[6]; /* file system pack name */
50 s32 s_magic; /* version of file system */
51 __fs32 s_type; /* type of file system: 1 for 512 byte blocks
59 * sysv2: System V Release 2 (e.g. Microport), structure elements aligned(2).
60 * sysv4: System V Release 4 (e.g. Consensys), structure elements aligned(4).
88 char s_fname[6]; /* file system volume name */
89 char s_fpack[6]; /* file system pack name */
91 __fs32 s_state; /* file system state: 0x7c269d38-s_time means clean */
92 s32 s_magic; /* version of file system */
[all …]
|
| /linux-3.3/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-3.3/fs/ext3/ |
| D | Kconfig | 2 tristate "Ext3 journalling file system support"
5 This is the journalling version of the Second extended file system
6 (often called ext3), the de facto standard Linux file system
10 to run e2fsck (file system checker) on your file systems after a
12 at the time the system crashed, and can ensure that your file system
15 Other than adding the journal to the file system, the on-disk format
18 file system has been cleanly unmounted, or e2fsck is run on the file
19 system.
21 To add a journal on an existing ext2 file system or change the
28 To compile this file system support as a module, choose M here: the
[all …]
|
| /linux-3.3/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-3.3/fs/sysv/ |
| D | Kconfig | 2 tristate "System V/Xenix/V7/Coherent file system support"
14 UnixWare, Dell Unix and System V programs under Linux. It is
21 network using NFS, you don't need the System V file system support
22 (but you need NFS file system support obviously).
28 nothing whatsoever to do with the option "System V IPC". Read about
29 the System V file system in
|
| /linux-3.3/drivers/base/ |
| D | syscore.c | 2 * syscore.c - Execution of system core operations.
18 * register_syscore_ops - Register a set of system core operations.
19 * @ops: System core operations to register.
30 * unregister_syscore_ops - Unregister a set of system core operations.
31 * @ops: System core operations to unregister.
43 * syscore_suspend - Execute all the registered system core suspend callbacks.
60 "Interrupts enabled before system core suspend.\n"); in syscore_suspend()
76 pr_err("PM: System core suspend callback %pF failed.\n", ops->suspend); in syscore_suspend()
87 * syscore_resume - Execute all the registered system core resume callbacks.
96 "Interrupts enabled before system core resume.\n"); in syscore_resume()
[all …]
|
| /linux-3.3/fs/ubifs/ |
| D | key.h | 92 * @c: UBIFS file-system description object
105 * @c: UBIFS file-system description object
121 * @c: UBIFS file-system description object
134 * @c: UBIFS file-system description object
147 * @c: UBIFS file-system description object
166 * @c: UBIFS file-system description object
182 * @c: UBIFS file-system description object
202 * @c: UBIFS file-system description object
215 * @c: UBIFS file-system description object
233 * @c: UBIFS file-system description object
[all …]
|
| /linux-3.3/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
|
| /linux-3.3/Documentation/devicetree/bindings/ |
| D | marvell.txt | 1 Marvell Discovery mv64[345]6x System Controller chips
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
[all …]
|
| /linux-3.3/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 …]
|