Searched full:interface (Results 1 – 25 of 1782) sorted by relevance
12345678910>>...72
| /Documentation/devicetree/bindings/clock/ti/ |
| D | interface.txt | 1 Binding for Texas Instruments interface clock.
16 "ti,omap3-interface-clock" - basic OMAP3 interface clock
17 "ti,omap3-no-wait-interface-clock" - interface clock which has no hardware
19 "ti,omap3-hsotgusb-interface-clock" - interface clock with USB specific HW
21 "ti,omap3-dss-interface-clock" - interface clock with DSS specific HW handling
22 "ti,omap3-ssi-interface-clock" - interface clock with SSI specific HW handling
23 "ti,am35xx-interface-clock" - interface clock with AM35xx specific HW handling
24 "ti,omap2430-interface-clock" - interface clock with OMAP2430 specific HW
37 compatible = "ti,omap3-interface-clock";
45 compatible = "ti,omap3-no-wait-interface-clock";
[all …]
|
| /Documentation/devicetree/bindings/powerpc/nintendo/ |
| D | wii.txt | 23 1.a) The Video Interface (VI) node
25 Represents the interface between the graphics processor and a external
34 1.b) The Processor Interface (PI) node
36 Represents the data and control interface between the main processor
58 Represents the digital signal processor interface, designed to offload
67 1.d) The Serial Interface (SI) node
69 Represents the interface to the four single bit serial interfaces.
70 The SI is a proprietary serial interface used normally to control gamepads.
71 It's NOT a RS232-type interface.
79 1.e) The Audio Interface (AI) node
[all …]
|
| D | gamecube.txt | 14 1.a) The Video Interface (VI) node
16 Represents the interface between the graphics processor and a external
25 1.b) The Processor Interface (PI) node
27 Represents the data and control interface between the main processor
47 Represents the digital signal processor interface, designed to offload
67 1.d) The Disk Interface (DI) node
69 Represents the interface used to communicate with mass storage devices.
77 1.e) The Audio Interface (AI) node
79 Represents the interface to the external 16-bit stereo digital-to-analog
88 1.f) The Serial Interface (SI) node
[all …]
|
| /Documentation/devicetree/bindings/rtc/ |
| D | trivial-rtc.yaml | 23 # AB-RTCMC-32.768kHz-B5ZE-S3: Real Time Clock/Calendar Module with I2C Interface
25 # AB-RTCMC-32.768kHz-EOZ9: Real Time Clock/Calendar Module with I2C Interface
35 # I2C-BUS INTERFACE REAL TIME CLOCK MODULE
37 # I2C-BUS INTERFACE REAL TIME CLOCK MODULE
40 # I2C-BUS INTERFACE REAL TIME CLOCK MODULE with Battery Backed RAM
42 # I2C-BUS INTERFACE REAL TIME CLOCK MODULE
54 # I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
56 # I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
58 # I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
60 # I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
[all …]
|
| /Documentation/networking/ |
| D | operstates.rst | 12 interface. Administrative state is the result of "ip link set dev
16 However, an interface is not usable just because the admin enabled it
20 shows the ability of an interface to transmit this user data.
34 to be notified of updates while the interface is admin up. This is
37 These values contain interface state:
40 Interface is admin up
43 Interface is in RFC2863 operational state UP or UNKNOWN. This is for
45 flag to determine whether they should use the interface.
56 contains RFC2863 state of the interface in numeric representation:
59 Interface is in unknown state, neither driver nor userspace has set
[all …]
|
| D | net_failover.rst | 16 original paravirtual interface is registered as 'standby' slave netdev and
19 'pci' device. The user accesses the network interface via 'failover' netdev.
35 feature on the virtio-net interface and assign the same MAC address to both
41 <interface type='network'>
50 </interface>
51 <interface type='hostdev' managed='yes'>
57 </interface>
60 interface and this acts as the 'persistent' device indicating that this
61 interface will always be plugged in. This is specified by the 'teaming' tag with
67 The second device definition is for the VF passthrough interface. Here the
[all …]
|
| D | batman-adv.rst | 30 batman-adv can operate. The batman-adv soft-interface can be created using the
35 To activate a given interface simply attach it to the ``bat0`` interface::
40 using/broadcasting on this/these interface(s).
42 To deactivate an interface you have to detach it from the "bat0" interface::
46 The same can also be done using the batctl interface subcommand::
48 batctl -m bat0 interface create
49 batctl -m bat0 interface add -M eth0
53 batctl -m bat0 interface del -M eth0
54 batctl -m bat0 interface destroy
56 There are additional settings for each batadv mesh interface, vlan and hardif
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | ca_high_level.rst | 25 Why the need for another CI interface?
29 Strictly speaking this is not a new interface.
31 The CI interface is defined in the DVB API in ca.h as:
38 int type; /* CA interface this slot supports */
39 #define CA_CI 1 /* CI high level interface */
40 #define CA_CI_LINK 2 /* CI link layer level interface */
41 #define CA_CI_PHYS 4 /* CI physical layer level interface */
43 #define CA_SC 128 /* simple smart card interface */
50 This CI interface follows the CI high level interface, which is not
53 This CI interface is quite different in the case that it tries to
[all …]
|
| /Documentation/devicetree/bindings/usb/ |
| D | usb-device.yaml | 19 "interface nodes" representing USB interfaces and "combined nodes"
22 A combined node shall be used instead of a device node and an interface node
24 interface.
26 A "hub node" is a combined node or an interface node that represents a USB
47 should be 2 for device nodes with interface nodes.
54 "^interface@[0-9a-f]{1,2}(,[0-9a-f]{1,2})$":
56 description: USB interface nodes.
58 representation of an interface-node unit address for configuration 1.
63 description: Interface nodes.
65 the product id, CN is the configuration value and IN is the interface
[all …]
|
| /Documentation/driver-api/usb/ |
| D | callbacks.rst | 19 interface on a device.
22 Called when the interface is no longer accessible, usually
54 The ioctl interface (2) should be used only if you have a very good
71 an interface. A driver's bond to an interface is exclusive.
81 Accept or decline an interface. If you accept the device return 0,
86 usb_set_intfdata(), to associate a data structure with an interface, so
88 particular interface. The device will not be suspended and you may do IO
89 to the interface you are called for and endpoint 0 of the device. Device
99 This callback is a signal to break any connection with an interface.
102 with another driver bound the interface, eg. a power management
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-net | 36 interface (Ethernet, FDDI, ATM, IEEE 802.15.4...). See
44 Hardware address currently assigned to this interface.
75 Hardware broadcast address for this interface. Format is a
84 Indicates the current physical link state of the interface.
94 operating correctly and designating another fallback interface.
129 Indicates whether the interface is in dormant state. Possible
131 0: interface is not dormant
132 1: interface is dormant
144 Indicates whether the interface is under test. Possible
148 0 interface is not being tested
[all …]
|
| D | procfs-attr-prev | 9 this interface is LSM dependent.
10 A process cannot write to this interface unless it
13 this interface are LSM dependent.
14 The format of the data used by this interface is LSM
16 SELinux and AppArmor provide this interface.
|
| D | procfs-attr-current | 8 this interface and hence obtain the security state
10 A process cannot write to this interface unless it
13 this interface and hence change the security state of
15 The format of the data used by this interface is LSM
17 SELinux, Smack and AppArmor provide this interface.
|
| D | procfs-attr-exec | 9 this interface and hence obtain the security state
11 A process cannot write to this interface unless it
14 this interface and hence change the security state of
16 The format of the data used by this interface is LSM
18 SELinux and AppArmor provide this interface.
|
| D | sysfs-tty | 29 These sysfs values expose the TIOCGSERIAL interface via
38 These sysfs values expose the TIOCGSERIAL interface via
47 These sysfs values expose the TIOCGSERIAL interface via
56 These sysfs values expose the TIOCGSERIAL interface via
65 These sysfs values expose the TIOCGSERIAL interface via
74 These sysfs values expose the TIOCGSERIAL interface via
83 These sysfs values expose the TIOCGSERIAL interface via
92 These sysfs values expose the TIOCGSERIAL interface via
101 These sysfs values expose the TIOCGSERIAL interface via
110 These sysfs values expose the TIOCGSERIAL interface via
[all …]
|
| /Documentation/devicetree/bindings/dma/ |
| D | atmel-xdma.txt | 13 - bit 13: SIF, source interface identifier, used to get the memory
14 interface identifier,
15 - bit 14: DIF, destination interface identifier, used to get the peripheral
16 interface identifier,
35 - bit 13: SIF, source interface identifier, used to get the memory
36 interface identifier,
37 - bit 14: DIF, destination interface identifier, used to get the peripheral
38 interface identifier,
|
| /Documentation/devicetree/bindings/media/ |
| D | ti-am437x-vpfe.txt | 5 applications. The capture module provides the system interface and the
13 - ti,am437x-vpfe-interface: can be one of the following,
14 0 - Raw Bayer Interface.
15 1 - 8 Bit BT656 Interface.
16 2 - 10 Bit BT656 Interface.
17 3 - YCbCr 8 Bit Interface.
18 4 - YCbCr 16 Bit Interface.
40 ti,am437x-vpfe-interface = <0>;
|
| D | microchip,csi2dc.yaml | 13 CSI2DC - Camera Serial Interface 2 Demux Controller
16 IDI interface or from a parallel bus interface.
19 clock domain towards a parallel interface that can be read by a sensor
21 IDI interface is Synopsys proprietary.
23 a parallel interface.
30 32-bit IDI interface or a parallel interface.
32 CSI2DC supports one 'port' node as source port with parallel interface.
143 # and the input is received from Synopsys IDI interface
156 csi2dc_in: endpoint { /* input from IDI interface */
172 # and the input is received from Synopsys IDI interface
[all …]
|
| /Documentation/driver-api/xilinx/ |
| D | eemi.rst | 5 Xilinx Zynq MPSoC Firmware Interface
7 The zynqmp-firmware node describes the interface to platform firmware.
8 ZynqMP has an interface to communicate with secure firmware. Firmware
9 driver provides an interface to firmware APIs. Interface APIs can be
12 Embedded Energy Management Interface (EEMI)
14 The embedded energy management interface is used to allow software
39 [0] Embedded Energy Management Interface (EEMI) API guide:
|
| /Documentation/devicetree/bindings/net/ |
| D | cavium-pip.txt | 5 several interfaces, and each interface may have several ports. These
21 - compatible: "cavium,octeon-3860-pip-interface"
25 - reg: The interface number.
31 Properties for PIP port which is a child the PIP interface:
36 - reg: The port number within the interface group.
54 interface@0 {
55 compatible = "cavium,octeon-3860-pip-interface";
58 reg = <0>; /* interface */
86 interface@1 {
87 compatible = "cavium,octeon-3860-pip-interface";
[all …]
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/ |
| D | network.txt | 58 - fsl,tdm-interface
61 Definition : Specify that hdlc is based on tdm-interface
63 The property below is dependent on fsl,tdm-interface:
75 Usage: required for tdm interface
81 Usage: required for tdm interface
87 Usage: required for tdm interface
93 Usage: required for tdm interface
98 usage: optional for tdm interface
108 Example for tdm interface:
121 fsl,tdm-interface;
[all …]
|
| /Documentation/networking/device_drivers/wwan/ |
| D | iosm.rst | 11 for linux or chrome platform for data exchange over PCIe interface between
12 Host platform & Intel M.2 Modem. The driver exposes interface conforming to the
14 manage the MBIM interface to enable data communication towards WWAN.
19 userspace interface MBIM "WWAN PORT" representing MBIM control channel and does
32 - configure IP network interface
37 described in [1] Mobile Broadband Interface Model v1.0 Errata-1.
44 The driver exposes an MBIM interface to the MBIM function by implementing
46 /dev/wwan0mbim0 character device. Application shall use this interface for
69 The IOSM driver exposes IP link interface "wwan0-X" of type "wwan" for IP
71 interface and for associating it with MBIM IP session. The Driver supports
[all …]
|
| D | t7xx.rst | 11 for data exchange over PCIe interface between Host platform & MediaTek's T700 5G modem.
12 The driver exposes an interface conforming to the MBIM protocol [1]. Any front end
13 application (e.g. Modem Manager) could easily manage the MBIM interface to enable
14 data communication towards WWAN. The driver also provides an interface to interact
35 - configure IP network interface
45 described in [1] Mobile Broadband Interface Model v1.0 Errata-1.
52 The driver exposes an MBIM interface to the MBIM function by implementing
54 /dev/wwan0mbim0 character device. Application shall use this interface for
77 The t7xx driver exposes IP link interface "wwan0-X" of type "wwan" for IP
79 interface and for associating it with MBIM IP session.
[all …]
|
| /Documentation/ABI/stable/ |
| D | syscalls | 1 What: The kernel syscall interface
3 This interface matches much of the POSIX interface and is based
7 Note that this interface is different for every architecture
|
| /Documentation/devicetree/bindings/pci/ |
| D | snps,dw-pcie-common.yaml | 23 Interface - DBI. In accordance with the reference manual the register
29 configuration provides a flexible interface for the system engineers to
45 generating interrupts. It's System Information Interface and MSI
46 interface. While the former one has some common for the Host and
47 Endpoint controllers IRQ-signals, the later interface is obviously
77 Data Bus Interface (DBI) clock. Clock signal for the AXI-bus
78 interface of the Configuration-Dependent Module, which is
82 Application AXI-bus Master interface clock. Basically this is
83 a clock for the controller DMA interface (PCI-to-CPU).
86 Application AXI-bus Slave interface clock. This is a clock for
[all …]
|
12345678910>>...72