| /Linux-v5.15/arch/m68k/ifpsp060/ |
| 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 …]
|
| 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-v5.15/arch/xtensa/include/asm/ |
| D | asm-uaccess.h | 72 * <success>. This implies that the macro falls through to the next
77 * through on error).
82 * fall-through macro on error
101 * <error>. This implies that the macro falls through to the next
106 * through on success).
112 * <error> label to branch to on error; implies fall-through
131 * <error>. This implies that the macro falls through to the next
135 * branch fall-through case on success.
142 * <error> label to branch to on error; implies fall-through
|
| /Linux-v5.15/Documentation/driver-api/md/ |
| 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-v5.15/Documentation/driver-api/media/drivers/ |
| 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-v5.15/Documentation/devicetree/bindings/interrupt-controller/ |
| 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-v5.15/drivers/net/dsa/microchip/ |
| D | Kconfig | 18 Select to enable support for registering switches configured through I2C.
25 Select to enable support for registering switches configured through SPI.
39 This driver accesses KSZ8795 chip through SPI.
42 is through SPI.
49 Select to enable support for registering switches configured through
|
| /Linux-v5.15/include/linux/mfd/ |
| 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-v5.15/include/uapi/linux/ |
| 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-v5.15/sound/core/seq/ |
| 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");
122 sprintf(pinfo.name, "Midi Through Port-%d:%c", idx, in create_port()
125 sprintf(pinfo.name, "Midi Through Port-%d", idx); in create_port()
163 "Midi Through"); in register_client()
|
| /Linux-v5.15/drivers/hwmon/occ/ |
| D | Kconfig | 7 tristate "POWER8 OCC through I2C"
16 established through I2C bus.
22 tristate "POWER9 OCC through SBE"
31 established through SBE fifo on an FSI bus.
|
| /Linux-v5.15/Documentation/userspace-api/media/v4l/ |
| 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``,
117 through the ``V4L2_CID_STATELESS_MPEG2_SEQUENCE`` and
119 Quantisation matrices can optionally be specified through the
161 through the ``V4L2_CID_STATELESS_VP8_FRAME`` control.
193 through the ``V4L2_CID_MPEG_VIDEO_HEVC_DECODE_MODE``
196 through the following controls:
223 through the ``V4L2_CID_STATELESS_FWHT_PARAMS`` control.
|
| /Linux-v5.15/arch/parisc/include/uapi/asm/ |
| 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-v5.15/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| 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-v5.15/drivers/gpu/drm/i915/gem/ |
| D | i915_gem_object_types.h | 101 * coherent with the GPU, when also reading or writing through the CPU cache
104 * Userspace can also control this through struct drm_i915_gem_caching.
114 * On shared LLC platforms reads and writes through the CPU cache are
128 * reading and writing through the CPU cache. GPU writes can dirty the
162 * Write-through. Used for scanout surfaces.
168 * fallback to I915_CACHE_NONE. On the CPU side writes through the CPU
262 * When we lock this object through i915_gem_object_lock() with a
323 * writing through the CPU caches. The largely depends on the
340 * engine we only need to care about flushing any writes through the CPU
350 * LLC. The kernel uses this to always flush writes through the CPU
[all …]
|
| /Linux-v5.15/Documentation/i2c/ |
| D | smbus-protocol.rst | 101 The register is specified through the Comm byte::
114 device, from a designated register that is specified through the Comm
132 register is specified through the Comm byte. This is the opposite of
149 specified through the Comm byte::
163 This command selects a device register (through the Comm byte), sends
178 designated register that is specified through the Comm byte. The amount
195 a device, to a designated register that is specified through the
211 This command selects a device register (through the Comm byte), sends
300 designated register that is specified through the Comm byte::
314 a device, to a designated register that is specified through the
|
| /Linux-v5.15/drivers/i2c/muxes/ |
| 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
|
| /Linux-v5.15/Documentation/filesystems/ |
| D | fuse-io.rst | 11 + write-through
25 write-through mode is the default and is supported on all kernels. The
29 In write-through mode each write is immediately sent to userspace as one or more
39 assumes that all changes to the filesystem go through the FUSE kernel module
|
| D | dax.rst | 166 Setting the `FS_XFLAG_DAX` flag (specifically or through inheritance) occurs even
187 a large amount of memory through a smaller window, then you cannot
219 exposure of uninitialized data through mmap.
243 writing the affected sectors (through the pmem driver, and if the underlying
246 Since `DAX` IO normally doesn't go through the ``driver/bio`` path, applications or
253 happens through the driver, and will clear bad sectors.
262 provided at the block layer through DM, or additionally, at the filesystem
264 can happen either by sending an IO through the driver, or zeroing (also through
|
| /Linux-v5.15/drivers/net/ethernet/sgi/ |
| 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-v5.15/drivers/gpu/drm/msm/disp/dpu1/ |
| D | dpu_hw_interrupts.c | 131 /* ensure register writes go through */ in dpu_hw_intr_clear_intr_status_nolock()
151 * Now need to go through each IRQ status and find matching in dpu_hw_intr_dispatch_irq()
177 * Search through matching intr status. in dpu_hw_intr_dispatch_irq()
202 /* ensure register writes go through */ in dpu_hw_intr_dispatch_irq()
245 /* ensure register write goes through */ in dpu_hw_intr_enable_irq_locked()
294 /* ensure register write goes through */ in dpu_hw_intr_disable_irq_locked()
319 /* ensure register writes go through */ in dpu_hw_intr_clear_irqs()
338 /* ensure register writes go through */ in dpu_hw_intr_disable_irqs()
369 /* ensure register writes go through */ in dpu_hw_intr_get_interrupt_status()
|
| /Linux-v5.15/Documentation/admin-guide/media/ |
| D | fimc.rst | 13 data from LCD controller (FIMD) through the SoC internal writeback data
55 data from the sensor through more than one FIMC instance (e.g. for simultaneous
60 through media entity and links enumeration.
90 In order to enable more precise camera pipeline control through the sub-device
97 When we configure these devices through sub-device API at user space, the
134 You can either grep through the kernel log to find relevant information, i.e.
|
| /Linux-v5.15/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| D | ethernet-driver.rst | 29 All hardware resources are allocated and configured through the Management
31 and exposes ABIs through which they can be configured and controlled. A few
109 Frames are transmitted and received through hardware frame queues, which can be
129 DPNIs are decoupled from PHYs; a DPNI can be connected to a PHY through a DPMAC
130 object or to another DPNI through an internal link, but the connection is
162 added to a container on the MC bus in one of two ways: statically, through a
170 The checksum offloads can be independently configured on RX and TX through
186 non-standard driver stats can be consulted through ethtool -S option.
|
| /Linux-v5.15/fs/ |
| D | attr.c | 27 * If the inode has been found through an idmapped mount the user namespace of
28 * the vfsmount must be passed through @mnt_userns. This function will then
54 * If the inode has been found through an idmapped mount the user namespace of
55 * the vfsmount must be passed through @mnt_userns. This function will then
87 * If the inode has been found through an idmapped mount the user namespace of
88 * the vfsmount must be passed through @mnt_userns. This function will then
216 * If the inode has been found through an idmapped mount the user namespace of
217 * the vfsmount must be passed through @mnt_userns. This function will then
304 * If the inode has been found through an idmapped mount the user namespace of
305 * the vfsmount must be passed through @mnt_userns. This function will then
|
| /Linux-v5.15/drivers/cpuidle/ |
| D | Kconfig.arm | 12 at run-time through DT nodes. The CPUidle suspend backend is
24 managing idle states through the PSCI firmware interface.
45 ARM systems. Driver manages CPUs coordination through MCPM and
46 define different C-states for little and big cores through the
|
