Searched full:interface (Results 1 – 25 of 1598) sorted by relevance
12345678910>>...64
| /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
36 compatible = "ti,omap3-interface-clock";
44 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/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 | 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 …]
|
| D | statistics.rst | 4 Interface statistics
10 This document is a guide to Linux network interface statistics.
12 There are three main sources of interface statistics in Linux:
14 - standard interface statistics based on
19 Standard interface statistics
48 to report related statistics. For example ethtool interface used
76 The historical `/proc/net/dev` text interface gives access to the list
79 Note that even though this interface is using
90 This simple interface is convenient especially in constrained/embedded
113 Ethtool IOCTL interface allows drivers to report implementation
[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
33 # I2C-BUS INTERFACE REAL TIME CLOCK MODULE
35 # I2C-BUS INTERFACE REAL TIME CLOCK MODULE with Battery Backed RAM
37 # I2C-BUS INTERFACE REAL TIME CLOCK MODULE
59 # I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
61 # I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
63 # I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
65 # I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
67 # I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
[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.txt | 9 "interface nodes" representing USB interfaces and "combined nodes"
12 A combined node shall be used instead of a device node and an interface node
14 interface.
16 A "hub node" is a combined node or an interface node that represents a USB
30 Required properties for device nodes with interface nodes:
35 Required properties for interface nodes:
37 the product id, CN is the configuration value and IN is the interface
43 - reg: the interface number and configuration value
46 an interface-node unit address for configuration 1.
92 interface@0 { /* interface 0 of configuration 1 */
[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 | 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 | 11 - bit 13: SIF, source interface identifier, used to get the memory
12 interface identifier,
13 - bit 14: DIF, destination interface identifier, used to get the peripheral
14 interface identifier,
33 - bit 13: SIF, source interface identifier, used to get the memory
34 interface identifier,
35 - bit 14: DIF, destination interface identifier, used to get the peripheral
36 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>;
|
| /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/arm/ |
| D | cci.txt | 10 clusters, through memory mapped interface, with a global control register
11 space and multiple sets of interface control registers, one per slave
12 interface.
53 - CCI control interface nodes
58 A CCI control interface node must contain the following
67 - interface-type:
71 depending on the interface type the node
80 corresponding interface programming
105 corresponding interface programming
135 Definition: a phandle containing the CCI control interface node
[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/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/admin-guide/ |
| D | btmrvl.rst | 5 All commands are used via debugfs interface.
18 It could be any valid GPIO pin# (e.g. 0-7) or 0xff (SDIO interface
26 # Use SDIO interface to wake up the host and set GAP to 0x80:
104 Interface Control Command::
106 hcitool cmd 0x3f 0x5b 0xf5 0x01 0x00 --Enable All interface
107 hcitool cmd 0x3f 0x5b 0xf5 0x01 0x01 --Enable Wlan interface
108 hcitool cmd 0x3f 0x5b 0xf5 0x01 0x02 --Enable BT interface
109 hcitool cmd 0x3f 0x5b 0xf5 0x00 0x00 --Disable All interface
110 hcitool cmd 0x3f 0x5b 0xf5 0x00 0x01 --Disable Wlan interface
111 hcitool cmd 0x3f 0x5b 0xf5 0x00 0x02 --Disable BT interface
|
| /Documentation/devicetree/bindings/misc/ |
| D | xlnx,sd-fec.txt | 15 - "s_axi_aclk", AXI4-Lite memory-mapped slave interface clock (required)
16 - "s_axis_din_aclk", DIN AXI4-Stream Slave interface clock (optional)
17 - "s_axis_din_words-aclk", DIN_WORDS AXI4-Stream Slave interface clock (optional)
18 - "s_axis_ctrl_aclk", Control input AXI4-Stream Slave interface clock (optional)
19 - "m_axis_dout_aclk", DOUT AXI4-Stream Master interface clock (optional)
20 - "m_axis_dout_words_aclk", DOUT_WORDS AXI4-Stream Master interface clock (optional)
21 - "m_axis_status_aclk", Status output AXI4-Stream Master interface clock (optional)
27 - xlnx,sdfec-din-words : A value 0 indicates that the DIN_WORDS interface is
34 - xlnx,sdfec-dout-words : A value 0 indicates that the DOUT_WORDS interface is
|
| /Documentation/driver-api/soundwire/ |
| D | summary.rst | 5 SoundWire is a new interface ratified in 2015 by the MIPI Alliance.
7 functions. SoundWire interface is optimized to integrate audio devices in
10 SoundWire is a 2-pin multi-drop interface with data and clock line. It
12 Broad level key features of SoundWire interface include:
15 commands over a single two-pin interface.
41 | Interface | | Data Signal | Interface 1 |
50 | Interface 2 |
59 or Slave interface, which of course can be confusing. In this summary and
60 code we use the term interface only to refer to the hardware. We follow the
61 Linux device model by mapping each Slave interface connected on the bus as a
[all …]
|
| /Documentation/process/ |
| D | stable-api-nonsense.rst | 3 The Linux Kernel Driver Interface
11 kernel interface, nor does it have a stable kernel interface**.
18 The kernel to userspace interface is the one that application programs use,
19 the syscall interface. That interface is **very** stable over time, and
22 That interface is the one that users and application programmers can count
28 You think you want a stable kernel interface, but you really do not, and
42 the world, they neither see this interface, nor do they care about it at
58 Binary Kernel Interface
60 Assuming that we had a stable kernel source interface for the kernel, a
61 binary interface would naturally happen too, right? Wrong. Please
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-querycap.rst | 147 :ref:`Video Capture <capture>` interface.
151 through the :ref:`Video Capture <capture>` interface.
155 :ref:`Video Output <output>` interface.
159 through the :ref:`Video Output <output>` interface.
163 Memory-To-Memory interface.
167 through the Video Memory-To-Memory interface.
171 interface. A video overlay device typically stores captured images
177 interface, providing Teletext and Closed Caption data.
181 interface.
185 interface.
[all …]
|
| /Documentation/infiniband/ |
| D | ipoib.rst | 8 setting the interface type to ARPHRD_INFINIBAND and the hardware
15 When the IPoIB driver is loaded, it creates one interface for each
16 port using the P_Key at index 0. To create an interface with a
17 different P_Key, write the desired P_Key into the main interface's
22 This will create an interface named ib0.8001 with P_Key 0x8001. To
27 The P_Key for any interface is given by the "pkey" file, and the
28 main interface for a subinterface is in "parent."
30 Child interface create/delete can also be done using IPoIB's
37 connected. The mode is set and read through an interface's
41 and so the interface MTU has is equal to the IB L2 MTU minus the
[all …]
|
12345678910>>...64