Searched +full:loss +full:- +full:of +full:- +full:signal (Results 1 – 25 of 28) sorted by relevance
12
| /Documentation/devicetree/bindings/phy/ |
| D | microchip,sparx5-serdes.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/phy/microchip,sparx5-serdes.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Steen Hegelund <steen.hegelund@microchip.com>
21 * Rx built-in fault detector (loss-of-lock/loss-of-signal)
22 * Adjustable tx de-emphasis (FFE)
31 The SERDES6G is a high-speed SERDES interface, which can operate at
34 * 100 Mbps (100BASE-FX)
35 * 1.25 Gbps (SGMII/1000BASE-X/1000BASE-KX)
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | sff,sfp.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Small Form Factor (SFF) Committee Small Form-factor Pluggable (SFP)
11 - Russell King <linux@armlinux.org.uk>
16 - sff,sfp # for SFP modules
17 - sff,sff # for soldered down SFF modules
19 i2c-bus:
22 phandle of an I2C bus controller for the SFP two wire serial
24 maximum-power-milliwatt:
[all …]
|
| D | ti,dp83822.yaml | 1 # SPDX-License-Identifier: (GPL-2.0+ OR BSD-2-Clause)
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Andrew Davis <afd@ti.com>
14 The DP83822 is a low-power, single-port, 10/100 Mbps Ethernet PHY. It
15 provides all of the physical layer functions needed to transmit and receive
16 data over standard, twisted-pair cables or to connect to an external,
17 fiber-optic transceiver. Additionally, the DP83822 provides flexibility to
24 - $ref: ethernet-phy.yaml#
30 ti,link-loss-low:
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | dev-event.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
11 include start of frame or loss of signal events, for example. Changes in
12 the value or state of a V4L2 control can also be reported through
18 an event is subscribed, the events of subscribed types are dequeueable
36 This means that flooding of one event type will not interfere with
42 3. Where applicable, certain event types can ensure that the payload of
44 payload of the next oldest event. Thus ensuring that no information
|
| D | vidioc-dqevent.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_DQEVENT - Dequeue event
35 ioctl. All the fields of the struct :c:type:`v4l2_event`
45 .. flat-table:: struct v4l2_event
46 :header-rows: 0
47 :stub-columns: 0
50 * - __u32
51 - ``type``
52 - Type of the event, see :ref:`event-type`.
53 * - union {
[all …]
|
| D | vidioc-qbuf.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_QBUF - VIDIOC_DQBUF - Exchange a buffer with the driver
42 To enqueue a buffer applications set the ``type`` field of a struct
47 range from zero to the number of buffers allocated with
50 one. The contents of the struct :c:type:`v4l2_buffer` returned
58 :ref:`multi-planar API <planar-apis>`, the ``m.planes`` field must
59 contain a userspace pointer to a filled-in array of struct
61 to the number of elements in that array.
72 the address of the buffer and ``length`` to its size. When the
73 multi-planar API is used, ``m.userptr`` and ``length`` members of the
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | dmx-qbuf.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 DMX_QBUF - DMX_DQBUF - Exchange a buffer with the driver
45 numbers range from zero to the number of buffers allocated with
47 one. The contents of the struct :c:type:`dmx_buffer` returned
51 memory pages of the buffer in physical memory, so they cannot be swapped
72 On success 0 is returned, on error -1 and the ``errno`` variable is set
74 :ref:`Generic Error Codes <gen-errors>` chapter.
77 Non-blocking I/O has been selected using ``O_NONBLOCK`` and no
81 The ``index`` is out of bounds, or no buffers have been allocated yet.
85 temporary problems like signal loss or CRC errors.
|
| /Documentation/scsi/ |
| D | libsas.rst | 1 .. SPDX-License-Identifier: GPL-2.0
32 Most of it is used by the SAS Layer but a few fields need to
47 ------------------
58 And then all the phys are an array of my_phy in your HA
75 - must be set (0/1)
78 - must be set [0,MAX_PHYS)]
81 - must be set
84 - you set this when OOB has finished and then notify
88 - this normally points to an array holding the sas
89 address of the phy, possibly somewhere in your my_phy
[all …]
|
| D | aic79xx.rst | 1 .. SPDX-License-Identifier: GPL-2.0
28 AIC-7901A Single Channel 64-bit PCI-X 133MHz to
30 AIC-7901B Single Channel 64-bit PCI-X 133MHz to
32 AIC-7902A4 Dual Channel 64-bit PCI-X 133MHz to
34 AIC-7902B Dual Channel 64-bit PCI-X 133MHz to
41 Adaptec SCSI Card 39320 Dual Channel 64-bit PCI-X 133MHz to 7902A4/7902B
43 68-pin, two internal 68-pin)
44 Adaptec SCSI Card 39320A Dual Channel 64-bit PCI-X 133MHz to 7902B
46 68-pin, two internal 68-pin)
47 Adaptec SCSI Card 39320D Dual Channel 64-bit PCI-X 133MHz to 7902A4
[all …]
|
| D | ChangeLog.lpfc | 2 * Please read the associated RELEASE-NOTES file !!!
8 * Fixed build warning for 2.6.12-rc2 kernels: mempool_alloc now
12 for fabric and nport logins out of lpfc_cmpl_els_flogi.
19 * Removed FC_TRANSPORT_PATCHESxxx defines. They're in 2.6.12-rc1.
20 * Compare return value of lpfc_scsi_tgt_reset against SCSI
26 * Added PCI ID for LP10000-S.
31 * Zero-out response sense length in lpfc_scsi_prep_cmnd to prevent
32 interpretation of stale sense length when the command completes
33 - was causing spurious 0710 messages.
34 * Moved clearing of host_scribble inside host_lock in IO
[all …]
|
| /Documentation/scheduler/ |
| D | sched-capacity.rst | 9 ----------------
11 Conventional, homogeneous SMP platforms are composed of purely identical
12 CPUs. Heterogeneous platforms on the other hand are composed of CPUs with
13 different performance characteristics - on such platforms, not all CPUs can be
16 CPU capacity is a measure of the performance a CPU can reach, normalized against
18 asymmetric CPU capacity systems, as they contain CPUs of different capacities.
23 - not all CPUs may have the same microarchitecture (µarch).
24 - with Dynamic Voltage and Frequency Scaling (DVFS), not all CPUs may be
27 Arm big.LITTLE systems are an example of both. The big CPUs are more
28 performance-oriented than the LITTLE ones (more pipeline stages, bigger caches,
[all …]
|
| /Documentation/networking/ |
| D | rds.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 This readme tries to provide some background on the hows and whys of RDS,
14 http://oss.oracle.com/pipermail/rds-devel/2007-November/000228.html
22 cluster - so in a cluster with N processes you need N sockets, in contrast
23 to N*N if you use a connection-oriented socket transport like TCP.
25 RDS is not Infiniband-specific; it was designed to support different
29 The high-level semantics of RDS from the application's point of view are
34 the end point of a connection. All socket operations that involve
39 transport has to be IP-based. In fact, RDS over IB uses a
43 The port space is entirely independent of UDP, TCP or any other
[all …]
|
| D | phy.rst | 8 Most network devices consist of set of registers which provide an interface
11 partner on the other side of the network connection (typically, an ethernet
18 amounts of redundant code. Also, on embedded systems with multiple (and
20 management bus, it is difficult to ensure safe use of the bus.
26 #. Increase code-reuse
27 #. Increase overall code-maintainability
37 Most network devices are connected to a PHY by means of a management bus.
39 In order to take advantage of the PAL, each bus interface needs to be
49 time, so it is safe for them to block, waiting for an interrupt to signal
57 mdiobus_register. Similarly, there's a remove function to undo all of
[all …]
|
| D | ip-sysctl.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 ip_forward - BOOLEAN
11 - 0 - disabled (default)
12 - not 0 - enabled
20 ip_default_ttl - INTEGER
21 Default value of TTL field (Time To Live) for outgoing (but not
25 ip_no_pmtu_disc - INTEGER
27 fragmentation-required ICMP is received, the PMTU to this
28 destination will be set to the smallest of the old MTU to
38 accept fragmentation-needed errors if the underlying protocol
[all …]
|
| D | packet_mmap.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 socket interface. This type of sockets is used for
22 - Ulisses Alonso Camaró <uaca@i.hate.spam.alumni.uv.es>
23 - Johann Baudy
36 most of the time there is no need to issue a single system call. Concerning
39 also has the benefit of minimizing packet copies.
41 It's fine to use PACKET_MMAP to improve the performance of the capture and
44 device driver of your network interface card supports some sort of interrupt
47 supported by devices of your network. CPU IRQ pinning of your network interface
57 Packet MMAP support was integrated into libpcap around the time of version 1.3.0;
[all …]
|
| D | ethtool-netlink.rst | 27 wake-on-lan password) omitted.
37 number 1 but any non-zero value should be understood as "true" by recipient.
41 with "+", parent nest can contain multiple attributes of the same type. This
42 implements an array of entries.
44 Attributes that need to be filled-in by device drivers and that are dumped to
46 valid value. This avoids the need to explicitly signal the validity of the
54 Structure of this header is
64 device message relates to. One of them is sufficient in requests, if both are
70 ``ETHTOOL_A_HEADER_FLAGS`` is a bitmap of request flags common for all request
71 types. The interpretation of these flags is the same for all request types but
[all …]
|
| /Documentation/networking/dsa/ |
| D | sja1105.rst | 8 The NXP SJA1105 is a family of 10 SPI-managed automotive switches:
10 - SJA1105E: First generation, no TTEthernet
11 - SJA1105T: First generation, TTEthernet
12 - SJA1105P: Second generation, no TTEthernet, no SGMII
13 - SJA1105Q: Second generation, TTEthernet, no SGMII
14 - SJA1105R: Second generation, no TTEthernet, SGMII
15 - SJA1105S: Second generation, TTEthernet, SGMII
16 - SJA1110A: Third generation, TTEthernet, SGMII, integrated 100base-T1 and
17 100base-TX PHYs
18 - SJA1110B: Third generation, TTEthernet, SGMII, 100base-T1, 100base-TX
[all …]
|
| /Documentation/sound/designs/ |
| D | compress-offload.rst | 2 ALSA Compress-Offload API
5 Pierre-Louis.Bossart <pierre-louis.bossart@linux.intel.com>
17 In recent years, audio digital signal processors (DSP) were integrated
18 in system-on-chip designs, and DSPs are also integrated in audio
20 reduction of power consumption compared to host-based
22 mostly because of a lack of a generic API available in the mainline
25 Rather than requiring a compatibility break with an API change of the
27 provide a control and data-streaming interface for audio DSPs.
29 The design of this API was inspired by the 2-year experience with the
31 API in the mainline kernel instead of the staging tree and make it
[all …]
|
| /Documentation/driver-api/pm/ |
| D | devices.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 :Copyright: |copy| 2010-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
17 Most of the code in Linux is device drivers, so most of the Linux power
18 management (PM) code is also driver-specific. Most drivers will do very
22 This writeup gives an overview of how drivers interact with system-wide
25 background for the domain-specific work you'd do with any specific driver.
31 Drivers will use one or both of these models to put devices into low-power
36 Drivers can enter low-power states as part of entering system-wide
37 low-power states like "suspend" (also known as "suspend-to-RAM"), or
39 "suspend-to-disk").
[all …]
|
| /Documentation/driver-api/gpio/ |
| D | consumer.rst | 5 This document describes the consumer interface of the GPIO framework.
21 - Simple compile coverage with e.g. COMPILE_TEST - it does not matter that
25 - Truly optional GPIOLIB support - where the driver does not really make use
26 of the GPIOs on certain compile-time configurations for certain systems, but
27 will use it under other compile-time configurations. In this case the
33 some open coding of error handling should be expected when you do this.
35 All the functions that work with the descriptor-based GPIO interface are
38 of the legacy functions is strongly discouraged, new code should use
45 With the descriptor-based interface, GPIOs are identified with an opaque,
46 non-forgeable handler that must be obtained through a call to one of the
[all …]
|
| /Documentation/driver-api/usb/ |
| D | power-management.rst | 1 .. _usb-power-management:
7 :Date: Last-updated: February 2014
11 ---------
15 * Forms of dynamic PM
17 * Changing the default idle-delay time
21 * Other parts of the driver interface
31 -------------------------
33 Power Management (PM) is the practice of saving energy by suspending
34 parts of a computer system when they aren't being used. While a
35 component is ``suspended`` it is in a nonfunctional low-power state; it
[all …]
|
| /Documentation/process/ |
| D | 2.Process.rst | 7 with relatively small numbers of users and developers involved. With a
9 course of one year, the kernel has since had to evolve a number of
10 processes to keep development happening smoothly. A solid understanding of
11 how the process works is required in order to be an effective part of it.
14 ---------------
16 The kernel developers use a loosely time-based release process, with a new
31 changesets with changes to several hundred thousand lines of code. 5.x is
32 the leading edge of Linux kernel development; the kernel uses a
36 merging of patches for each release. At the beginning of each development
39 community) is merged into the mainline kernel. The bulk of changes for a
[all …]
|
| /Documentation/cdrom/ |
| D | cdrom-standard.rst | 2 A Linux CD-ROM standard
14 Linux is probably the Unix-like operating system that supports
15 the widest variety of hardware devices. The reasons for this are
18 - The large list of hardware devices available for the many platforms
19 that Linux now supports (i.e., i386-PCs, Sparc Suns, etc.)
20 - The open design of the operating system, such that anybody can write a
22 - There is plenty of source code around as examples of how to write a driver.
24 The openness of Linux, and the many different types of available
27 all these different devices has also allowed the behavior of each
29 This divergence of behavior has been very significant for CD-ROM
[all …]
|
| /Documentation/filesystems/xfs/ |
| D | xfs-online-fsck-design.rst | 1 .. SPDX-License-Identifier: GPL-2.0
5 Mapping of heading styles within this document:
8 Heading 3 uses "----"
21 This document captures the design of the online filesystem check feature for
23 The purpose of this document is threefold:
25 - To help kernel distributors understand exactly what the XFS online fsck
28 - To help people reading the code to familiarize themselves with the relevant
31 - To help developers maintaining the system by capturing the reasons
37 This document is licensed under the terms of the GNU Public License, v2.
42 Parts 2 and 3 present a high level overview of how online fsck process works
[all …]
|
| /Documentation/filesystems/ |
| D | proc.rst | 1 .. SPDX-License-Identifier: GPL-2.0
17 .. Table of Contents
24 1.1 Process-Specific Subdirectories
36 3 Per-Process Parameters
37 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj - Adjust the oom-killer
39 3.2 /proc/<pid>/oom_score - Display current oom-killer score
40 3.3 /proc/<pid>/io - Display the IO accounting fields
41 3.4 /proc/<pid>/coredump_filter - Core dump filtering settings
42 3.5 /proc/<pid>/mountinfo - Information about mounts
44 3.7 /proc/<pid>/task/<tid>/children - Information about task children
[all …]
|
12