| /linux/Documentation/driver-api/ |
| H A D | firewire.rst | 8 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 D | target.rst | 10 Target core device interfaces
16 Target core transport interfaces
44 iSCSI TCP interfaces
|
| H A D | s390-drivers.rst | 10 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
|
| /linux/Documentation/networking/ |
| H A D | ipv6.rst | 37 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.
|
| H A D | 6lowpan.rst | 4 Netdev private dataroom for 6lowpan interfaces
7 All 6lowpan able net devices, means all interfaces with ARPHRD_6LOWPAN,
53 by ARPHRD_6LOWPAN interfaces.
|
| H A D | proc_net_tcp.rst | 7 This document describes the interfaces /proc/net/tcp and /proc/net/tcp6.
8 Note that these interfaces are deprecated in favor of tcp_diag.
10 These /proc interfaces provide information about currently active TCP
|
| H A D | batman-adv.rst | 29 The module is now waiting for activation. You must add some interfaces on which
39 Repeat this step for all interfaces you wish to add. Now batman-adv starts
84 interface "bat0" which you should use from this point on. All interfaces added
101 interfaces now used by batman advanced, e.g.::
147 and interfaces to the kernel module settings.
|
| /linux/Documentation/scsi/ |
| H A D | bnx2fc.rst | 7 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/drivers/greybus/ |
| H A D | module.c | 30 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()
210 gb_module_register_interface(module->interfaces[i]); in gb_module_add()
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/i2c/algos/ |
| H A D | Kconfig | 10 tristate "I2C bit-banging interfaces"
13 tristate "I2C PCF 8584 interfaces"
16 tristate "I2C PCA 9564 interfaces"
|
| /linux/Documentation/usb/ |
| H A D | authorization.rst | 12 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/Documentation/process/ |
| H A D | stable-api-nonsense.rst | 15 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
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
134 interfaces and do things in improper ways, causing the stability of the
[all …]
|
| /linux/Documentation/networking/dsa/ |
| H A D | bcm_sf2.rst | 13 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 D | configuration.rst | 35 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/Documentation/gpu/imagination/ |
| H A D | uapi.rst | 75 :doc: PowerVR IOCTL CREATE_VM_CONTEXT and DESTROY_VM_CONTEXT interfaces
84 :doc: PowerVR IOCTL VM_MAP and VM_UNMAP interfaces
93 :doc: PowerVR IOCTL CREATE_CONTEXT and DESTROY_CONTEXT interfaces
112 :doc: PowerVR IOCTL CREATE_FREE_LIST and DESTROY_FREE_LIST interfaces
123 :doc: PowerVR IOCTL CREATE_HWRT_DATASET and DESTROY_HWRT_DATASET interfaces
|
| /linux/net/mac802154/ |
| H A D | util.c | 33 list_for_each_entry_rcu(sdata, &local->interfaces, list) { in ieee802154_wake_queue()
58 list_for_each_entry_rcu(sdata, &local->interfaces, list) { in ieee802154_stop_queue()
92 list_for_each_entry_rcu(sdata, &local->interfaces, list) { in ieee802154_disable_queue()
|
| /linux/Documentation/driver-api/media/drivers/ |
| H A D | pvrusb2.rst | 39 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/Documentation/firmware-guide/acpi/dsd/ |
| H A D | leds.rst | 14 Referring to LEDs in Device tree is documented in [video-interfaces], in
102 [video-interfaces] Documentation/devicetree/bindings/media/video-interfaces.yaml
|
| /linux/Documentation/hwmon/ |
| H A D | emc2305.rst | 23 The driver provides the following sysfs interfaces in hwmon subsystem:
31 sysfs interfaces in thermal subsystem:
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | net.rst | 19 In order to create the Linux virtual network interfaces, an application
23 virtual ``dvb?_?`` network interfaces, and will be controlled/routed via
|
| /linux/net/8021q/ |
| H A D | Kconfig | 9 Select this and you will be able to create 802.1Q VLAN interfaces
10 on your Ethernet interfaces. 802.1Q VLAN supports almost
|
| /linux/drivers/infiniband/sw/rxe/ |
| H A D | Kconfig | 17 The driver is split into two layers, one interfaces with the
21 space verbs API, libibverbs. The other layer interfaces
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | dv-timings.rst | 12 hardware interfaces such as High Definition TV interfaces (HDMI), VGA,
14 extend the API to select the video timings for these interfaces. Since
|
| /linux/Documentation/admin-guide/aoe/ |
| H A D | aoe.rst | 51 "echo eth2 eth4 > /dev/etherd/interfaces" tells the aoe driver to
112 option discussed below) instead of /dev/etherd/interfaces to limit
113 AoE traffic to the network interfaces in the given
118 interfaces. The aoetools package provides an aoe-discover script
127 all network interfaces may be used for ATA over Ethernet. Here is a
|
| /linux/Documentation/admin-guide/media/ |
| H A D | qcom_camss.rst | 17 The driver implements V4L2, Media controller and V4L2 subdev interfaces.
39 hardware blocks. The VFE has different input interfaces. The PIX (Pixel) input
42 RDI (Raw Dump Interface) input interfaces bypass the image processing
119 the number of the input interfaces (3 RDI and 1 PIX for each VFE).
126 to use the input interfaces concurrently and independently as this is
|