Searched +full:implementation +full:- +full:defined (Results 1 – 25 of 227) sorted by relevance
12345678910
| /Documentation/watchdog/ |
| D | mlx-wdt.rst | 16 Actual HW timeout can be defined as a power of 2 msec.
19 Get time-left isn't supported
22 Actual HW timeout is defined in sec. and it's the same as
23 a user-defined timeout.
25 Get time-left is supported.
31 Type 1 HW watchdog implementation exist in old systems and
33 Two types of HW implementation have also different register map.
35 Type 3 HW watchdog implementation can exist on all Mellanox systems
43 There are several actions that can be defined in the watchdog:
54 This mlx-wdt driver supports both HW watchdog implementations.
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | coresight-cti.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only or BSD-2-Clause
4 ---
5 $id: http://devicetree.org/schemas/arm/coresight-cti.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
22 number is defined at design time, the maximum of each defined in the DEVID
26 programmable channels, usually 4, but again implementation defined and
32 are implementation defined, except when the CTI is connected to an ARM v8
38 indicate this feature (arm,coresight-cti-v8-arch).
52 and usages. These can be defined along with the signal indexes with the
53 constants defined in <dt-bindings/arm/coresight-cti-dt.h>
[all …]
|
| /Documentation/driver-api/ |
| D | io-mapping.rst | 8 The io_mapping functions in linux/io-mapping.h provide an abstraction for
10 usage is to support the large graphics aperture on 32-bit processors where
33 'offset' is the offset within the defined mapping region.
39 This _wc variant returns a write-combining map to the
54 If you need to sleep while holding the lock, you can use the non-atomic
77 Current Implementation
80 The initial implementation of these functions uses existing mapping
84 On 64-bit processors, io_mapping_create_wc calls ioremap_wc for the whole
85 range, creating a permanent kernel-visible mapping to the resource. The
89 On 32-bit processors with HIGHMEM defined, io_mapping_map_atomic_wc uses
[all …]
|
| /Documentation/networking/device_drivers/ethernet/altera/ |
| D | altera_tse.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 Altera Triple-Speed Ethernet MAC driver
9 Copyright |copy| 2008-2014 Altera Corporation
11 This is the driver for the Altera Triple-Speed Ethernet (TSE) controllers
24 The Triple-Speed Ethernet, SGDMA, and MSGDMA components are all soft IP
31 Triple-Speed Ethernet instance is using an SGDMA or MSGDMA component. The
36 The SGDMA component is to be deprecated in the near future (over the next 1-2
46 Scatter-gather DMA is not supported by the SGDMA or MSGDMA at this time.
47 Scatter-gather DMA will be added to a future maintenance update to this
60 Device Drivers ---> Network device support ---> Ethernet driver support --->
[all …]
|
| /Documentation/crypto/ |
| D | intro.rst | 5 ------------
25 - consumers requesting cryptographic services
27 - data transformation implementations (typically ciphers) that can be
41 -----------
43 The transformation implementation is an actual code or interface to
45 defined behavior.
48 implementation. There can be multiple transformation objects associated
49 with a single transformation implementation. Each of those
52 consumer requests a transformation implementation. The consumer is then
|
| D | architecture.rst | 5 ----------------------
10 - Symmetric ciphers
12 - AEAD ciphers
14 - Message digest, including keyed message digest
16 - Random number generation
18 - User space interface
21 ---------------------
30 a caller or invoked together with a template to form multi-block ciphers
38 - aes
40 - ecb(aes)
[all …]
|
| /Documentation/networking/caif/ |
| D | linux_caif.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 Copyright |copy| ST-Ericsson AB 2010
17 CAIF is a MUX protocol used by ST-Ericsson cellular modems for
22 ST-Ericsson modems support a number of transports between modem
29 The implementation of CAIF is divided into:
32 * CAIF Core Protocol Implementation
39 ! +------+ +------+
40 ! +------+! +------+!
42 +-------> !interf!+ ! API !+ <- CAIF Client APIs
43 ! +------+ +------!
[all …]
|
| /Documentation/networking/ |
| D | ipsec.rst | 1 .. SPDX-License-Identifier: GPL-2.0
17 2.2. Non-Expansion Policy
20 defined in section 3, is not smaller than the size of the original
21 payload, the IP datagram MUST be sent in the original non-compressed
22 form. To clarify: If an IP datagram is sent non-compressed, no
33 is implementation dependent.
35 Current IPComp implementation is indeed by the book, while as in practice
36 when sending non-compressed packet to the peer (whether or not packet len
|
| /Documentation/admin-guide/ |
| D | lockup-watchdogs.rst | 8 A 'softlockup' is defined as a bug that causes the kernel to loop in
9 kernel mode for more than 20 seconds (see "Implementation" below for
14 "softlockup_panic" (see "Documentation/admin-guide/kernel-parameters.rst" for
18 A 'hardlockup' is defined as a bug that causes the CPU to loop in
19 kernel mode for more than 10 seconds (see "Implementation" below for
26 (see "Documentation/admin-guide/kernel-parameters.rst" for details).
33 Implementation subtitle
43 (compile-time initialized to 10 and configurable through sysctl of the
64 event. The right value for a particular environment is a trade-off
77 to continue to run on the housekeeping (non-tickless) cores means
|
| /Documentation/virt/kvm/devices/ |
| D | arm-vgic.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 - KVM_DEV_TYPE_ARM_VGIC_V2 ARM Generic Interrupt Controller v2.0
13 controller, requiring emulated user-space devices to inject interrupts to the
18 device and guest ITS devices, see arm-vgic-v3.txt. It is not possible to
26 KVM_VGIC_V2_ADDR_TYPE_DIST (rw, 64-bit)
31 KVM_VGIC_V2_ADDR_TYPE_CPU (rw, 64-bit)
39 -E2BIG Address outside of addressable IPA range
40 -EINVAL Incorrectly aligned address
41 -EEXIST Address already configured
42 -ENXIO The group or attribute is unknown/unsupported for this device
[all …]
|
| /Documentation/driver-api/soundwire/ |
| D | summary.rst | 10 SoundWire is a 2-pin multi-drop interface with data and clock line. It
15 commands over a single two-pin interface.
23 (4) Device status monitoring, including interrupt-style alerts to the Master.
38 +---------------+ +---------------+
40 | Master |-------+-------------------------------| Slave |
42 | |-------|-------+-----------------------| |
43 +---------------+ | | +---------------+
47 +--+-------+--+
52 +-------------+
64 3rd-party vendors to enable implementation-defined functionality while
[all …]
|
| D | error_handling.rst | 13 1. Bus clash or parity errors: This mechanism relies on low-level detectors
15 and audio data. The current implementation only logs such errors.
20 impact its audibility (most-significant bits will be more impacted in PCM),
34 be applied. In case of a bad programming (command sent to non-existent
35 Slave or to a non-implemented register) or electrical issue, no response
40 reset and re-enumerate all devices.
47 driver will return a -ETIMEOUT. Such timeouts are symptoms of a faulty
58 hard-reset might be the best solution.
62 that the Slave might behave in implementation-defined ways. The bus
63 implementation does not provide a recovery mechanism for such errors, Slave
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | cpus.txt | 9 defined below may be present on CPU nodes.
13 - fsl,eref-*
18 Power CPUs. The EREF defines some architecture categories not defined
19 by the Power ISA. For these EREF-specific categories, the existence of
20 a property named fsl,eref-[CAT], where [CAT] is the abbreviated category
22 the category is supported by the implementation.
24 - fsl,portid-mapping
|
| /Documentation/core-api/ |
| D | genericirq.rst | 7 :Copyright: |copy| 2005-2010: Thomas Gleixner
8 :Copyright: |copy| 2005-2006: Ingo Molnar
28 The original implementation of interrupt handling in Linux uses the
29 __do_IRQ() super-handler, which is able to deal with every type of
33 a quite universal set for the ARM interrupt handler implementation in
36 - Level type
38 - Edge type
40 - Simple type
42 During the implementation we identified another type:
44 - Fast EOI type
[all …]
|
| /Documentation/driver-api/rapidio/ |
| D | mport_cdev.rst | 17 for user-space applications. Most of RapidIO operations are supported through
24 Using available set of ioctl commands user-space applications can perform
27 - Reads and writes from/to configuration registers of mport devices
29 - Reads and writes from/to configuration registers of remote RapidIO devices.
30 This operations are defined as RapidIO Maintenance reads/writes in RIO spec.
32 - Set RapidIO Destination ID for mport devices (RIO_MPORT_MAINT_HDID_SET)
33 - Set RapidIO Component Tag for mport devices (RIO_MPORT_MAINT_COMPTAG_SET)
34 - Query logical index of mport devices (RIO_MPORT_MAINT_PORT_IDX_GET)
35 - Query capabilities and RapidIO link configuration of mport devices
37 - Enable/Disable reporting of RapidIO doorbell events to user-space applications
[all …]
|
| D | rio_cm.rst | 19 This driver (RIO_CM) provides to user-space applications shared access to
23 messaging mailboxes in case of multi-packet message (up to 4KB) and
24 up to 64 mailboxes if single-packet messages (up to 256 B) are used. In addition
25 to protocol definition limitations, a particular hardware implementation can
30 capability to large number of user-space processes by introducing socket-like
39 Following ioctl commands are available to user-space applications:
41 - RIO_CM_MPORT_GET_LIST:
46 - RIO_CM_EP_GET_LIST_SIZE:
49 - RIO_CM_EP_GET_LIST:
53 - RIO_CM_CHAN_CREATE:
[all …]
|
| /Documentation/livepatch/ |
| D | livepatch.rst | 15 5. Livepatch life-cycle
43 - The kernel probes are the most generic. The code can be redirected by
46 - The function tracer calls the code from a predefined location that is
48 compiler using the '-pg' gcc option.
50 - Livepatching typically needs to redirect the code at the very beginning
67 release locks, read, process, and even write some data in a defined way,
68 have return values. In other words, each function has a defined semantic.
87 The aim is to define a so-called consistency model. It attempts to define
88 conditions when the new implementation could be used so that the system
92 kpatch: it uses kGraft's per-task consistency and syscall barrier
[all …]
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-intro.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _cec-intro:
10 HDMI cable to communicate. The protocol for CEC version 1.4 is defined
13 extensions added to CEC version 2.0 are defined in chapter 11 of the
33 the `v4l-utils <https://git.linuxtv.org/v4l-utils.git/>`_ package. It
36 - cec-ctl: the Swiss army knife of CEC. Allows you to configure, transmit
39 - cec-compliance: does a CEC compliance test of a remote CEC device to
40 determine how compliant the CEC implementation is.
42 - cec-follower: emulates a CEC follower.
|
| /Documentation/driver-api/media/drivers/ |
| D | pvrusb2.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 ----------
13 Its history started with the reverse-engineering effort by Björn
29 1. Low level wire-protocol implementation with the device.
31 2. I2C adaptor implementation and corresponding I2C client drivers
34 3. High level hardware driver implementation which coordinates all
38 tear-down, arbitration, and interaction with high level
53 implementation and interface isolated from each other. Thus while
61 --------
70 --------------------------------------
[all …]
|
| /Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 27 Please check the I-D abstract listing contained in each Internet Draft
46 mandatory access controls and multi-level security. These systems are
57 defined in future RFCs.
88 once in a datagram. All multi-octet fields in the option are defined to be
91 +----------+----------+------//------+-----------//---------+
93 +----------+----------+------//------+-----------//---------+
124 corresponding ASCII representations. Non-related groups of systems may
148 actual security information to be passed. All multi-octet fields in a tag
149 are defined to be transmitted in network byte order. Like the DOI
152 octet boundary. The tag types defined in this document contain alignment
[all …]
|
| /Documentation/driver-api/mei/ |
| D | mei-client-bus.rst | 1 .. SPDX-License-Identifier: GPL-2.0
19 Existing device drivers can even potentially be re-used by adding an MEI CL bus layer to
26 A driver implementation for an MEI Client is very similar to any other existing bus
28 the ``struct mei_cl_driver`` structure defined in :file:`include/linux/mei_cl_bus.c`
30 .. code-block:: C
44 The mei_cl_device_id structure defined in :file:`include/linux/mod_devicetable.h` allows a
47 .. code-block:: C
70 ----
71 .. kernel-doc:: drivers/misc/mei/bus.c
82 .. code-block:: C
[all …]
|
| /Documentation/arm/ |
| D | vlocks.rst | 2 vlocks for Bare-Metal Mutual Exclusion
5 Voting Locks, or "vlocks" provide a simple low-level mutual exclusion
10 which are otherwise non-coherent, in situations where the hardware
28 ---------
30 The easiest way to explain the vlocks algorithm is with some pseudo-code::
34 int last_vote = -1; /* no votes yet */
40 if (last_vote != -1) {
64 last_vote = -1;
74 priority rule to act as a tie-breaker, or any counters which could
83 ------------------------
[all …]
|
| /Documentation/scheduler/ |
| D | sched-arch.rst | 2 CPU Scheduler implementation hints for architecture specific code
17 (typically the one where switch_to is defined).
20 penalty to the core scheduler implementation in the CONFIG_SMP case.
57 - 5a. If TIF_POLLING_NRFLAG is set, and we do decide to enter
71 ia64 - is safe_halt call racy vs interrupts? (does it sleep?) (See #4a)
73 sh64 - Is sleeping racy vs interrupts? (See #4a)
75 sparc - IRQs on at this point(?), change local_irq_save to _disable.
76 - TODO: needs secondary CPUs to disable preempt (See #1)
|
| /Documentation/filesystems/ |
| D | relay.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 to userspace via user-defined 'relay channels'.
11 A 'relay channel' is a kernel->user data relay mechanism implemented
12 as a set of per-cpu kernel buffers ('channel buffers'), each
25 filtering - this also is left to the kernel client. The purpose is to
30 functions in the relay interface code - please see that for details.
36 sub-buffers. Messages are written to the first sub-buffer until it is
38 the next (if available). Messages are never split across sub-buffers.
40 sub-buffer, while the kernel continues writing to the next.
42 When notified that a sub-buffer is full, the kernel knows how many
[all …]
|
| /Documentation/devicetree/bindings/display/bridge/ |
| D | tda998x.txt | 1 Device-Tree bindings for the NXP TDA998x HDMI transmitter
4 - compatible: must be "nxp,tda998x"
6 - reg: I2C address
9 - port: Input port node with endpoint definition, as described
13 - interrupts: interrupt number and trigger type
16 - pinctrl-0: pin control group to be used for
19 - pinctrl-names: must contain a "default" entry.
21 - video-ports: 24 bits value which defines how the video controller
22 output is wired to the TDA998x input - default: <0x230145>
24 - audio-ports: array of 8-bit values, 2 values per one DAI[1].
[all …]
|
12345678910