Home
last modified time | relevance | path

Searched refs:interfaces (Results 1 – 200 of 448) sorted by relevance

123

/linux-4.4.14/arch/cris/arch-v10/kernel/
Dio_interface_mux.c121 static struct interface interfaces[] = { variable
618 if (interfaces[ioif].used) { in cris_request_io_interface()
621 interfaces[ioif].name, in cris_request_io_interface()
623 interfaces[ioif].owner); in cris_request_io_interface()
630 group_set = interfaces[ioif].groups; in cris_request_io_interface()
636 if_group_use = interfaces[ioif].group_a; in cris_request_io_interface()
639 if_group_use = interfaces[ioif].group_b; in cris_request_io_interface()
642 if_group_use = interfaces[ioif].group_c; in cris_request_io_interface()
645 if_group_use = interfaces[ioif].group_d; in cris_request_io_interface()
648 if_group_use = interfaces[ioif].group_e; in cris_request_io_interface()
[all …]
/linux-4.4.14/Documentation/networking/
Dipv6.txt31 No IPv6 addresses will be added to interfaces, and
39 on all interfaces. This might be used when one does not wish
46 IPv6 address autoconfiguration is disabled on all interfaces.
49 will be added to interfaces.
52 IPv6 address autoconfiguration is enabled on all interfaces.
58 Specifies whether to disable IPv6 on all interfaces.
64 IPv6 is enabled on all interfaces.
69 IPv6 is disabled on all interfaces.
71 No IPv6 addresses will be added to interfaces.
D6lowpan.txt2 Netdev private dataroom for 6lowpan interfaces:
4 All 6lowpan able net devices, means all interfaces with ARPHRD_6LOWPAN,
50 by ARPHRD_6LOWPAN interfaces.
Dproc_net_tcp.txt1 This document describes the interfaces /proc/net/tcp and /proc/net/tcp6.
2 Note that these interfaces are deprecated in favor of tcp_diag.
4 These /proc interfaces provide information about currently active TCP
Dbatman-adv.txt30 batman advanced will scan your systems interfaces to search for
31 compatible interfaces. Once found, it will create subfolders in
38 ably is not supported. Not supported interfaces are: loopback,
39 non-ethernet and batman's own interfaces.
42 new interfaces to verify the compatibility. There is no need to
51 Repeat this step for all interfaces you wish to add. Now batman
109 All interfaces added to batman advanced are not relevant any
123 ously assigned to interfaces now used by batman advanced, e.g.
183 interfaces to the kernel module settings.
Dvrf.txt18 example network namespaces provide separation of network interfaces at L1
19 (Layer 1 separation), VLANs on the interfaces within a namespace provide
24 A VRF device is created with an associated route table. Network interfaces
70 3. Enslave L3 interfaces to a VRF device.
157 Network interfaces are assigned to a VRF by enslaving the netdevice to a
208 To show addresses for interfaces associated with a VRF add the master
292 Network interfaces are removed from a VRF by breaking the enslavement to
348 Interface addresses from /etc/network/interfaces:
Dfore200e.txt13 same time, by hosts that have several bus interfaces (such as PCI+SBUS,
17 for other bus interfaces such as EISA should not be too hard to add.
Dbonding.txt22 multiple network interfaces into a single logical "bonded" interface.
23 The behavior of the bonded interfaces depends upon the mode; generally
569 interface and each VLAN interfaces configured above
572 interfaces are tagged with the appropriate VLAN id.
592 interfaces. This mode provides fault tolerance.
909 striped across two interfaces. This may result in out
973 network initialization scripts: initscripts, sysconfig or interfaces.
978 distros using versions of initscripts, sysconfig and interfaces with full
984 initscripts or interfaces, or don't know if it's new enough, have no fear.
987 First, look for a file called interfaces in /etc/network directory.
[all …]
De100.txt156 (non-partitioned switch) behave as expected. All Ethernet interfaces
160 If you have multiple interfaces in a server, either turn on ARP
166 (2) installing the interfaces in separate broadcast domains (either
Dgianfar.txt42 open interfaces. See ethtool documentation for details.
Dbaycom.txt81 but they are now true kernel network interfaces. Installation is therefore
82 simple. Once installed, four interfaces named bc{sf,sh,p,e}[0-3] are available.
144 interface at a time. The serial driver grabs all interfaces it can find at
Dgeneric-hdlc.txt8 interfaces can share a single PVC.
53 if the card has software-selectable interfaces
Dcdc_mbim.txt59 The driver <-> userspace interfaces are described below. The MBIM
98 configuration descriptor kernel interfaces described in [6] or [7].
179 kernel interfaces, either ioctl or netlink.
229 are expected to use the tools and programming interfaces required by
Doperstates.txt50 Unused in current kernel (notpresent interfaces normally disappear),
114 otherwise. Kernel can recognise stacked interfaces because their
/linux-4.4.14/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.
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
30 these interfaces, so that the kernel developers can easily
[all …]
/linux-4.4.14/Documentation/scsi/
Dbnx2fc.txt4 cooperates with all interfaces provided by the Linux ecosystem for FC/FCoE and
10 depend on the state of the network interfaces to operate. As such, the network
12 It is recommended that the network interfaces be configured to be brought up
15 Furthermore, the Broadcom FCoE offload solution creates VLAN interfaces to
17 eth0.1001-fcoe). Do not delete or disable these interfaces or FCoE operation
25 2. Configure the interfaces on which bnx2fc driver has to operate on.
29 c. Repeat this for all the interfaces where FCoE has to be enabled.
37 the system, bnx2fc driver would automatically claim the interfaces, starts vlan
63 <INTERFACE>.<VLAN>-fcoe interfaces are automatically created.
66 create/destroy interfaces or to display lun/target information.
Dlpfc.txt62 By default, the driver expects the patches for block/unblock interfaces
69 at the top of this file). It relies on interfaces that are slowing
/linux-4.4.14/drivers/i2c/algos/
DKconfig9 tristate "I2C bit-banging interfaces"
12 tristate "I2C PCF 8584 interfaces"
15 tristate "I2C PCA 9564 interfaces"
/linux-4.4.14/Documentation/usb/
Dauthorization.txt11 its interfaces are immediately made available to the users. With this
96 There is a similar approach to allow or deny specific USB interfaces.
105 The default value for new interfaces
108 Allow interfaces per default:
111 Deny interfaces per default:
115 So all interfaces would authorized per default.
121 For drivers that need multiple interfaces all needed interfaces should be
Dfunctionfs.txt16 to worry about endpoints, interfaces or strings numbers but
39 One can imagine a gadget that has an Ethernet, MTP and HID interfaces
Dpower-management.txt314 (although the interfaces will be in the same altsettings as
333 USB drivers are bound to interfaces, so their suspend and resume
334 methods get called when the interfaces are suspended or resumed. In
335 principle one might want to suspend some interfaces on a device (i.e.,
337 suspending the other interfaces. The USB core doesn't allow this; all
338 interfaces are suspended when the device itself is suspended and all
339 interfaces are resumed when the device is resumed. It isn't possible
340 to suspend or resume some but not all of a device's interfaces. The
341 closest you can come is to unbind the interfaces' drivers.
351 USB core whenever one of its interfaces becomes busy or idle. The
Dhotplug.txt72 alternate interfaces that complicate driver selection. By design, USB
118 frameworks connect using interfaces layered over USB, and so they won't
/linux-4.4.14/Documentation/devicetree/bindings/media/
Dsamsung-s5k6a3.txt4 S5K6A3(YX) is a raw image sensor with MIPI CSI-2 and CCP2 image data interfaces
26 The common video interfaces bindings (see video-interfaces.txt) should be
33 video-interfaces.txt. The sensor supports only one data lane.
Dsamsung-s5c73m3.txt7 slave device nodes corresponding to these control bus interfaces are required
36 The common video interfaces bindings (see video-interfaces.txt) should be used
49 video-interfaces.txt. This sensor doesn't support data lane remapping
Dsamsung-s5k5baf.txt28 media/video-interfaces.txt. The following are properties specific to those
35 video-interfaces.txt. If present it should be <1> - the device
Drcar_vin.txt24 as described in video-interfaces.txt[1]. Only the first one will
88 [1] video-interfaces.txt common video media interface
Dexynos4-fimc-is.txt49 interfaces bindings, defined in video-interfaces.txt.
Dpxa-camera.txt7 - any required generic properties defined in video-interfaces.txt
Datmel-isi.txt14 defined in Documentation/devicetree/bindings/media/video-interfaces.txt.
Dti-am437x-vpfe.txt22 defined in Documentation/devicetree/bindings/media/video-interfaces.txt.
Dti,omap3isp.txt30 video-interfaces.txt in the same directory.
Dsamsung-mipi-csis.txt31 media/video-interfaces.txt. The following are properties specific to those nodes.
Dsamsung-fimc.txt110 using the common video interfaces bindings, defined in video-interfaces.txt.
/linux-4.4.14/Documentation/
Dstable_api_nonsense.txt8 realize that this article describes the _in kernel_ interfaces, not the
9 kernel to userspace interfaces. The kernel to userspace interface is
32 to worry about the in-kernel interfaces changing. For the majority of
44 So, there are two main topics here, binary kernel interfaces and stable
45 kernel source interfaces. They both depend on each other, but we will
97 current interfaces, or figure out a better way to do things. If they do
98 that, they then fix the current interfaces to work better. When they do
104 As a specific examples of this, the in-kernel USB interfaces have
118 which have had to maintain their older USB interfaces over time. This
120 interfaces and do things in improper ways, causing the stability of the
[all …]
DIPMI.txt36 The message handler does not provide any user-level interfaces.
97 IPMI users tie into this, and the IPMI physical interfaces (called
106 ipmi_si - A driver for various system interfaces. This supports KCS,
107 SMIC, and BT interfaces. Unless you have an SMBus interface or your
111 I2C kernel driver's SMBus interfaces to send and receive IPMI messages
134 linux/ipmi_smi.h - Contains the interface for system management interfaces
243 view of the IPMI interfaces. It allows multiple SMI interfaces to be
342 As mentioned before, multiple SMI interfaces may be registered to the
348 The ipmi_smi.h defines the interface for management interfaces, see
355 The SI driver allows up to 4 KCS or SMIC interfaces to be configured
[all …]
Dcachetlb.txt6 This document describes the cache/tlb flushing interfaces called
22 First, the TLB flushing interfaces, since they are the simplest. The
113 Next, we have the cache flushing interfaces. In general, when Linux
141 implement these interfaces since the caches are fully synchronized
220 Here in these two interfaces we are flushing a specific range
230 require a whole different set of interfaces to handle properly.
312 This allows these interfaces to be implemented much more
DSubmitChecklist74 19: All new userspace interfaces are documented in Documentation/ABI/.
76 Patches that change userspace interfaces should be CCed to
Ddma-buf-sharing.txt288 There are also atomic variants of these interfaces. Like for kmap they
341 - supporting existing mmap interfaces in importers.
356 No special interfaces, userspace simply calls mmap on the dma-buf fd.
358 2. Supporting existing mmap interfaces in importers
361 the userspace code of a given importing subsystem can use the same interfaces
367 The assumption in the current dma-buf interfaces is that redirecting the
372 adding interfaces to intercept pagefaults and allow pte shootdowns would
464 [2] All interfaces mentioned above defined in include/linux/dma-buf.h
Datomic_ops.txt8 interfaces properly.
41 As with all of the atomic_ interfaces, replace the leading "atomic_"
178 Now, we move onto the atomic operation interfaces typically implemented with
291 operation which does not return a value, a set of interfaces are
440 semantics required of these interfaces.
456 paths using these interfaces, so on 64-bit if the bit is set in the
491 semantics), two interfaces are provided:
528 They have names similar to the above bitmask operation interfaces,
/linux-4.4.14/Documentation/networking/dsa/
Dbcm_sf2.txt12 ports, offering a range of built-in and customizable interfaces:
18 - several external MII/RevMII/GMII/RGMII interfaces
22 band back-pressure to the host CPU network interface when downstream interfaces
29 * SWITCH_REG: external interfaces switch register
78 Multimedia over CoAxial (MoCA) interfaces
81 MoCA interfaces are fairly specific and require the use of a firmware blob which
88 The MoCA interfaces are supported using the PHY library's fixed PHY/emulated PHY
Ddsa.txt40 stack. These specialized network interfaces are referred to as "slave" network
41 interfaces in DSA terminology and code.
56 Note that DSA does not currently create network interfaces for the "cpu" and
61 would get two interfaces for the same conduit: master netdev, and "cpu" netdev
64 cannot really be used as proper network interfaces either, only the
144 device, each of these network interfaces will be responsible for being a
146 These interfaces are specialized in order to:
266 can make it harder to debug MDIO switch connected using xMII interfaces
386 configure the switch to separate all network interfaces from each other, that
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-class-backlight49 interfaces are available for a single device, firmware
54 backlight state. Platform interfaces are mostly a
56 interfaces.
Dsyscalls4 on it and other Unix based interfaces. It will only be added to
Dsysfs-firmware-opal-dump5 This directory exposes interfaces for interacting with
Dsysfs-firmware-efi-vars5 This directory exposes interfaces for interactive with
/linux-4.4.14/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.
26 Required properties for ethernet interfaces that have external PHY:
Dcavium-pip.txt5 several interfaces, and each interface may have several ports. These
20 Properties for PIP interfaces which is a child the PIP nexus:
Dkeystone-netcp.txt94 - interfaces: specification for each of the switch port to be registered as a
171 interfaces {
195 netcp-interfaces {
Dbrcm,bcm7445-switch-v4.0.txt30 - brcm,num-rgmii-ports: specify the maximum number of RGMII interfaces supported
/linux-4.4.14/Documentation/devicetree/bindings/display/bridge/
Dps8622.txt12 - video interfaces: Device node can contain video interface port
15 [1]: Documentation/devicetree/bindings/media/video-interfaces.txt
Dptn3460.txt20 - video interfaces: Device node can contain video interface port
23 [1]: Documentation/devicetree/bindings/media/video-interfaces.txt
Ddw_hdmi.txt15 in Documentation/devicetree/bindings/media/video-interfaces.txt,
/linux-4.4.14/net/mac802154/
Dutil.c28 list_for_each_entry_rcu(sdata, &local->interfaces, list) { in ieee802154_wake_queue()
44 list_for_each_entry_rcu(sdata, &local->interfaces, list) { in ieee802154_stop_queue()
Dmain.c99 INIT_LIST_HEAD(&local->interfaces); in ieee802154_alloc_hw()
130 BUG_ON(!list_empty(&local->interfaces)); in ieee802154_free_hw()
Drx.c208 list_for_each_entry_rcu(sdata, &local->interfaces, list) { in __ieee802154_rx_handle_packet()
235 list_for_each_entry_rcu(sdata, &local->interfaces, list) { in ieee802154_monitors_rx()
Dieee802154_i.h48 struct list_head interfaces; member
Diface.c281 list_for_each_entry(nsdata, &local->interfaces, list) { in ieee802154_check_concurrent_iface()
683 list_add_tail_rcu(&sdata->list, &local->interfaces); in ieee802154_if_add()
710 list_for_each_entry_safe(sdata, tmp, &local->interfaces, list) { in ieee802154_remove_interfaces()
/linux-4.4.14/Documentation/filesystems/nfs/
D00-INDEX15 nfsd-admin-interfaces.txt
16 - Administrative interfaces for nfsd.
Dnfsd-admin-interfaces.txt1 Administrative interfaces for nfsd
4 Note that normally these interfaces are used only by the utilities in
/linux-4.4.14/drivers/net/can/usb/
DKconfig1 menu "CAN USB interfaces"
17 tristate "Geschwister Schneider UG interfaces"
62 tristate "PEAK PCAN-USB/USB Pro interfaces for CAN 2.0b/CAN-FD"
/linux-4.4.14/net/8021q/
DKconfig8 Select this and you will be able to create 802.1Q VLAN interfaces
9 on your Ethernet interfaces. 802.1Q VLAN supports almost
/linux-4.4.14/Documentation/devicetree/bindings/soc/fsl/
Dbman-portals.txt12 Portals are memory mapped interfaces to BMan that allow low-latency, lock-less
14 interfaces with the BMan
Dqman-portals.txt13 Portals are memory mapped interfaces to QMan that allow low-latency, lock-less
15 interfaces with the QMan
/linux-4.4.14/Documentation/devicetree/bindings/misc/
Dfsl,qoriq-mc.txt7 queues, buffer pools, I/O interfaces. These resources are building
9 such as network interfaces, crypto accelerator instances, L2 switches,
/linux-4.4.14/drivers/staging/gdm72xx/
DKconfig40 Select this option if the WiMAX module interfaces with the host
47 Select this option if the WiMAX module interfaces with the host
/linux-4.4.14/Documentation/ide/
Dide.txt15 *** PCI versions of the CMD640 and RZ1000 interfaces are now detected
33 *** interfaces, one *MUST* use the "cmd640.probe_vlb" kernel option.
56 It supports up to 9 IDE interfaces per default, on one or more IRQs (usually
66 To access devices on interfaces > ide0, device entries please make sure that
70 This driver automatically probes for most IDE interfaces (including all PCI
71 ones), for the drives/geometries attached to those interfaces, and for the IRQ
72 lines being used by the interfaces (normally 14, 15 for ide0/ide1).
74 Any number of interfaces may share a single IRQ if necessary, at a slight
144 be a separate MS-DOS driver just for the controller. IDE interfaces
/linux-4.4.14/Documentation/devicetree/bindings/dma/
Dapm-xgene-dma.txt3 DMA nodes are defined to describe on-chip DMA interfaces in
6 Required properties for DMA interfaces:
/linux-4.4.14/Documentation/virtual/kvm/
Dreview-checklist.txt29 10. User/kernel interfaces and guest/host interfaces must be 64-bit clean
/linux-4.4.14/sound/usb/
DKconfig31 audio/MIDI interfaces.
44 interfaces or controllers US-122, US-224 and US-428.
55 Say Y here to include support for caiaq USB audio interfaces,
99 interfaces.
/linux-4.4.14/drivers/char/ipmi/
DKconfig54 bool 'Probe for all possible IPMI system interfaces by default'
58 Modern systems will usually expose IPMI interfaces via a discoverable
77 Provides a driver for OPAL firmware-based IPMI interfaces.
/linux-4.4.14/Documentation/video4linux/
DREADME.pvrusb239 interfaces appropriately as devices are hotplugged in the
42 3. High level interfaces which glue the driver to various published
89 interfaces tie into the driver through this module. This module
92 instances of multiple interfaces (thus you can for example change
122 interfaces (e.g. V4L, sysfs, etc), and in fact even those high
123 level interfaces are restricted to the API defined in
127 controlling the hardware. High level interfaces (e.g. V4L, sysfs)
163 through one of the high level interfaces).
Domap4_camera.txt19 This driver is supporting _only_ the CSI2-A/B interfaces for now.
/linux-4.4.14/sound/soc/rockchip/
DKconfig6 the Rockchip SoCs' Audio interfaces. You will also need to
7 select the audio interfaces to support below.
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-class-net90 value. This is used to disambiguate interfaces which might be
91 stacked (e.g: VLAN interfaces) but still have the same MAC
119 Note: This attribute is only valid for interfaces that implement
157 used to resolve interfaces chaining, linking and stacking.
158 Physical interfaces have the same 'ifindex' and 'iflink' values.
226 Note: this attribute is only valid for interfaces that implement
Ddebugfs-pfo-nx-crypto7 These debugfs interfaces are built by the nx-crypto driver, built in
Dconfigfs-spear-pcie-gadget10 This interfaces can be used to show spear's PCIe device capability.
Dsysfs-bus-usb5 individual interfaces instead a whole device
11 that need multiple interfaces.
17 This is used as value that determines if interfaces
/linux-4.4.14/Documentation/aoe/
Daoe.txt46 "echo eth2 eth4 > /dev/etherd/interfaces" tells the aoe driver to
106 option discussed below) instead of /dev/etherd/interfaces to limit
107 AoE traffic to the network interfaces in the given
112 interfaces. The aoetools package provides an aoe-discover script
120 all network interfaces may be used for ATA over Ethernet. Here is a
Dudev.txt21 SUBSYSTEM=="aoe", KERNEL=="interfaces", NAME="etherd/%k", GROUP="disk", MODE="0220"
/linux-4.4.14/Documentation/cris/
DREADME31 range of built-in interfaces, all with modern scatter/gather DMA.
33 Memory interfaces:
40 I/O interfaces:
51 (not all interfaces are available at the same time due to chip pin
61 I-cache and 16kB D-cache and with a wide range of device interfaces
/linux-4.4.14/net/mac80211/
Dpm.c85 list_for_each_entry(sdata, &local->interfaces, list) { in __ieee80211_suspend()
142 list_for_each_entry(sdata, &local->interfaces, list) { in __ieee80211_suspend()
Diface.c186 list_for_each_entry(iter, &local->interfaces, list) { in ieee80211_verify_mac()
261 list_for_each_entry(nsdata, &local->interfaces, list) { in ieee80211_check_concurrent_iface()
1583 list_for_each_entry(sdata, &local->interfaces, list) { in ieee80211_assign_perm_addr()
1594 list_for_each_entry(sdata, &local->interfaces, list) { in ieee80211_assign_perm_addr()
1609 list_for_each_entry(sdata, &local->interfaces, list) { in ieee80211_assign_perm_addr()
1645 list_for_each_entry(sdata, &local->interfaces, list) { in ieee80211_assign_perm_addr()
1670 list_for_each_entry(sdata, &local->interfaces, list) { in ieee80211_assign_perm_addr()
1845 list_add_tail_rcu(&sdata->list, &local->interfaces); in ieee80211_if_add()
1905 list_for_each_entry_safe(sdata, tmp, &local->interfaces, list) { in ieee80211_remove_interfaces()
Dutil.c250 list_for_each_entry_rcu(sdata, &local->interfaces, list) { in ieee80211_propagate_queue_wake()
356 list_for_each_entry_rcu(sdata, &local->interfaces, list) { in __ieee80211_stop_queue()
594 list_for_each_entry_rcu(sdata, &local->interfaces, list) { in __iterate_interfaces()
1693 list_for_each_entry(sdata, &local->interfaces, list) in ieee80211_handle_reconfig_failure()
1849 list_for_each_entry(sdata, &local->interfaces, list) { in ieee80211_reconfig()
1863 list_for_each_entry_continue_reverse(sdata, &local->interfaces, in ieee80211_reconfig()
1893 list_for_each_entry(sdata, &local->interfaces, list) { in ieee80211_reconfig()
1991 list_for_each_entry(sdata, &local->interfaces, list) { in ieee80211_reconfig()
2020 list_for_each_entry(sdata, &local->interfaces, list) in ieee80211_reconfig()
2023 list_for_each_entry(sdata, &local->interfaces, list) in ieee80211_reconfig()
[all …]
Doffchannel.c127 list_for_each_entry(sdata, &local->interfaces, list) { in ieee80211_offchannel_stop_vifs()
161 list_for_each_entry(sdata, &local->interfaces, list) { in ieee80211_offchannel_return()
Dchan.c252 list_for_each_entry_rcu(sdata, &local->interfaces, list) { in ieee80211_get_chanctx_max_required_bw()
406 list_for_each_entry_rcu(sdata, &local->interfaces, list) { in ieee80211_is_radar_required()
429 list_for_each_entry_rcu(sdata, &local->interfaces, list) { in ieee80211_chanctx_radar_required()
576 list_for_each_entry_rcu(sdata, &local->interfaces, list) { in ieee80211_recalc_chanctx_chantype()
707 list_for_each_entry_rcu(sdata, &local->interfaces, list) { in ieee80211_recalc_smps_chanctx()
/linux-4.4.14/drivers/net/can/spi/
DKconfig1 menu "CAN SPI interfaces"
/linux-4.4.14/Documentation/watchdog/
Dwdt.txt10 All the interfaces provide /dev/watchdog, which when open must be written
46 The external event interfaces on the WDT boards are not currently supported.
/linux-4.4.14/Documentation/devicetree/bindings/media/i2c/
Dadv7604.txt24 Documentation/devicetree/bindings/media/video-interfaces.txt. The port nodes
40 The following three properties are defined in video-interfaces.txt and are
Dmt9m111.txt11 Documentation/devicetree/bindings/media/video-interfaces.txt.
Dmt9p031.txt20 Documentation/devicetree/bindings/media/video-interfaces.txt.
Dov2659.txt16 Documentation/devicetree/bindings/media/video-interfaces.txt.
Dmt9v032.txt25 Documentation/devicetree/bindings/media/video-interfaces.txt.
Dov2640.txt18 Documentation/devicetree/bindings/media/video-interfaces.txt.
Dtvp514x.txt24 media/video-interfaces.txt.
Dnokia,smia.txt8 Documentation/devicetree/bindings/media/video-interfaces.txt .
Dtvp7002.txt31 video-interfaces.txt.
Dtc358743.txt26 Documentation/devicetree/bindings/media/video-interfaces.txt.
/linux-4.4.14/Documentation/devicetree/bindings/display/imx/
Dfsl-imx-drm.txt33 Documentation/devicetree/bindings/media/video-interfaces.txt.
69 Documentation/devicetree/bindings/media/video-interfaces.txt.
Dhdmi.txt20 Documentation/devicetree/bindings/media/video-interfaces.txt,
/linux-4.4.14/sound/soc/bcm/
DKconfig9 to select the audio interfaces to support below.
/linux-4.4.14/drivers/gpu/drm/udl/
DKconfig15 Say M/Y to add support for these devices via drm/kms interfaces.
/linux-4.4.14/Documentation/isdn/
DREADME.mISDN3 It was designed to allow a broad range of applications and interfaces
DREADME.concap33 In contrast, LAN network interfaces always used a single encapsulation
44 makes isdn network interfaces more flexible, but also much more
45 complex than traditional lan network interfaces.
59 isdn network interfaces I could have introduced yet another branch to
69 several different interfaces of even different hardware type, e.g. the
227 If general linux network interfaces explicitly supported concap
DREADME.x25105 isdn interfaces.
155 When all drivers and interfaces are loaded and configured you need to
156 ifconfig the network interfaces up and add X.25-routes to them. Use
181 used to monitor X.25 packets received by the network interfaces.
DREADME294 3. (only for network interfaces if the security flag is set)
313 This makes it possible to configure several network interfaces and ttys
314 for one EAZ, if the network interfaces are set to secure operation.
410 to one of the configured net-interfaces:
416 You can add as many interfaces as you like with addif following the
418 tested as many as 20 interfaces without any problem. However, if you
420 which starts with "eth". The number of "eth"-interfaces is limited by
544 Creates a slave interface for channel-bundling. Slave interfaces are
548 want. InterfaceName must be a real interface, NOT a slave. Slave interfaces
569 CAN be used, however it's possible to use single tty's/interfaces with
DREADME.sc64 channels can be specifically bound to particular interfaces.
149 To remove the driver, delete any interfaces that may exist (see isdnctrl(8)
190 interfaces are created and two routes added between the channels.
228 xiv) link the two /dev interfaces to the daemon
262 xvi) link the two /dev interfaces to the daemon
D00-INDEX8 - description of isdn4linux Link Level and Hardware Level interfaces.
DREADME.pcbit7 The driver interfaces with the standard kernel isdn facilities
DREADME.syncppp2 connection using network interfaces.
/linux-4.4.14/drivers/staging/gs_fpgaboot/
DREADME51 doesn't talk to any of Linux interfaces (such as PCIE).
58 any of linux interfaces (such as PCIE)
/linux-4.4.14/drivers/isdn/hardware/mISDN/
DKconfig22 * HFC-4S (4 S/T interfaces on one chip)
23 * HFC-8S (8 S/T interfaces on one chip)
/linux-4.4.14/drivers/net/ethernet/tile/
DKconfig15 on-chip Tilera Gigabit Ethernet and XAUI interfaces.
/linux-4.4.14/drivers/staging/fsl-mc/
DREADME.txt35 interfaces, an L2 switch, or accelerator instances.
37 The MC provides memory-mapped I/O command interfaces (MC portals)
82 the objects involved in creating a network interfaces.
190 -DPIO (Datapath I/O): provides interfaces to enqueue and dequeue
326 -DPMCPs to send MC commands, to configure network interfaces
354 interfaces needed to connect the DPAA2 network interface to
/linux-4.4.14/Documentation/gpio/
D00-INDEX4 - Introduction to GPIOs and their kernel interfaces
Dsysfs.txt32 - Control interfaces used to get userspace control over GPIOs;
40 The control interfaces are write-only:
Ddrivers-on-gpio.txt69 presenting all the right in-kernel and sysfs interfaces to make your system
74 with the regulator subsystem and giving you all the right interfaces.
/linux-4.4.14/Documentation/x86/
Dpat.txt22 attributes at the page level. In order to avoid aliasing, these interfaces
23 should be used thoughtfully. Below is a table of interfaces available,
160 interfaces. Users writing to /proc/mtrr are suggested to use above interfaces.
Dearly-microcode.txt24 There are two legacy user space interfaces to load microcode, either through
/linux-4.4.14/sound/soc/kirkwood/
DKconfig7 audio interfaces to support below.
/linux-4.4.14/drivers/staging/unisys/
DTODO9 - enhance debugfs interfaces (e.g., per device, etc.)
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
Dpxa-mmc.txt3 Driver bindings for the PXA MCI (MMC/SDIO) interfaces
/linux-4.4.14/Documentation/devicetree/bindings/display/exynos/
Dexynos_dp.txt69 -video interfaces: Device node can contain video interface port
72 [1]: Documentation/devicetree/bindings/media/video-interfaces.txt
Dexynos_dsim.txt31 Video interfaces:
53 [2]: Documentation/devicetree/bindings/media/video-interfaces.txt
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Dfsl-sai.txt5 serial interfaces with frame synchronization such as I2S, AC97, TDM, and
6 codec/DSP interfaces.
/linux-4.4.14/Documentation/devicetree/bindings/media/xilinx/
Dxlnx,v-tc.txt14 interfaces clock.
Dxlnx,video.txt22 - ports: Video port, using the DT bindings defined in ../video-interfaces.txt.
Dxlnx,v-tpg.txt21 - port: Video port, using the DT bindings defined in ../video-interfaces.txt.
Dvideo.txt10 cores are represented as defined in ../video-interfaces.txt.
/linux-4.4.14/drivers/staging/fsl-mc/bus/
DKconfig18 network interfaces (NICs), crypto accelerator instances,
/linux-4.4.14/drivers/iio/buffer/
DKconfig7 tristate "IIO callback buffer used for push in-kernel interfaces"
/linux-4.4.14/arch/arm/boot/dts/
Dk2l-netcp.dtsi160 interfaces {
186 netcp-interfaces {
Dk2e-netcp.dtsi161 interfaces {
203 netcp-interfaces {
Dk2hk-netcp.dtsi180 interfaces {
206 netcp-interfaces {
Dat91sam9x5_macb1.dtsi3 * Ethernet interfaces.
/linux-4.4.14/drivers/block/aoe/
Daoechr.c69 interfaces(const char __user *str, size_t size) in interfaces() function
174 ret = interfaces(buf, cnt); in aoechr_write()
/linux-4.4.14/Documentation/devicetree/bindings/display/
Darm,pl11x.txt41 for video transmitter interfaces; see
42 Documentation/devicetree/bindings/media/video-interfaces.txt;
Dmarvell,pxa2xx-lcdc.txt14 - port: connection to the LCD panel (see video-interfaces.txt)
/linux-4.4.14/Documentation/devicetree/bindings/arm/bcm/
Dbrcm,nsp.txt7 several peripheral interfaces including multiple Gigabit Ethernet PHYs,
/linux-4.4.14/sound/soc/jz4740/
DKconfig8 interfaces to support below.
/linux-4.4.14/Documentation/cpu-freq/
Dintel-pstate.txt19 itself. The driver provides the interfaces between the cpufreq core and
24 In addition to the interfaces provided by the cpufreq core for
/linux-4.4.14/drivers/media/platform/davinci/
DKconfig38 Enables DaVinci CCD hw module. DaVinci CCDC hw interfaces
54 Enables DM355 CCD hw module. DM355 CCDC hw interfaces
/linux-4.4.14/Documentation/sound/alsa/
DAudiophile-Usb.txt25 The device has 4 audio interfaces, and 2 MIDI ports:
39 * Two interfaces can't use different sample depths at the same time.
43 Due to the USB 1.1 bandwidth limitation, a limited number of interfaces can be
102 Audiophile interfaces are mapped to alsa pcm devices in the following
181 Alsa now reports Little-Endian interfaces. Thus playing a file now is as simple as
309 - choosing b2 will prepare all interfaces for 24bits/96kHz but you'll
415 4.3 - Getting 2 input and/or output interfaces in Jack
434 Enabling multiple Audiophile USB interfaces for Jackd will certainly require:
/linux-4.4.14/net/hsr/
DKconfig10 your Linux box needs (at least) two physical Ethernet interfaces,
/linux-4.4.14/drivers/net/ethernet/smsc/
Dsmc9194.h195 static const char * interfaces[ 2 ] = { "TP", "AUI" }; variable
/linux-4.4.14/Documentation/devicetree/bindings/
Dgraph.txt22 Documentation/devicetree/bindings/media/video-interfaces.txt.
23 Here the ports describe data interfaces, and the links between them are
/linux-4.4.14/sound/soc/blackfin/
DKconfig10 You will also need to select the audio interfaces to support below.
84 interfaces are connected to the first SPORT port on the BF5XX board.
131 You will also need to select the audio interfaces to support below.
/linux-4.4.14/Documentation/sysctl/
Dnet.txt63 interfaces still use mq as root qdisc, which in turn uses this default for its
145 Maximum number of packets taken from all interfaces in one polling cycle (NAPI
146 poll). In one polling cycle interfaces which are registered to polling are
242 /proc/net/atalk_iface lists all the interfaces configured for appletalk.It
266 The /proc/net/ipx_interface file lists all IPX interfaces. For each interface
/linux-4.4.14/Documentation/devicetree/bindings/display/rockchip/
Ddw_hdmi-rockchip.txt12 Documentation/devicetree/bindings/media/video-interfaces.txt. For
Drockchip-vop.txt33 Documentation/devicetree/bindings/media/video-interfaces.txt.
/linux-4.4.14/Documentation/powerpc/
D00-INDEX30 - Information on the ptrace interfaces for hardware debug registers.
Dbootwrapper.txt13 interfaces found on PowerPC platforms. OpenFirmware is the most commonly
33 bd_info structure used in the old U-Boot interfaces,
95 Used by OpenFirmware and other firmware interfaces
/linux-4.4.14/Documentation/hwmon/
Dadt741133 Besides standard interfaces, this driver adds (0 = off, 1 = on):
Dibmaem23 interfaces. This driver is completely separate from the older ibmpex driver.
Dadt746253 Besides standard interfaces driver adds the following:
Dadt747052 Besides standard interfaces driver adds the following:
/linux-4.4.14/sound/soc/cirrus/
DKconfig7 the EP93xx I2S or AC97 interfaces.
/linux-4.4.14/drivers/bus/
DKconfig27 connected slave/master interfaces.
45 can count events pertaining to the slave/master interfaces as well
/linux-4.4.14/Documentation/devicetree/bindings/display/panel/
Dsamsung,s6e8aa0.txt25 [2]: Documentation/devicetree/bindings/media/video-interfaces.txt
Dsamsung,ld9040.txt25 [3]: Documentation/devicetree/bindings/media/video-interfaces.txt
/linux-4.4.14/drivers/base/
Dbase.h31 struct list_head interfaces; member
Dclass.c177 INIT_LIST_HEAD(&cp->interfaces); in __class_register()
454 list_add_tail(&class_intf->node, &parent->p->interfaces); in class_interface_register()
Dbus.c561 list_for_each_entry(sif, &bus->p->interfaces, node) in bus_probe_device()
586 list_for_each_entry(sif, &bus->p->interfaces, node) in bus_remove_device()
933 INIT_LIST_HEAD(&priv->interfaces); in bus_register()
1144 list_add_tail(&sif->node, &subsys->p->interfaces); in subsys_interface_register()
/linux-4.4.14/drivers/staging/most/Documentation/
Ddriver_usage.txt35 one of the peripheral interfaces of a network interface controller (e.g.
54 and provides an easy way of extending the number of supported interfaces.
160 to the AIM. In case the AIM interfaces the VFS this would also create a device
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dmfd.txt11 drivers, level shifters, PHY (physical interfaces to things like USB or
/linux-4.4.14/Documentation/driver-model/
Dclass.txt41 can be used by drivers, extensions and interfaces.
143 particular class type. Device interfaces describe these mechanisms.
Ddevres.txt14 6. List of managed interfaces : Currently implemented managed interfaces
233 6. List of managed interfaces
/linux-4.4.14/Documentation/s390/
Ddriver-model.txt1 S/390 driver model interfaces
50 The device drivers can add entries to export per-device data and interfaces.
67 a. Each driver can provide one or more parameter interfaces where parameters can
68 be specified. These interfaces are also in the driver's responsibility.
Dcds.txt28 In order to build common device support for ESA/390 I/O interfaces, a
33 below. Some of them implement common Linux device driver interfaces, while
94 driver implementations on the IBM ESA/390 hardware platform. Those interfaces
128 Up to kernel 2.4, Linux/390 used to provide interfaces via the IRQ (subchannel).
154 ESA/390 I/O commands itself, but must use the Linux/390 CDS interfaces instead.
183 routine provides all interfaces required to drive arbitrary devices.
/linux-4.4.14/drivers/isdn/capi/
DKconfig36 ippp interfaces or ttyI emulation, say Y/M here.
/linux-4.4.14/drivers/staging/android/
DTODO6 - audit userspace interfaces to make sure they are sane
/linux-4.4.14/tools/power/cpupower/
DREADME19 interfaces [depending on configuration, see below].
/linux-4.4.14/drivers/iio/
DKconfig11 number of different physical interfaces (i2c, spi, etc).
/linux-4.4.14/drivers/net/
DKconfig124 This allows one to create virtual interfaces that map packets to
156 on packets. All interfaces (including the main interface) share L2
173 This allows one to create vxlan virtual interfaces that provide
187 This allows one to create geneve virtual interfaces that provide
306 This option enables the support for mapping interfaces into VRF's. The
/linux-4.4.14/Documentation/devicetree/bindings/i2c/
Di2c-rk3x.txt3 This driver interfaces with the native I2C controller present in Rockchip
/linux-4.4.14/sound/soc/atmel/
DKconfig7 to select the audio interfaces to support below.
/linux-4.4.14/Documentation/security/
DLSM.txt33 For extensive documentation on the available LSM hook interfaces, please
/linux-4.4.14/drivers/net/ethernet/apple/
DKconfig47 Say Y for support of BMAC Ethernet interfaces. These are used on G3
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/
DS3C2412.txt108 No current support for the SPI interfaces.
/linux-4.4.14/sound/soc/samsung/
DKconfig9 the Samsung SoCs' Audio interfaces. You will also need to
10 select the audio interfaces to support below.
/linux-4.4.14/Documentation/DocBook/
D80211.xml.db160 API-ieee80211-iterate-active-interfaces
161 API-ieee80211-iterate-active-interfaces-atomic
/linux-4.4.14/drivers/media/
DKconfig95 This API is mostly used by camera interfaces in embedded platforms.
124 This API is mostly used by camera interfaces in embedded platforms.
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dcci.txt44 interfaces.
53 hierarchical bus addressing. CCI interfaces
/linux-4.4.14/Documentation/hid/
Dhiddev.txt7 interfaces, but have similar sorts of communication needs. The two big
12 HID events to two separate interfaces:
14 device interfaces (such as keyboard, mouse and joystick) and a
/linux-4.4.14/Documentation/ioctl/
Dbotching-up-ioctls.txt13 actually only used once interfaces. But the clear downside is that there's much
180 are truly device-unique. One counterexample in the drm modeset interfaces is
206 interfaces. Indefinitely.
208 * Consider other interfaces than ioctls. A sysfs attribute is much better for
/linux-4.4.14/drivers/staging/iio/Documentation/
Dinkernel.txt29 Supporting in kernel interfaces in the driver (driver.h)
Doverview.txt31 turned on or off (if possible) via sysfs interfaces.
/linux-4.4.14/Documentation/input/
Dbcm5974.txt37 different interfaces of the same usb device. This creates a race condition
Dcma3000_d0x.txt29 CMA3000 chip supports mutually exclusive I2C and SPI interfaces for
/linux-4.4.14/tools/perf/Documentation/
Dperf-annotate.txt66 used. This interfaces starts by centering on the line with more
/linux-4.4.14/net/can/
DKconfig50 CAN frames can be routed between CAN network interfaces (one hop).
/linux-4.4.14/drivers/net/team/
DKconfig4 This allows one to create virtual interfaces that teams together
/linux-4.4.14/Documentation/devicetree/bindings/iommu/
Diommu.txt71 have multiple master interfaces (to one or more IOMMU devices).
76 master interfaces of the device. One entry in the list describes one master
/linux-4.4.14/drivers/i2c/busses/
DKconfig40 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
50 756/766/768 mainboard I2C interfaces. The driver also includes
96 801 family of mainboard I2C interfaces. Specifically, the following
160 PIIX4 family of mainboard I2C interfaces. Specifically, the following
193 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
236 96x SMBus (a subset of I2C) interfaces. Specifically, the following
318 This exposes the various PowerMac i2c interfaces to the linux i2c
717 Supports the PA Semi PWRficient on-chip SMBus interfaces.
827 This driver supports the 2 I2C interfaces on the Renesas SH7760.
1158 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
[all …]
/linux-4.4.14/drivers/ide/
DKconfig220 tristate "Platform driver for IDE interfaces"
257 prefetch on CMD640 IDE interfaces. For details, read
725 This includes on-board IDE interfaces on some Amiga models (A600,
726 A1200, A4000, and A4000T), and IDE interfaces on the Zorro expansion
741 use Gayle IDE interfaces on the Zorro expansion bus.
747 This is the IDE driver for the IDE interfaces on the Buddha, Catweasel
748 and X-Surf expansion boards. It supports up to two interfaces on the
753 to one of its IDE interfaces.
/linux-4.4.14/net/batman-adv/
DKconfig47 Note that interfaces controlled by batman-adv must be manually
/linux-4.4.14/drivers/staging/
DKconfig10 interfaces that most likely will be changed in the near
/linux-4.4.14/Documentation/arm/
Duefi.txt2 governing the behaviours of compatible firmware interfaces. It is
DIXP4xx42 - Network interfaces (HSS, Utopia, NPEs, etc)
109 interface. In addition, it also supports to POTs interfaces connected
/linux-4.4.14/drivers/net/ethernet/sun/
DKconfig14 the questions about Sun network interfaces. If you say Y, you will be
/linux-4.4.14/tools/testing/selftests/ftrace/
DREADME4 kernel. Since ftrace exports interfaces via the debugfs, we just need

123