Home
last modified time | relevance | path

Searched full:interfaces (Results 1 – 25 of 709) sorted by relevance

12345678910>>...29

/Documentation/ABI/
DREADME2 userspace, and the relative stability of these interfaces. Due to the
4 interfaces should be used by userspace programs in different ways.
7 different subdirectories in this location. Interfaces may change levels
13 This directory documents the interfaces that the developer has
15 interfaces with no restrictions, and backward compatibility for
16 them will be guaranteed for at least 2 years. Most interfaces
21 This directory documents interfaces that are felt to be stable,
26 programs can start to rely on these interfaces, but they must be
27 aware of changes that can occur before these interfaces move to
28 be marked stable. Programs that use these interfaces are
[all …]
/Documentation/networking/
Dipv6.rst37 No IPv6 addresses will be added to interfaces, and
45 on all interfaces. This might be used when one does not wish
52 IPv6 address autoconfiguration is disabled on all interfaces.
55 will be added to interfaces.
58 IPv6 address autoconfiguration is enabled on all interfaces.
64 Specifies whether to disable IPv6 on all interfaces.
70 IPv6 is enabled on all interfaces.
75 IPv6 is disabled on all interfaces.
77 No IPv6 addresses will be added to interfaces.
Dtipc.rst145 TIPC Bearer Interfaces
154 TIPC Crypto Interfaces
160 TIPC Discoverer Interfaces
166 TIPC Link Interfaces
172 TIPC msg Interfaces
178 TIPC Name Interfaces
187 TIPC Node Management Interfaces
193 TIPC Socket Interfaces
199 TIPC Network Topology Interfaces
205 TIPC Server Interfaces
[all …]
D6lowpan.rst4 Netdev private dataroom for 6lowpan interfaces
7 All 6lowpan able net devices, means all interfaces with ARPHRD_6LOWPAN,
53 by ARPHRD_6LOWPAN interfaces.
/Documentation/admin-guide/
Dabi-testing.rst4 Documents interfaces that are felt to be stable,
11 Userspace programs can start to rely on these interfaces, but they must
12 be aware of changes that can occur before these interfaces move to
15 Programs that use these interfaces are strongly encouraged to add their
16 name to the description of these interfaces, so that the kernel
Dabi-stable.rst4 Documents the interfaces that the developer has defined to be stable.
6 Userspace programs are free to use these interfaces with no
10 Most interfaces (like syscalls) are expected to never change and always
/Documentation/scsi/
Dbnx2fc.rst7 cooperates with all interfaces provided by the Linux ecosystem for FC/FCoE and
13 depend on the state of the network interfaces to operate. As such, the network
15 It is recommended that the network interfaces be configured to be brought up
18 Furthermore, the Broadcom FCoE offload solution creates VLAN interfaces to
20 eth0.1001-fcoe). Do not delete or disable these interfaces or FCoE operation
28 2. Configure the interfaces on which bnx2fc driver has to operate on.
33 c. Repeat this for all the interfaces where FCoE has to be enabled.
41 the system, bnx2fc driver would automatically claim the interfaces, starts vlan
69 <INTERFACE>.<VLAN>-fcoe interfaces are automatically created.
72 create/destroy interfaces or to display lun/target information.
/Documentation/driver-api/
Dfirewire.rst8 The Linux FireWire subsystem adds some interfaces into the Linux system to
11 The main purpose of these interfaces is to access address space on each node
15 Two types of interfaces are added, according to consumers of the interface. A
16 set of userspace interfaces is available via `firewire character devices`. A set
17 of kernel interfaces is available via exported symbols in `firewire-core` module.
28 Firewire device probing and sysfs interfaces
37 Firewire core transaction interfaces
43 Firewire Isochronous I/O interfaces
Dtarget.rst2 target and iSCSI Interfaces Guide
10 Target core device interfaces
16 Target core transport interfaces
44 iSCSI TCP interfaces
Ds390-drivers.rst10 This document describes the interfaces available for device drivers that
11 drive s390 based channel attached I/O devices. This includes interfaces
12 for interaction with the hardware and interfaces for interacting with
13 the common driver core. Those interfaces are provided by the s390 common
121 Generic interfaces
124 The following section contains interfaces in use not only by drivers
Dipmi.rst35 The message handler does not provide any user-level interfaces.
98 IPMI users tie into this, and the IPMI physical interfaces (called
99 System Management Interfaces, or SMIs) also tie in here. This
107 ipmi_si - A driver for various system interfaces. This supports KCS,
108 SMIC, and BT interfaces. Unless you have an SMBus interface or your
112 I2C kernel driver's SMBus interfaces to send and receive IPMI messages
135 linux/ipmi_smi.h - Contains the interface for system management interfaces
261 view of the IPMI interfaces. It allows multiple SMI interfaces to be
266 Watching For Interfaces
273 watcher with ipmi_smi_watcher_register() to iterate over interfaces
[all …]
/Documentation/process/
Dstable-api-nonsense.rst15 Please realize that this article describes the **in kernel** interfaces, not
16 the kernel to userspace interfaces.
41 to worry about the in-kernel interfaces changing. For the majority of
53 So, there are two main topics here, binary kernel interfaces and stable
54 kernel source interfaces. They both depend on each other, but we will
101 Stable Kernel Source Interfaces
110 current interfaces, or figure out a better way to do things. If they do
111 that, they then fix the current interfaces to work better. When they do
117 As a specific examples of this, the in-kernel USB interfaces have
132 which have had to maintain their older USB interfaces over time. This
[all …]
/Documentation/devicetree/bindings/phy/
Dmicrochip,lan966x-serdes.yaml13 Lan966x has 7 interfaces, consisting of 2 copper transceivers(CU),
14 3 SERDES6G and 2 RGMII interfaces. Two of the SERDES6G support QSGMII.
16 interfaces. The Serdes controller will allow to configure these interfaces
17 and allows to "mux" the interfaces to different ports.
/Documentation/usb/
Dauthorization.rst12 its interfaces are immediately made available to the users. With this
98 There is a similar approach to allow or deny specific USB interfaces.
109 The default value for new interfaces
112 Allow interfaces per default::
116 Deny interfaces per default::
121 So all interfaces would authorized per default.
127 For drivers that need multiple interfaces all needed interfaces should be
/Documentation/devicetree/bindings/media/i2c/
Dmipi-ccs.yaml24 Documentation/devicetree/bindings/media/video-interfaces.txt .
62 description: Flash LED phandles. See ../video-interfaces.txt for details.
65 description: Lens focus controller phandles. See ../video-interfaces.txt
69 description: Rotation of the sensor. See ../video-interfaces.txt for
79 $ref: /schemas/media/video-interfaces.yaml#
107 #include <dt-bindings/media/video-interfaces.h>
Dtoshiba,et8ek8.txt6 Documentation/devicetree/bindings/media/video-interfaces.txt .
26 - flash-leds: See ../video-interfaces.txt
27 - lens-focus: See ../video-interfaces.txt
Dmt9m111.txt15 Documentation/devicetree/bindings/media/video-interfaces.txt
18 - pclk-sample: For information see ../video-interfaces.txt. The value is set to
/Documentation/networking/dsa/
Dbcm_sf2.rst13 ports, offering a range of built-in and customizable interfaces:
19 - several external MII/RevMII/GMII/RGMII interfaces
23 band back-pressure to the host CPU network interface when downstream interfaces
30 - ``SWITCH_REG``: external interfaces switch register
79 Multimedia over CoAxial (MoCA) interfaces
82 MoCA interfaces are fairly specific and require the use of a firmware blob which
89 The MoCA interfaces are supported using the PHY library's fixed PHY/emulated PHY
Dconfiguration.rst35 All other corresponding linux interfaces are called user interfaces.
37 The user interfaces depend on the conduit interface being up in order for them
44 - when the conduit interface is brought down, all DSA user interfaces are
47 In this documentation the following Ethernet interfaces are used:
67 Further Ethernet interfaces can be configured similar.
103 # bring up the user interfaces
115 # bring up the user interfaces
141 # bring up the user interfaces
188 # bring up the user interfaces
229 # bring up the user interfaces
[all …]
/Documentation/ABI/stable/
Dsysfs-class-backlight51 interfaces are available for a single device, firmware
56 backlight state. Platform interfaces are mostly a
58 interfaces.
/Documentation/
Dsubsystem-apis.rst27 Human interfaces
40 Networking interfaces
52 Storage interfaces
/Documentation/driver-api/firmware/
Dother_interfaces.rst1 Other Firmware Interfaces
4 DMI Interfaces
10 EDD Interfaces
/Documentation/devicetree/bindings/net/
Dapm-xgene-enet.txt3 Ethernet nodes are defined to describe on-chip ethernet interfaces in
6 Required properties for all the ethernet interfaces:
20 This is supported only on SGMII based 1GbE and 10GbE interfaces.
28 Required properties for ethernet interfaces that have external PHY:
/Documentation/driver-api/media/drivers/
Dpvrusb2.rst39 interfaces appropriately as devices are hotplugged in the
42 5. High level interfaces which glue the driver to various published
84 interfaces tie into the driver through this module. This module
87 instances of multiple interfaces (thus you can for example change
117 interfaces (e.g. V4L, sysfs, etc), and in fact even those high
118 level interfaces are restricted to the API defined in
122 controlling the hardware. High level interfaces (e.g. V4L, sysfs)
158 through one of the high level interfaces).
/Documentation/devicetree/bindings/sound/
Dfsl,audmix.yaml16 audio interfaces. These are driven by two Synchronous Audio interface
19 from two interfaces into a single sample. Before mixing, audio samples of
21 Audio Mixer is also a serial audio interface. Like input interfaces it has

12345678910>>...29