Searched +full:2 +full:- +full:way (Results 1 – 25 of 677) sorted by relevance
12345678910>>...28
| /Documentation/arch/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/devicetree/bindings/mux/ |
| D | mux-controller.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/mux/mux-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Peter Rosin <peda@axentia.se>
20 space is a simple zero-based enumeration. I.e. 0-1 for a 2-way multiplexer,
21 0-7 for an 8-way multiplexer, etc.
25 --------------------
28 specifier using the '#mux-control-cells' or '#mux-state-cells' property.
29 The value of '#mux-state-cells' will always be one greater than the value
[all …]
|
| /Documentation/devicetree/bindings/serial/ |
| D | serial-peripheral-props.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/serial/serial-peripheral-props.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Common Properties for Serial-attached Devices
10 - Rob Herring <robh@kernel.org>
11 - Greg Kroah-Hartman <gregkh@linuxfoundation.org>
19 max-speed:
28 current-speed:
35 * device supports auto-baud
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | yuv-formats.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _yuv-formats:
12 *color difference* signals, this way the green component can be
16 color in a way compatible with existing receivers a new signal carrier
29 direction are possible, common factors are 1 (no subsampling), 2 and 4, with
33 - `4:4:4`: No subsampling
34 - `4:2:2`: Horizontal subsampling by 2, no vertical subsampling
35 - `4:2:0`: Horizontal subsampling by 2, vertical subsampling by 2
36 - `4:1:1`: Horizontal subsampling by 4, no vertical subsampling
37 - `4:1:0`: Horizontal subsampling by 4, vertical subsampling by 4
[all …]
|
| /Documentation/devicetree/bindings/cache/ |
| D | baikal,bt1-l2-ctl.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/cache/baikal,bt1-l2-ctl.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Baikal-T1 L2-cache Control Block
11 - Serge Semin <fancer.lancer@gmail.com>
14 By means of the System Controller Baikal-T1 SoC exposes a few settings to
16 to change the Tag, Data and Way-select RAM access latencies. Baikal-T1
17 L2-cache controller block is responsible for the tuning. Its DT node is
22 const: baikal,bt1-l2-ctl
[all …]
|
| /Documentation/admin-guide/ |
| D | devices.txt | 1 0 Unnamed devices (e.g. non-device mounts)
7 2 = /dev/kmem OBSOLETE - replaced by /proc/kcore
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/dev-tools/ |
| D | sparse.rst | 11 contains some kernel-specific sparse information.
17 -----------------------------
25 PM_RESUME = (__force pm_request_t) 2
40 So the simpler way is to just do::
45 #define PM_RESUME ((__force pm_request_t) 2)
52 sure that bitwise types don't get mixed up (little-endian vs big-endian
53 vs cpu-endian vs whatever), and there the constant "0" really _is_
57 ------------------------------
64 __must_hold - The specified lock is held on function entry and exit.
66 __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/driver-api/media/ |
| D | tx-rx.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 .. _transmitter-receiver:
10 CSI-2 receiver in an SoC.
13 ---------
17 MIPI CSI-2
20 CSI-2 is a data bus intended for transferring images from cameras to
32 .. _`BT.656`: https://en.wikipedia.org/wiki/ITU-R_BT.656
35 -------------------
44 See :ref:`v4l2-mbus-pixelcode`.
49 The :ref:`V4L2_CID_LINK_FREQ <v4l2-cid-link-freq>` control is used to tell the
[all …]
|
| /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/filesystems/ |
| D | inotify.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Inotify - A Powerful yet Simple File Change Notification System
13 - Deleted obsoleted interface, just refer to manpages for user interface.
29 What is the design decision behind using an-fd-per-instance as opposed to
30 an fd-per-watch?
33 An fd-per-watch quickly consumes more file descriptors than are allowed,
35 select()-able. Yes, root can bump the per-process fd limit and yes, users
38 spaces is thus sensible. The current design is what user-space developers
41 thousand times is silly. If we can implement user-space's preferences
42 cleanly--and we can, the idr layer makes stuff like this trivial--then we
[all …]
|
| /Documentation/process/ |
| 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
53 be called 5.6-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
78 September 30 5.4-rc1, merge window closes
[all …]
|
| D | development-process.rst | 8 an attempt to document how this community works in a way which is
11 there is some technical material here, this is very much a process-oriented
18 :maxdepth: 2
21 2.Process
22 3.Early-stage
|
| /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
59 ASL Optimizing Compiler version 20140214-64 [Mar 29 2014]
60 Copyright (c) 2000 - 2014 Intel Corporation
62 ASL Input: minnomax.asl - 30 lines, 614 bytes, 7 keywords
63 AML Output: minnowmax.aml - 165 bytes, 6 named objects, 1 executable opcodes
76 It works in a similar way with initrd based ACPI tables override/upgrade: SSDT
90 mkdir -p kernel/firmware/acpi
[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/devicetree/bindings/i2c/ |
| D | i2c-gpio.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/i2c/i2c-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Wolfram Sang <wsa@kernel.org>
13 - $ref: /schemas/i2c/i2c-controller.yaml#
18 - const: i2c-gpio
20 sda-gpios:
24 from <dt-bindings/gpio/gpio.h> since the signal is by definition
28 scl-gpios:
[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/devicetree/bindings/iio/dac/ |
| D | dac.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jonathan Cameron <jic23@kernel.org>
13 A few properties are defined in a common way for DAC channels.
17 pattern: "^channel(@[0-9a-f]+)?$"
27 output-range-microamp:
28 maxItems: 2
29 minItems: 2
33 output-range-microvolt:
[all …]
|
| /Documentation/i2c/ |
| D | instantiating-devices.rst | 13 --------------------------------------------
17 is known in advance. It is thus possible to pre-declare the I2C devices
20 This information is provided to the kernel in a different way on different
24 instantiated automatically by i2c-core. The devices will be automatically
36 .. code-block:: dts
40 clock-frequency = <100000>;
49 gpio-controller;
50 #gpio-cells = <2>;
64 which is currently located at Documentation/firmware-guide/acpi/enumeration.rst.
78 .. code-block:: c
[all …]
|
| /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/networking/device_drivers/ethernet/dec/ |
| D | dmfe.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 as published by the Free Software Foundation; either version 2
26 dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
32 This way it will autodetect the device mode.This is the suggested way to load the module.Or you can…
56 - Implement pci_driver::suspend() and pci_driver::resume() power management methods.
57 - Check on 64 bit boxes.
58 - Check and fix on big endian boxes.
59 - Test and make sure PCI latency is now correct for all cases.
68 - Marcelo Tosatti <marcelo@conectiva.com.br>
69 - Alan Cox <alan@lxorguk.ukuu.org.uk>
[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/usb/ |
| D | raw-gadget.rst | 5 USB Raw Gadget is a gadget driver that gives userspace low-level control over
28 2. Raw Gadget allows providing arbitrary data as responses to USB requests,
33 3. Raw Gadget provides a way to select a UDC device/driver to bind to,
38 capabilities. This allows the user to write UDC-agnostic gadgets.
40 5. Raw Gadget has an ioctl-based interface instead of a filesystem-based
46 The user can interact with Raw Gadget by opening ``/dev/raw-gadget`` and
53 1. Create a Raw Gadget instance by opening ``/dev/raw-gadget``.
54 2. Initialize the instance via ``USB_RAW_IOCTL_INIT``.
62 Nevertheless, Raw Gadget provides a UDC-agnostic way to write USB gadgets.
71 https://github.com/xairy/raw-gadget
[all …]
|
| /Documentation/arch/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/dev-tools/kunit/api/ |
| D | functionredirection.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 stability of the rest of the system (making it less likely for test-specific
22 This coupling is often due to global state in some way: be it a global list of
32 A simpler way to intercept and replace some of the function calls is to use
39 Static stubs are a way of redirecting calls to one function (the "real"
57 .. code-block:: c
65 2. Write one or more replacement functions.
68 In the event they need to access or modify test-specific state, they can use
75 .. code-block:: c
93 .. code-block:: c
[all …]
|
12345678910>>...28