| /linux/arch/m68k/ifpsp060/ |
| H A D | fpsp.doc | 109 The third section is the code section. After entering through an "Entry-point",
173 always exits through _060_real_snan <----
181 always exits through _060_real_operr <-----
189 always exits through _060_real_dz <----
197 always exits through _060_real_inex <----
206 may exit through _060_real_inex <---|
208 may exit through _060_real_ovfl <---|
210 may exit through _060_fpsp_done <---|
218 may exit through _060_real_inex <---|
220 may exit through _060_real_unfl <---|
[all …]
|
| H A D | isp.doc | 118 The third section is the code section. After entering through an "Entry-point",
176 060ISP is installed properly, these instructions will enter through the
185 through the "Entry-point"s _060_isp_cas() or _060_isp_cas2().
195 code has completed, then it should re-enter the 060ISP package through the
198 _060_real_cas2() and what it should be upon return to the package through
212 may exit through _060_real_itrace <----|
214 may exit through _060_real_chk <----|
216 may exit through _060_real_divbyzero <----|
218 may exit through _060_isp_done <----|
|
| /linux/Documentation/driver-api/media/drivers/ |
| H A D | pvrusb2.rst | 84 interfaces tie into the driver through this module. This module
86 and is designed to allow concurrent access through multiple
88 the tuner's frequency through sysfs while simultaneously streaming
89 video through V4L out to an instance of mplayer).
109 (proxy through USB instead of PCI) are enough different that this
116 access to the driver should be through one of the high level
123 will work through here.
151 kernel-friendly I2C adaptor driver, through which other external
154 through here that other V4L modules can reach into this driver to
158 through one of the high level interfaces).
[all …]
|
| /linux/Documentation/driver-api/md/ |
| H A D | raid5-cache.rst | 7 caches data to the RAID disks. The cache can be in write-through (supported
11 in write-through mode. A user can switch it to write-back mode by::
15 And switch it back to write-through mode by::
17 echo "write-through" > /sys/block/md0/md/journal_mode
22 write-through mode
34 The write-through cache will cache all data on cache disk first. After the data
39 In write-through mode, MD reports IO completion to upper layer (usually
44 In write-through mode, the cache disk isn't required to be big. Several
80 The write-through and write-back cache use the same disk format. The cache disk
91 write-through mode, MD calculates parity for IO data, writes both IO data and
|
| /linux/Documentation/devicetree/bindings/interrupt-controller/ |
| H A D | ti,pruss-intc.yaml | 15 which are then mapped to 10 possible output interrupts through two levels
19 remaining 8 (2 through 9) connected to external interrupt controllers
23 differences on the output interrupts 2 through 9. If this property is not
24 defined, it implies that all the PRUSS INTC output interrupts 2 through 9
25 (host_intr0 through host_intr7) are connected exclusively to the Arm interrupt
30 through 19) are connected to new sub-modules within the ICSSG instances.
81 interrupts through 2 levels of many-to-one mapping i.e. events to channel
82 mapping and channels to host interrupts so through this property entire
89 output interrupts 2 through 9) that are not connected to the Arm interrupt
|
| /linux/Documentation/networking/ |
| H A D | representors.rst | 105 if) their network access is implemented through a virtual switch port. [#]_
111 through a virtual switch port, even if they do not have a corresponding PCIe
114 This allows the entire switching behaviour of the NIC to be controlled through
121 A PCIe function which does not have network access through the internal switch
122 (not even indirectly through the hardware implementation of whatever services
132 network packets pass through the virtual port onto the switch. The network
133 access that the IP stack "sees" would then be configurable through tc rules;
155 through the switchdev function. For example, ``ndo_start_xmit()`` might send
156 the packet through a hardware TX queue attached to the switchdev function, with
164 through ``net_dev->dev.parent`` / ``SET_NETDEV_DEV()``), either of the
[all …]
|
| H A D | phy-link-topology.rst | 16 through the legacy ioctls and the ethtool netlink commands. The base assumption
25 Commands that needs to configure the PHY will go through the net_device.phydev
47 In this case, the SFP PHY is handled by phylib, and registered by phylink through
72 it is then possible to register PHYs to the topology through :
81 The PHY can then be removed from the topology through
86 are linked to a net_device through :c:func:`phy_attach_direct` will automatically
|
| /linux/arch/xtensa/include/asm/ |
| H A D | asm-uaccess.h | 31 * <error>. This implies that the macro falls through to the next
36 * through on success).
42 * <error> label to branch to on error; implies fall-through
61 * <error>. This implies that the macro falls through to the next
65 * branch fall-through case on success.
72 * <error> label to branch to on error; implies fall-through
|
| /linux/include/linux/mfd/ |
| H A D | db8500-prcmu.h | 306 * through I2C has not been correctly executed in the given time
308 * through I2C has not been correctly executed in the given time
309 * @VARMLOWSPEEDVALTO_ERR:The ARM low speed supply value transfered through
312 * through I2C has not been correctly executed in the given time
313 * @VARMRETENTIONVALTO_ERR: The ARM retention supply value transfered through
316 * through I2C has not been correctly executed in the given time
317 * @VAPEHIGHSPEEDVALTO_ERR: The APE highspeed supply value transfered through
319 * @VSAFEHPVALTO_ERR: The SAFE high power supply value transfered through I2C
321 * @VMODSEL1VALTO_ERR: The MODEM sel1 supply value transfered through I2C has
323 * @VMODSEL2VALTO_ERR: The MODEM sel2 supply value transfered through I2C has
[all …]
|
| /linux/tools/perf/pmu-events/arch/powerpc/power10/ |
| H A D | others.json | 45 …her unaligned, or treated as unaligned and require an additional recycle through the pipeline usin…
50 …her unaligned, or treated as unaligned and require an additional recycle through the pipeline usin…
55 …her unaligned, or treated as unaligned and require an additional recycle through the pipeline. Thi…
60 …her unaligned, or treated as unaligned and require an additional recycle through the pipeline. Thi…
65 …fetch stream. The stream could have been allocated through the hardware prefetch mechanism or thro…
|
| /linux/include/uapi/linux/ |
| H A D | if.h | 50 * via /sys/class/net/<dev>/flags. Flags which can be toggled through sysfs
59 * @IFF_UP: interface is up. Can be toggled through sysfs.
61 * @IFF_DEBUG: turn on debugging. Can be toggled through sysfs.
64 * @IFF_NOTRAILERS: avoid use of trailers. Can be toggled through sysfs.
67 * @IFF_NOARP: no ARP protocol. Can be toggled through sysfs. Volatile.
68 * @IFF_PROMISC: receive all packets. Can be toggled through sysfs.
69 * @IFF_ALLMULTI: receive all multicast packets. Can be toggled through
73 * @IFF_MULTICAST: Supports multicast. Can be toggled through sysfs.
74 * @IFF_PORTSEL: can set media type. Can be toggled through sysfs.
75 * @IFF_AUTOMEDIA: auto media select active. Can be toggled through sysfs.
[all …]
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | pixfmt-compressed.rst | 68 through the ``V4L2_CID_STATELESS_H264_DECODE_MODE``
71 required to be passed through the ``V4L2_CID_STATELESS_H264_SPS``,
122 through the ``V4L2_CID_STATELESS_MPEG2_SEQUENCE`` and
124 Quantisation matrices can optionally be specified through the
166 through the ``V4L2_CID_STATELESS_VP8_FRAME`` control.
188 through the ``V4L2_CID_STATELESS_VP9_FRAME`` and
213 through the ``V4L2_CID_MPEG_VIDEO_HEVC_DECODE_MODE``
216 through the following controls:
238 through the ``V4L2_CID_STATELESS_FWHT_PARAMS`` control.
268 frame to decode is required to be passed through the
|
| /linux/sound/core/seq/ |
| H A D | seq_dummy.c | 3 * ALSA sequencer MIDI-through client
17 Sequencer MIDI-through client
19 This gives a simple midi-through client. All the normal input events
49 MODULE_DESCRIPTION("ALSA sequencer MIDI-through client");
128 sprintf(pinfo.name, "Midi Through Port-%d:%c", idx, in create_port()
131 sprintf(pinfo.name, "Midi Through Port-%d", idx); in create_port()
173 "Midi Through"); in register_client()
189 /* don't convert events but just pass-through */ in register_client()
|
| /linux/drivers/hwmon/occ/ |
| H A D | Kconfig | 7 tristate "POWER8 OCC through I2C"
15 established through I2C bus.
21 tristate "POWER9 OCC through SBE"
29 established through SBE fifo on an FSI bus.
|
| /linux/drivers/i2c/muxes/ |
| H A D | Kconfig | 28 I2C busses connected through a MUX, which is controlled
29 through GPIO pins.
41 I2C busses connected through a MUX, which in turn is controlled
96 I2C busses connected through a MUX, which is controlled
116 I2C busses connected through a MUX, which is controlled
127 devices that are reachable through an I2C-mux. The devices on the mux
|
| /linux/Documentation/devicetree/bindings/sound/ |
| H A D | rt5682.txt | 11 - AVDD-supply: phandle to the regulator supplying analog power through the
15 bias through the MICVDD pin. Either MICVDD or VBAT should be present.
17 - VBAT-supply: phandle to the regulator supplying battery power through the
20 - DBVDD-supply: phandle to the regulator supplying I/O power through the DBVDD
24 and charge pump through the LDO1_IN pin.
|
| /linux/arch/parisc/include/uapi/asm/ |
| H A D | ptrace.h | 21 * It can be accessed through PTRACE_PEEKUSR/PTRACE_POKEUSR only.
48 * It can be accessed through PTRACE_GETREGSET with NT_PRSTATUS
49 * and through PTRACE_GETREGS.
73 * It can be accessed through PTRACE_GETREGSET with NT_PRFPREG
74 * and through PTRACE_GETFPREGS.
|
| /linux/Documentation/i2c/ |
| H A D | smbus-protocol.rst | 103 The register is specified through the Comm byte::
116 device, from a designated register that is specified through the Comm
134 register is specified through the Comm byte. This is the opposite of
151 specified through the Comm byte::
165 This command selects a device register (through the Comm byte), sends
180 designated register that is specified through the Comm byte. The amount
197 a device, to a designated register that is specified through the
213 This command selects a device register (through the Comm byte), sends
302 designated register that is specified through the Comm byte::
316 a device, to a designated register that is specified through the
|
| /linux/Documentation/filesystems/ |
| H A D | dax.rst | 166 Setting the `FS_XFLAG_DAX` flag (specifically or through inheritance) occurs even
175 whether DAX shall be enabled or not from virtiofs server through FUSE protocol,
203 a large amount of memory through a smaller window, then you cannot
235 exposure of uninitialized data through mmap.
259 writing the affected sectors (through the pmem driver, and if the underlying
262 Since `DAX` IO normally doesn't go through the ``driver/bio`` path, applications or
269 happens through the driver, and will clear bad sectors.
278 provided at the block layer through DM, or additionally, at the filesystem
280 can happen either by sending an IO through the driver, or zeroing (also through
|
| H A D | fuse-io.rst | 11 + write-through
26 write-through mode is the default and is supported on all kernels. The
30 In write-through mode each write is immediately sent to userspace as one or more
40 assumes that all changes to the filesystem go through the FUSE kernel module
|
| /linux/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| H A D | usb.txt | 11 "brg1" through "brg16": clock source is BRG1-BRG16, respectively
12 "clk1" through "clk24": clock source is CLK1-CLK24, respectively
15 "brg1" through "brg16": clock source is BRG1-BRG16, respectively
16 "clk1" through "clk24": clock source is CLK1-CLK24, respectively
|
| /linux/drivers/net/ethernet/sgi/ |
| H A D | meth.h | 122 … /* Bits 8 through 14 are used to determine Inter-Packet Gap between "Back to Back" packets */
126 /* Bits 15 through 21 are used to determine IPGR1 */
128 /* Bits 22 through 28 are used to determine IPGR2 */
130 #define METH_REV_SHIFT 29 /* Bits 29 through 31 are used to determine the revision */
186 /*#define METH_INT_RX_RPTR_MASK 0x0001F00*/ /* Bits 8 through 12 alias of RX read-pointer */
187 #define METH_INT_RX_RPTR_MASK 0x0000F00 /* Bits 8 through 11 alias of RX read-pointer - so, is Rx …
189 /* Bits 13 through 15 are always 0. */
191 #define METH_INT_TX_RPTR_MASK 0x1FF0000 /* Bits 16 through 24 alias of TX read-pointer */
193 #define METH_INT_RX_SEQ_MASK 0x2E000000 /* Bits 25 through 29 are the starting seq number for the m…
|
| /linux/Documentation/arch/s390/ |
| H A D | vfio-ap-locking.rst | 72 device driver is using it to plug/unplug AP devices passed through to the KVM
78 AP devices passed through to a KVM guest.
81 if the adapter is passed through to a KVM guest, it will have to be
82 unplugged. In order to figure out whether the adapter is passed through,
85 the mediated device is passed through (matrix_mdev->kvm != NULL) and if so,
89 pointer is not used to plug/unplug devices passed through to the KVM guest;
|
| /linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | bpf_obj_pinning.c | 79 /* pin BPF map into detached BPF FS through mnt_fd */ in bpf_obj_pinning_detached()
86 /* get BPF map from detached BPF FS through mnt_fd */ in bpf_obj_pinning_detached()
93 /* update map through one FD */ in bpf_obj_pinning_detached()
98 /* check values written/read through different FDs do match */ in bpf_obj_pinning_detached()
168 /* update map through one FD */ in validate_pin()
172 /* check values written/read through different FDs do match */ in validate_pin()
229 /* update map through one FD */ in validate_get()
233 /* check values written/read through different FDs do match */ in validate_get()
|
| /linux/drivers/regulator/ |
| H A D | Kconfig | 11 also provide status information to user space applications through a
301 EC and controlled through EC host commands.
358 through an I2C interface.
378 converter 12A DC-DC Buck controlled through an I2C
389 step down converter 12A or 16A DC-DC Buck controlled through an I2C
412 programmed through an I2C interface.
795 through the regulator interface. In addition it enables
814 supports basic operations (get/set voltage) through the regulator
834 through regulator interface.
844 through regulator interface.
[all …]
|