Home
last modified time | relevance | path

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

12345678910>>...61

/linux/Documentation/ABI/
H A 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 …]
/linux/Documentation/networking/
H A 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.
/linux/Documentation/process/
H A 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 …]
/linux/Documentation/scsi/
H A 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.
/linux/Documentation/driver-api/
H A 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
H A 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 …]
H A 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
H A Dtarget.rst2 target and iSCSI Interfaces Guide
10 Target core device interfaces
16 Target core transport interfaces
44 iSCSI TCP interfaces
/linux/drivers/net/phy/
H A Dsfp-bus.c142 * @interfaces: pointer to an array of unsigned long for phy interface modes
149 unsigned long *support, unsigned long *interfaces) in sfp_parse_support() argument
178 __set_bit(PHY_INTERFACE_MODE_10GBASER, interfaces); in sfp_parse_support()
182 __set_bit(PHY_INTERFACE_MODE_10GBASER, interfaces); in sfp_parse_support()
186 __set_bit(PHY_INTERFACE_MODE_10GBASER, interfaces); in sfp_parse_support()
190 __set_bit(PHY_INTERFACE_MODE_10GBASER, interfaces); in sfp_parse_support()
196 __set_bit(PHY_INTERFACE_MODE_1000BASEX, interfaces); in sfp_parse_support()
201 __set_bit(PHY_INTERFACE_MODE_1000BASEX, interfaces); in sfp_parse_support()
202 __set_bit(PHY_INTERFACE_MODE_SGMII, interfaces); in sfp_parse_support()
209 __set_bit(PHY_INTERFACE_MODE_1000BASEX, interfaces); in sfp_parse_support()
[all …]
/linux/Documentation/admin-guide/
H A 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
/linux/Documentation/usb/
H A 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
/linux/drivers/greybus/
H A Dmodule.c30 intf = module->interfaces[i]; in eject_store()
96 module = kzalloc(struct_size(module, interfaces, num_interfaces), in gb_module_create()
122 module->interfaces[i] = intf; in gb_module_create()
129 gb_interface_put(module->interfaces[i]); in gb_module_create()
195 /* Register a module and its interfaces. */
210 gb_module_register_interface(module->interfaces[i]); in gb_module_add()
215 /* Deregister a module and its interfaces. */
221 gb_module_deregister_interface(module->interfaces[i]); in gb_module_del()
233 gb_interface_put(module->interfaces[i]); in gb_module_put()
/linux/drivers/net/can/usb/
H A DKconfig2 menu "CAN USB interfaces"
18 tristate "esd electronics gmbh CAN/USB interfaces"
20 This driver adds support for several CAN/USB interfaces
32 tristate "ETAS ES58X CAN/USB interfaces"
36 This driver supports the ES581.4, ES582.1 and ES584.1 interfaces
55 tristate "Geschwister Schneider UG and candleLight compatible interfaces"
61 interfaces.
137 tristate "PEAK PCAN-USB/USB Pro interfaces for CAN 2.0b/CAN-FD"
/linux/include/acpi/
H A Dacpixf.h4 * Name: acpixf.h - External interfaces to the ACPI subsystem
55 * These macros configure the various ACPICA interfaces. They are
274 * Interfaces that are configured out of the ACPICA build are replaced
282 * All ACPICA hardware-related interfaces that use these macros will be
324 * All interfaces related to error and warning messages
341 * All interfaces related to debug output messages
358 * All interfaces used by application will be configured
375 * All interfaces used by debugger will be configured
419 * Miscellaneous global interfaces
454 * ACPI table load/unload interfaces
[all...]
/linux/Documentation/devicetree/bindings/phy/
H A 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.
/linux/Documentation/devicetree/bindings/media/i2c/
H A 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>
/linux/Documentation/networking/dsa/
H A 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
H A 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 …]
/linux/drivers/clk/zynqmp/
H A Dpll.c15 * @hw: Handle between common and hardware-specific interfaces
45 * @hw: Handle between common and hardware-specific interfaces
69 * @hw: Handle between common and hardware-specific interfaces
95 * @hw: Handle between common and hardware-specific interfaces
128 * @hw: Handle between common and hardware-specific interfaces
169 * @hw: Handle between common and hardware-specific interfaces
221 * @hw: Handle between common and hardware-specific interfaces
245 * @hw: Handle between common and hardware-specific interfaces
275 * @hw: Handle between common and hardware-specific interfaces
/linux/drivers/net/ethernet/freescale/dpaa2/
H A Ddpsw.h59 * interfaces present in each of them can be configured using
64 * interfaces present in each of them can be configured using
77 * interfaces present in each of them can be configured using
144 * @num_ifs: Number of interfaces
439 * struct dpsw_vlan_if_cfg - Set of VLAN Interfaces
440 * @num_ifs: The number of interfaces that are assigned to the egress
442 * @if_id: The set of interfaces that are
445 * @fdb_id: FDB id to be used by this VLAN on these specific interfaces
506 * @if_info: unicast - egress interface, multicast - number of egress interfaces
523 * @num_ifs: Number of external and internal interfaces
[all …]
/linux/Documentation/security/
H A Dsnp-tdx-threat-model.rst18 interfaces (USB, thunderbolt). The goal of this document is to explain
53 The basic CoCo guest layout includes the host, guest, the interfaces that
64 communication channels or interfaces between the CoCo security manager and
70 | Interfaces | | CoCo security manager |
91 | External attack | | Interfaces |
104 "Interfaces" box represents the various interfaces that allow
115 interfaces (e.g. USB, Thunderbolt), and the ability to modify the contents
144 | External attack | | | Interfaces | |
152 | | | Interfaces |
193 explicit (not side-channel) interfaces include accesses to port I/O, MMIO
[all …]
/linux/Documentation/driver-api/media/drivers/
H A 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).
/linux/drivers/i2c/algos/
H A DKconfig10 tristate "I2C bit-banging interfaces"
13 tristate "I2C PCF 8584 interfaces"
16 tristate "I2C PCA 9564 interfaces"
/linux/drivers/clk/zynq/
H A Dpll.c16 * @hw: Handle between common and hardware-specific interfaces
46 * @hw: Handle between common and hardware-specific interfaces
67 * @hw: Handle between common and hardware-specific interfaces
89 * @hw: Handle between common and hardware-specific interfaces
112 * @hw: Handle between common and hardware-specific interfaces
142 * @hw: Handle between common and hardware-specific interfaces
/linux/arch/mips/include/asm/octeon/
H A Dcvmx-helper.h74 * This function enables the IPD and also enables the packet interfaces.
75 * The packet interfaces (RGMII and SPI) must be enabled after the
109 * Return the number of interfaces the chip has. Each interface
110 * may have multiple ports. Most chips support two interfaces,
114 * Returns Number of interfaces on chip
125 * Returns Mode of the interface. Unknown or unsupported interfaces return

12345678910>>...61