| /linux-6.15/drivers/usb/gadget/udc/cdns2/ |
| H A D | cdns2-gadget.c | 1358 min_buf_tx += pep->buffering; in cdns2_eps_onchip_buffer_init() 1360 min_buf_rx += pep->buffering; in cdns2_eps_onchip_buffer_init() 1372 if (free + pep->buffering >= 4) in cdns2_eps_onchip_buffer_init() 1375 free = free + pep->buffering; in cdns2_eps_onchip_buffer_init() 1379 pep->buffering = free; in cdns2_eps_onchip_buffer_init() 1388 tx_offset += pep->buffering * 1024; in cdns2_eps_onchip_buffer_init() 1392 if (free + pep->buffering >= 4) in cdns2_eps_onchip_buffer_init() 1395 free = free + pep->buffering; in cdns2_eps_onchip_buffer_init() 1399 pep->buffering = free; in cdns2_eps_onchip_buffer_init() 1979 pep->buffering = 4; in cdns2_gadget_match_ep() [all …]
|
| /linux-6.15/tools/perf/tests/shell/attr/ |
| H A D | test-record-no-buffering | 3 args = --no-bpf-event --no-buffering kill >/dev/null 2>&1
|
| /linux-6.15/drivers/iio/buffer/ |
| H A D | Kconfig | 34 tristate "Industrial I/O HW buffering" 44 tristate "Industrial I/O buffering based on kfifo"
|
| /linux-6.15/tools/memory-model/litmus-tests/ |
| H A D | LB+poonceonces.litmus | 6 * Can the counter-intuitive outcome for the load-buffering pattern
|
| H A D | LB+poacquireonce+pooncerelease.litmus | 6 * Does a release-acquire pair suffice for the load-buffering litmus
|
| H A D | SB+poonceonces.litmus | 7 * to order the store-buffering pattern, where each process writes to the
|
| H A D | SB+fencembonceonces.litmus | 7 * order the store-buffering pattern, where each process writes to the
|
| H A D | LB+fencembonceonce+ctrlonceonce.litmus | 7 * the load-buffering pattern, in other words, preventing all processes
|
| H A D | README | 54 load-buffering litmus test, where each process reads from one 58 Does a release-acquire pair suffice for the load-buffering 118 buffering, which forms the core of Dekker's mutual-exclusion
|
| /linux-6.15/Documentation/devicetree/bindings/net/ |
| H A D | lpc-eth.txt | 11 - use-iram: Use LPC32xx internal SRAM (IRAM) for DMA buffering
|
| H A D | fsl,fman-muram.yaml | 18 Packet buffering (Tx/Rx FIFOs)
|
| H A D | adi,adin1110.yaml | 16 circuitry, input and output clock buffering.
|
| /linux-6.15/drivers/gpu/drm/clients/ |
| H A D | Kconfig | 51 is 100. Typical values for double buffering will be 200, 52 triple buffering 300.
|
| /linux-6.15/Documentation/devicetree/bindings/iio/imu/ |
| H A D | bosch,bmi323.yaml | 14 gyroscopic measurements with hardware fifo buffering. Sensor also provides
|
| /linux-6.15/Documentation/devicetree/bindings/iio/accel/ |
| H A D | kionix,kx022a.yaml | 16 data-rates and a hardware-fifo buffering. These accelerometers can be
|
| /linux-6.15/Documentation/devicetree/bindings/iio/dac/ |
| H A D | microchip,mcp4725.yaml | 34 Enable buffering of the external Vref pin. This boolean is not valid
|
| /linux-6.15/Documentation/admin-guide/device-mapper/ |
| H A D | dm-ebs.rst | 13 Underlying block size can be set to > 4K to test buffering larger units.
|
| H A D | dm-zoned.rst | 37 dm-zoned implements an on-disk buffering scheme to handle non-sequential 53 zones of the device may be used also for buffering user random writes. 56 reused for buffering incoming random writes.
|
| /linux-6.15/tools/memory-model/Documentation/ |
| H A D | recipes.txt | 195 load buffering, release-acquire chains, store buffering. 350 Load buffering (LB) 471 Store buffering 474 Store buffering can be thought of as upside-down load buffering, so
|
| /linux-6.15/fs/jffs2/ |
| H A D | Kconfig | 33 bool "JFFS2 write-buffering support" 37 This enables the write-buffering support in JFFS2.
|
| /linux-6.15/fs/cramfs/ |
| H A D | Kconfig | 43 This saves some memory since no intermediate buffering is
|
| /linux-6.15/Documentation/filesystems/ |
| H A D | udf.rst | 15 be bound to the underlying cd device to provide the required buffering
|
| /linux-6.15/Documentation/core-api/ |
| H A D | swiotlb.rst | 13 memory buffer. This approach is generically called "bounce buffering", and the 20 if bounce buffering is necessary. If so, the DMA layer manages the allocation, 22 device, some devices in a system may use bounce buffering while others do not. 25 memory buffer, doing bounce buffering is slower than doing DMA directly to the 55 the unrelated kernel data. This problem is solved by bounce buffering the DMA
|
| /linux-6.15/drivers/usb/cdns3/ |
| H A D | cdnsp-gadget.c | 1599 pep->buffering = readl(reg + XBUF_RX_TAG_MASK_0_OFFSET); in cdnsp_get_ep_buffering() 1601 pep->buffering = (pep->buffering + 1) / 2; in cdnsp_get_ep_buffering() 1613 pep->buffering = (readl(reg) + 1) / 2; in cdnsp_get_ep_buffering() 1614 pep->buffering_period = pep->buffering; in cdnsp_get_ep_buffering()
|
| H A D | cdns3-gadget.c | 2107 u8 buffering; in cdns3_ep_config() local 2110 buffering = priv_dev->ep_buf_size - 1; in cdns3_ep_config() 2129 buffering = (priv_ep->bMaxBurst + 1) * (priv_ep->mult + 1) - 1; in cdns3_ep_config() 2170 buffering = min_t(u8, buffering, EP_CFG_BUFFERING_MAX); in cdns3_ep_config() 2175 ret = cdns3_ep_onchip_buffer_reserve(priv_dev, buffering + 1, in cdns3_ep_config() 2204 EP_CFG_BUFFERING(buffering) | in cdns3_ep_config()
|