Searched +full:2 +full:- +full:way (Results 1 – 25 of 525) sorted by relevance
12345678910>>...21
| /Documentation/devicetree/bindings/mux/ |
| D | mux-controller.txt | 11 space is a simple zero-based enumeration. I.e. 0-1 for a 2-way multiplexer,
12 0-7 for an 8-way multiplexer, etc.
16 ---------
19 want to use with a property containing a 'mux-ctrl-list':
21 mux-ctrl-list ::= <single-mux-ctrl> [mux-ctrl-list]
22 single-mux-ctrl ::= <mux-ctrl-phandle> [mux-ctrl-specifier]
23 mux-ctrl-phandle : phandle to mux controller node
24 mux-ctrl-specifier : array of #mux-control-cells specifying the
27 Mux controller properties should be named "mux-controls". The exact meaning of
29 each consumer. An optional property "mux-control-names" may contain a list of
[all …]
|
| /Documentation/admin-guide/ |
| D | devices.txt | 1 0 Unnamed devices (e.g. non-device mounts)
7 2 = /dev/kmem Kernel virtual memory access
11 6 = /dev/core OBSOLETE - replaced by /proc/kcore
18 12 = /dev/oldmem OBSOLETE - replaced by /proc/vmcore
31 2 char Pseudo-TTY masters
37 Pseudo-tty's are named as follows:
40 the 1st through 16th series of 16 pseudo-ttys each, and
44 These are the old-style (BSD) PTY devices; Unix98
49 2 block Floppy disks
52 2 = /dev/fd2 Controller 0, drive 2, autodetect
[all …]
|
| /Documentation/ia64/ |
| D | efirtc.rst | 13 the IA-64 platform.
23 2. Design Decisions
28 portable way, the CMOS clock. A program like /sbin/hwclock uses such a clock
31 Because we wanted to minimize the impact on existing user-level apps using
38 EFI uses a slightly different way of representing the time, noticeably
39 the reference date is different. Year is the using the full 4-digit format.
41 expose this new way of representing time. Instead we use something very
43 One of the reasons for doing it this way is to allow for EFI to still evolve
48 ioctl()s. The other is read-only via the /proc filesystem.
94 # /sbin/hwclock --show
[all …]
|
| /Documentation/x86/ |
| D | entry_64.rst | 1 .. SPDX-License-Identifier: GPL-2.0
16 for 64-bit, arch/x86/entry/entry_32.S for 32-bit and finally
17 arch/x86/entry/entry_64_compat.S which implements the 32-bit compatibility
18 syscall entry points and thus provides for 32-bit processes the
19 ability to execute syscalls when running on 64-bit kernels.
25 - system_call: syscall instruction from 64-bit code.
27 - entry_INT80_compat: int 0x80 from 32-bit or 64-bit code; compat syscall
28 either way.
30 - entry_INT80_compat, ia32_sysenter: syscall and sysenter from 32-bit
33 - interrupt: An array of entries. Every IDT vector that doesn't
[all …]
|
| /Documentation/dev-tools/ |
| D | sparse.rst | 11 contains some kernel-specific sparse information.
15 -----------------------------
23 PM_RESUME = (__force pm_request_t) 2
38 So the simpler way is to just do::
43 #define PM_RESUME ((__force pm_request_t) 2)
50 sure that bitwise types don't get mixed up (little-endian vs big-endian
51 vs cpu-endian vs whatever), and there the constant "0" really _is_
55 ------------------------------
62 __must_hold - The specified lock is held on function entry and exit.
64 __acquires - The specified lock is held on function exit, but not entry.
[all …]
|
| /Documentation/driver-api/driver-model/ |
| D | design-patterns.rst | 10 2. container_of()
21 The most common way to achieve this is to use the state container design
35 return -ENOMEM;
36 spin_lock_init(&foo->lock);
62 This way you always get a pointer back to the correct instance of foo in
66 2. container_of()
89 queue_work(foo->wq, &foo->offload);
97 foo->wq = create_singlethread_workqueue("foo-wq");
98 INIT_WORK(&foo->offload, foo_work);
115 instance this way, while still keeping the number of parameters passed to the
|
| /Documentation/filesystems/ |
| D | inotify.txt | 8 --Deleted obsoleted interface, just refer to manpages for user interface.
21 Q: What is the design decision behind using an-fd-per-instance as opposed to
22 an fd-per-watch?
24 A: An fd-per-watch quickly consumes more file descriptors than are allowed,
26 select()-able. Yes, root can bump the per-process fd limit and yes, users
29 spaces is thus sensible. The current design is what user-space developers
32 thousand times is silly. If we can implement user-space's preferences
33 cleanly--and we can, the idr layer makes stuff like this trivial--then we
38 fd returns all watch events and also any potential out-of-band data. If
41 - There would be no way to get event ordering. Events on file foo and
[all …]
|
| /Documentation/power/ |
| D | swsusp-and-swap-files.rst | 7 The Linux kernel handles swap files almost in the same way as it handles swap
11 (2) the header of a swap file is not in the first block of the partition that
13 already taken care of by the swap-handling code, but (2) has to be taken into
33 2) Use an application that will bmap the swap file with the help of the
44 application in 2) (of course, this step may be carried out automatically
52 Documentation/power/userland-swsusp.rst (this is the only method to suspend
56 Now, swsusp will use the swap file in the same way in which it would use a swap
|
| /Documentation/process/ |
| D | development-process.rst | 10 :maxdepth: 2
13 2.Process
14 3.Early-stage
23 an attempt to document how this community works in a way which is
26 there is some technical material here, this is very much a process-oriented
|
| D | 2.Process.rst | 8 user base in the millions and with some 2,000 developers involved over the
14 ---------------
16 The kernel developers use a loosely time-based release process, with a new
22 4.12 July 2, 2017
53 be called 2.6.40-rc1. The -rc1 release is the signal that the time to
63 exception is made for drivers for previously-unsupported hardware; if they
64 touch no in-tree code, they cannot cause regressions and should be safe to
67 As fixes make their way into the mainline, the patch rate will slow over
68 time. Linus releases new -rc kernels about once a week; a normal series
69 will get up to somewhere between -rc6 and -rc9 before the kernel is
[all …]
|
| /Documentation/security/ |
| D | sak.rst | 10 is an undefeatable way of killing all programs which could be
15 providing SAK. One is the ALT-SYSRQ-K sequence. You shouldn't use
19 The proper way of generating a SAK is to define the key sequence using
28 What key sequence should you use? Well, CTRL-ALT-DEL is used to reboot
29 the machine. CTRL-ALT-BACKSPACE is magical to the X server. We'll
30 choose CTRL-ALT-PAUSE.
46 2. On the PC keyboard, SAK kills all applications which have
57 # ls -l /proc/[0-9]*/fd/* | grep console
58 l-wx------ 1 root root 64 Mar 18 00:46 /proc/579/fd/0 -> /dev/console
63 root 579 0.0 0.1 1088 436 ? S 00:43 0:00 gpm -t ps/2
[all …]
|
| /Documentation/networking/device_drivers/dec/ |
| D | dmfe.txt | 7 as published by the Free Software Foundation; either version 2
21 dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
27 This way it will autodetect the device mode.This is the suggested way to load the module.Or you can…
|
| /Documentation/PCI/ |
| D | acpi-info.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 OS might use unless there's another way for the OS to find it [1, 2].
25 namespace [2]. The _CRS is like a generalized PCI BAR: the OS can read
39 If the OS is expected to manage a non-discoverable device described via
50 These are all device-specific, non-architected things, so the only way a
52 the device-specific details. The host bridge registers also include ECAM
64 Consumer/Producer meant there was no way to describe bridge registers in
66 bridge registers (including ECAM space) in PNP0C02 catch-all devices [6].
67 With the exception of ECAM, the bridge register space is device-specific
76 describe bridge registers this way on those architectures.
[all …]
|
| /Documentation/admin-guide/acpi/ |
| D | ssdt-overlays.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 In order to support ACPI open-ended hardware configurations (e.g. development
8 boards) we need a way to augment the ACPI configuration provided by the firmware
18 way to augment firmware ACPI configuration is by dynamically loading
60 ASL Optimizing Compiler version 20140214-64 [Mar 29 2014]
61 Copyright (c) 2000 - 2014 Intel Corporation
63 ASL Input: minnomax.asl - 30 lines, 614 bytes, 7 keywords
64 AML Output: minnowmax.aml - 165 bytes, 6 named objects, 1 executable opcodes
77 It works in a similar way with initrd based ACPI tables override/upgrade: SSDT
91 mkdir -p kernel/firmware/acpi
[all …]
|
| /Documentation/devicetree/bindings/gpio/ |
| D | rockchip,rk3328-grf-gpio.txt | 6 also be set in the same way.
12 - compatible: Should contain "rockchip,rk3328-grf-gpio".
13 - gpio-controller: Marks the device node as a gpio controller.
14 - #gpio-cells: Should be 2. The first cell is the pin number and
22 compatible = "rockchip,rk3328-grf", "syscon", "simple-mfd";
24 grf_gpio: grf-gpio {
25 compatible = "rockchip,rk3328-grf-gpio";
26 gpio-controller;
27 #gpio-cells = <2>;
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-log.rst | 2 Device-Mapper Logging
4 The device-mapper logging code is used by some of the device-mapper
14 There is a generic logging interface that the device-mapper RAID
16 dm_dirty_log_type in include/linux/dm-dirty-log.h). Various different
23 disk drivers/md/dm-log.c
24 core drivers/md/dm-log.c
25 userspace drivers/md/dm-log-userspace* include/linux/dm-log-userspace.h
29 -------------------
30 This log implementation commits the log state to disk. This way, the
34 -------------------
[all …]
|
| /Documentation/devicetree/bindings/ |
| D | example-schema.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 # All the top-level keys are standard json-schema keywords except for
10 $id: "http://devicetree.org/schemas/example-schema.yaml#"
11 # $schema is the meta-schema this schema should be validated with.
12 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
17 - Rob Herring <robh@kernel.org>
20 A more detailed multi-line description of the binding.
41 # isn't another way to express a constraint of the last string value.
44 - items:
[all …]
|
| /Documentation/bpf/ |
| D | prog_cgroup_sysctl.rst | 1 .. SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause)
8 provides cgroup-bpf hook for sysctl.
19 2. Context
31 (``1``). This field is read-only.
34 or written. This field is read-write. Writing to the field sets the starting
35 position in sysctl proc file ``read(2)`` will be reading from or ``write(2)``
37 whole sysctl value by ``bpf_sysctl_set_new_value()`` on ``write(2)`` even
38 when it's called by user space on ``file_pos > 0``. Writing non-zero
55 If program returns ``0`` user space will get ``-1`` from ``read(2)`` or
56 ``write(2)`` and ``errno`` will be set to ``EPERM``.
[all …]
|
| /Documentation/i2c/ |
| D | instantiating-devices.rst | 13 ------------------------------------------------
17 which is known in advance. It is thus possible to pre-declare the I2C
49 by i2c-core.
56 -------------------------------------------------
65 clock-frequency = <100000>;
74 gpio-controller;
75 #gpio-cells = <2>;
86 -------------------------------------------
89 which is currently located at Documentation/firmware-guide/acpi/enumeration.rst.
92 Method 2: Instantiate the devices explicitly
[all …]
|
| /Documentation/virt/kvm/ |
| D | ppc-pv.txt | 5 space code in PR=1 which is user space. This way we trap all privileged
32 'hypercall-instructions'. This property contains at most 4 opcodes that make
39 r0 - volatile
41 r4 2nd parameter 1st output value
42 r5 3rd parameter 2nd output value
49 r12 - volatile
73 applicable to the target. For now, we always map the page to -4096. This way we
77 ld rX, -4096(0)
144 mfmsr rX ld rX, magic_page->msr
145 mfsprg rX, 0 ld rX, magic_page->sprg0
[all …]
|
| /Documentation/arm/ |
| D | interrupts.rst | 5 2.5.2-rmk5:
7 major architecture-specific subsystems.
9 Firstly, it contains some pretty major changes to the way we handle the
10 MMU TLB. Each MMU TLB variant is now handled completely separately -
18 The 2.5 kernels will be having major changes to the way IRQs are handled.
25 GPIO25 IRR:2
26 SA1100 ------------> Neponset -----------> SA1111
28 -----------> USAR
30 -----------> SMC9196
32 The way stuff currently works, all SA1111 interrupts are mutually
[all …]
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | arm-mhu.txt | 4 The ARM's Message-Handling-Unit (MHU) is a mailbox controller that has
7 received data. However, there is no specified way of knowing if the sent
17 --------------------
18 - compatible: Shall be "arm,mhu" & "arm,primecell"
19 - reg: Contains the mailbox register address range (base
21 - #mbox-cells Shall be 1 - the index of the channel needed.
22 - interrupts: Contains the interrupt information corresponding to
26 --------
28 mhu: mailbox@2b1f0000 {
29 #mbox-cells = <1>;
[all …]
|
| /Documentation/device-mapper/ |
| D | dm-bow.txt | 9 dm_bow has three states, set by writing ‘1’ or ‘2’ to /sys/block/dm-?/bow/state.
11 state 1 to state 2.
20 the free (trimmed) area as needed in such a way as they can be restored.
25 isn't enough free space, writes are failed with -ENOSPC.
27 State 2: The transition to state 2 triggers replacing the special sector 0 with
29 becomes a pass-through driver, allowing the device to continue to be used with
34 dm-bow takes one command line parameter, the name of the underlying device.
36 dm-bow will typically be used in the following way. dm-bow will be loaded with a
40 the changes can either be committed by switching to state 2, or rolled back by
41 unmounting the file system, removing the dm-bow device and running the command
[all …]
|
| /Documentation/input/devices/ |
| D | rotary-encoder.rst | 2 rotary-encoder - a generic driver for GPIO connected devices
8 --------
11 peripherals with two wires. The outputs are phase-shifted by 90 degrees
16 a stable state with both outputs high (half-period mode) and some have
17 a stable state in all steps (quarter-period mode).
33 |<-------->|
36 |<-->|
37 one step (half-period mode)
40 one step (quarter-period mode)
47 ----------------------
[all …]
|
| /Documentation/watchdog/ |
| D | mlx-wdt.rst | 13 There are 2 types of HW watchdog implementations.
16 Actual HW timeout can be defined as a power of 2 msec.
19 Get time-left isn't supported
21 Type 2:
23 a user-defined timeout.
25 Get time-left is supported.
28 all new systems have type 2 HW watchdog.
31 Mellanox system can have 2 watchdogs: main and auxiliary.
36 The last 2 actions are performed without a system reset.
42 Watchdog can be initialised in nowayout way, i.e. oncse started
[all …]
|
12345678910>>...21