| /linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | srio.txt | 64 memory and maintenance transactions then a single LIODN is
65 represented in the property for both transactions.
68 memory transactions and a unique LIODN for maintenance
69 transactions then a pair of LIODNs are represented in the
71 LIODN associated with memory transactions and the second element
72 represents the LIODN associated with maintenance transactions
|
| D | raideng.txt | 64 transactions from this JR and than be able to do address
|
| D | msi-pic.txt | 97 intercepts transactions and reroutes them to the true physical address.
|
| D | srio-rmu.txt | 32 The LIODN value is associated with all RMU transactions
|
| /linux-4.1.27/Documentation/devicetree/bindings/mfd/ |
| D | cros-ec.txt | 22 additional processing time in order to accept new transactions. If the delay
23 between transactions is not long enough the EC may not be able to respond
24 properly to subsequent transactions and cause them to hang. This property
25 specifies the delay, in usecs, introduced between transactions to account
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-fs-xfs | 25 outstanding transactions. The grant head is exported in
36 oustanding transactions, including regrants due to
37 rolling transactions. The grant head is exported in
|
| /linux-4.1.27/sound/firewire/ |
| D | fcp.c | 181 static LIST_HEAD(transactions);
242 list_add_tail(&t.list, &transactions); in fcp_avc_transaction()
300 list_for_each_entry(t, &transactions, list) { in fcp_bus_reset()
346 list_for_each_entry(t, &transactions, list) { in fcp_response()
392 WARN_ON(!list_empty(&transactions)); in fcp_module_exit()
|
| /linux-4.1.27/Documentation/powerpc/ |
| D | transactional_memory.txt | 16 instructions are presented to delimit transactions; transactions are
71 - See the ISA for full documentation of everything that will abort transactions.
80 Syscalls do not by design abort transactions, but beware: The kernel code will
98 Delivery of signals (both sync and async) during transactions provides a second
101 abort transactions. The usual ucontext_t passed to the signal handler
118 However, basic signal handlers don't need to be aware of transactions
180 transactions for consistency will use this.
198 in parts within transactions.
|
| D | pci_iov_resource_on_powernv.txt | 29 The interesting part is how the various PCIe transactions (MMIO, DMA, ...)
|
| /linux-4.1.27/Documentation/filesystems/pohmelfs/ |
| D | design_notes.txt | 28 Resending transactions to different servers on timeout or error.
35 POHMELFS is based on transactions, which are potentially long-standing objects that live
37 command (or set of commands, which is frequently used during data writing: single transactions
42 POHMELFS uses a asynchronous approach to data processing. Courtesy of transactions, it is
45 servers and async threads will pick up replies in parallel, find appropriate transactions in the
|
| /linux-4.1.27/Documentation/i2c/ |
| D | functionality | 64 A typical SMBus-only adapter would list all the SMBus transactions it
82 I2C_FUNC_SMBUS_EMUL includes all the SMBus transactions (with the
83 addition of I2C block transactions) which i2c-core can emulate using
109 and SMBus word data transactions. If not, then the driver won't work on
121 i2c-core will transparently implement SMBus transactions on top of I2C
|
| D | dev-interface | 90 transactions (mixing read and write messages in the same transaction)
116 Used only for SMBus transactions. This request only has an effect if the
143 You can do plain i2c transactions by using read(2) and write(2) calls.
147 You can do SMBus level transactions (see documentation file smbus-protocol
160 All these transactions return -1 on failure; you can read errno to see
161 what happened. The 'write' transactions return 0 on success; the
162 'read' transactions return the read value, except for read_block, which
189 checking on future transactions.)
|
| D | i2c-protocol | 37 Combined transactions
42 They are just like the above transactions, but instead of a stop bit P
49 Modified transactions
|
| D | writing-clients | 341 and they can be mixed in any way. The transactions are combined: no
387 All these transactions return a negative errno value on failure. The 'write'
388 transactions return 0 on success; the 'read' transactions return the read
389 value, except for block transactions, which return the number of values
|
| D | smbus-protocol | 243 The following I2C block transactions are supported by the
247 I2C block transactions do not limit the number of bytes transferred
|
| D | fault-codes | 51 fault is only reported on read transactions; the SMBus slave
|
| D | slave-interface | 169 byte-based transactions as the ultimate fallback because this is how the
|
| /linux-4.1.27/drivers/xen/xenbus/ |
| D | xenbus_dev_frontend.c | 101 struct list_head transactions; member
333 list_add(&trans->list, &u->transactions); in xenbus_write_transaction()
336 list_for_each_entry(trans, &u->transactions, list) in xenbus_write_transaction()
339 BUG_ON(&trans->list == &u->transactions); in xenbus_write_transaction()
543 INIT_LIST_HEAD(&u->transactions); in xenbus_file_open()
568 list_for_each_entry_safe(trans, tmp, &u->transactions, list) { in xenbus_file_release()
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | xfs-delayed-logging-design.txt | 27 of transactions, their contents and the log sequence number (LSN) of the
49 transactions. These transaction are known as rolling transactions, and require
67 Another feature of the XFS transaction subsystem is that most transactions are
69 filled (a log buffer can hold multiple transactions) or a synchronous operation
70 forces the log buffers holding the transactions to disk. This means that XFS is
71 doing aggregation of transactions in memory - batching them, if you like - to
81 buffers are full and under IO, then no more transactions can be committed until
83 be to able to issue enough transactions to keep the log buffers full and under
94 transactions A through D are committed to disk in the same log buffer.
132 recovered filesystem is concerned, there may be many thousands of transactions
[all …]
|
| D | ext3.txt | 146 transactions capabilities to ext2. Journaling is done by the Journaling Block
154 The journal supports the transactions start and stop, and in case of a crash,
155 the journal can replay the transactions to quickly put the partition back into
|
| D | ext4.txt | 84 * extent format reduces metadata overhead (RAM, IO for access, transactions)
137 journal_checksum Enable checksumming of the journal transactions.
283 of time to see if any other transactions can
|
| /linux-4.1.27/Documentation/xtensa/ |
| D | atomctl.txt | 16 which can implement RCW transactions. For FPGA cards with an External
27 don't support atomic RCW memory transactions and will likely want to
|
| /linux-4.1.27/Documentation/i2c/busses/ |
| D | i2c-viapro | 69 VT8231), this driver supports I2C block transactions. Such transactions
|
| D | i2c-ali1535 | 24 Additionally, the sequencing of the SMBus transactions has been modified to
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | lm90 | 174 * SMBus PEC support for Write Byte and Receive Byte transactions.
246 not support PEC on all transactions though, so some care must be taken.
257 These transactions will be used to read register values, instead of
264 on SMBus Send Byte transactions in the lm90 driver.
266 PEC on byte data transactions represents a significant increase in bandwidth
269 two transactions will typically mean twice as much delay waiting for
|
| D | lm93 | 26 A "0" allows SMBus block data transactions if the host supports them. A "1"
27 disables SMBus block data transactions. The default is 0.
|
| /linux-4.1.27/Documentation/devicetree/bindings/power_supply/ |
| D | sbs_sbs-battery.txt | 8 - sbs,i2c-retry-count : The number of times to retry i2c transactions on i2c
|
| /linux-4.1.27/drivers/staging/octeon-usb/ |
| D | octeon-hcd.c | 330 struct list_head transactions; member
1131 INIT_LIST_HEAD(&pipe->transactions); in cvmx_usb_open_pipe()
1378 list_first_entry(&pipe->transactions, typeof(*transaction), in cvmx_usb_start_channel_control()
1524 list_first_entry(&pipe->transactions, typeof(*transaction), in cvmx_usb_start_channel()
1874 list_first_entry(&pipe->transactions, typeof(*t), in cvmx_usb_find_ready_pipe()
2121 if (list_empty(&pipe->transactions)) in cvmx_usb_perform_complete()
2188 if (!list_empty(&pipe->transactions)) { in cvmx_usb_submit_transaction()
2189 list_add_tail(&transaction->node, &pipe->transactions); in cvmx_usb_submit_transaction()
2191 list_add_tail(&transaction->node, &pipe->transactions); in cvmx_usb_submit_transaction()
2338 if (list_first_entry(&pipe->transactions, typeof(*transaction), node) == in cvmx_usb_cancel()
[all …]
|
| /linux-4.1.27/Documentation/usb/ |
| D | ehci.txt | 19 (TT) in the hub, which turns low or full speed transactions into
20 high speed "split transactions" that don't waste transfer bandwidth.
81 transactions (interrupt and isochronous transfers). These place some
82 limits on the number of periodic transactions that can be scheduled,
169 so that it's only trying six (or maybe seven) USB transactions each
|
| D | dma.txt | 95 DMA transactions:
|
| D | usbmon.txt | 12 usbmon may not correspond to bus transactions precisely. This is the same
|
| D | usb-serial.txt | 411 The driver was put together by looking at the usb bus transactions
|
| /linux-4.1.27/Documentation/devicetree/bindings/net/ |
| D | brcm,unimac-mdio.txt | 8 larger than 16-bits MDIO transactions
|
| /linux-4.1.27/drivers/staging/ozwpan/ |
| D | README | 23 transactions as this would be rather busy and inefficient. Instead the chapter 9
|
| /linux-4.1.27/Documentation/devicetree/bindings/mtd/ |
| D | fsmc-nand.txt | 21 Only valid for write transactions. Zero means zero cycles,
|
| /linux-4.1.27/drivers/gpu/drm/ |
| D | drm_dp_mst_topology.c | 268 buf[idx] = req->u.i2c_read.transactions[i].i2c_dev_id & 0x7f; in drm_dp_encode_sideband_req()
270 buf[idx] = req->u.i2c_read.transactions[i].num_bytes; in drm_dp_encode_sideband_req()
272 …memcpy(&buf[idx], req->u.i2c_read.transactions[i].bytes, req->u.i2c_read.transactions[i].num_bytes… in drm_dp_encode_sideband_req()
273 idx += req->u.i2c_read.transactions[i].num_bytes; in drm_dp_encode_sideband_req()
275 buf[idx] = (req->u.i2c_read.transactions[i].no_stop_bit & 0x1) << 5; in drm_dp_encode_sideband_req()
276 buf[idx] |= (req->u.i2c_read.transactions[i].i2c_transaction_delay & 0xf); in drm_dp_encode_sideband_req()
2975 msg.u.i2c_read.transactions[i].i2c_dev_id = msgs[i].addr; in drm_dp_mst_i2c_xfer()
2976 msg.u.i2c_read.transactions[i].num_bytes = msgs[i].len; in drm_dp_mst_i2c_xfer()
2977 msg.u.i2c_read.transactions[i].bytes = msgs[i].buf; in drm_dp_mst_i2c_xfer()
|
| /linux-4.1.27/Documentation/rapidio/ |
| D | tsi721.txt | 10 To generate SRIO maintenance transactions this driver uses one of Tsi721 DMA
|
| D | sysfs.txt | 47 the RapidIO maintenance transactions:
|
| D | rapidio.txt | 36 packets (transactions). In the RapidIO subsystem each master port is represented
185 The enumeration and discovery routines use RapidIO maintenance transactions
|
| /linux-4.1.27/Documentation/devicetree/bindings/iommu/ |
| D | samsung,sysmmu.txt | 15 master), but one System MMU can handle transactions from only one peripheral
|
| /linux-4.1.27/drivers/scsi/aic7xxx/ |
| D | Kconfig.aic79xx | 21 This is an upper bound value for the number of tagged transactions
|
| D | Kconfig.aic7xxx | 26 This is an upper bound value for the number of tagged transactions
|
| D | aic7xxx.seq | 362 * when we have outstanding transactions, so we can safely
364 * we start sending out transactions again.
790 * be transferred using memory write and invalidate PCI transactions.
1811 * transactions by first looking at the transaction stored in
1876 * transactions since the SCB may exist in any slot. If we're not
|
| D | aic79xx.seq | 457 * PCI-X mode, we do this to avoid split transactions since
1093 * transactions by first looking at the transaction stored in
1914 * so it can be used for other transactions. On RTI capable controllers,
|
| /linux-4.1.27/Documentation/networking/ |
| D | cxgb.txt | 281 the number of outstanding transactions, via BIOS configuration
285 Total allowed outstanding transactions: 2
296 NOTE: The default setting on most systems is 8 outstanding transactions
|
| D | s2io.txt | 102 max-split-transactions(MOST) and MMRBC (use setpci command).
|
| /linux-4.1.27/include/drm/ |
| D | drm_dp_mst_helper.h | 265 } transactions[DP_REMOTE_I2C_READ_MAX_TRANSACTIONS]; member
|
| /linux-4.1.27/drivers/media/usb/msi2500/ |
| D | msi2500.c | 262 unsigned int i, j, transactions, dst_len = 0; in msi2500_convert_stream() local
266 transactions = src_len / 1024; in msi2500_convert_stream()
268 for (i = 0; i < transactions; i++) { in msi2500_convert_stream()
|
| /linux-4.1.27/Documentation/ |
| D | Intel-IOMMU.txt | 64 The same is true for peer to peer transactions. Hence we reserve the
|
| D | vfio.txt | 56 transactions between devices to reach the IOMMU. Examples of this
394 /* Waiting for pending PCI transactions to be completed and don't
452 [4] In this case the device is below a PCI bridge, so transactions
|
| D | dynamic-debug-howto.txt | 246 will show early Embedded Controller transactions during ACPI setup if
|
| D | DMA-API-HOWTO.txt | 158 support 64-bit addressing (DAC) for all transactions. And at least
|
| D | memory-barriers.txt | 2586 between PCI transactions.
|
| /linux-4.1.27/Documentation/w1/masters/ |
| D | ds2490 | 28 - The number of USB bus transactions could be reduced if w1_reset_send
|
| /linux-4.1.27/Documentation/video4linux/cx2341x/ |
| D | fw-memory.txt | 55 0x1c - always 0x20 or 32, smaller values slow down DMA transactions
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/ |
| D | cci.txt | 7 transactions and manage coherency, TLB invalidations and memory barriers.
|
| D | vexpress.txt | 85 of generating transactions on the configuration bus.
|
| /linux-4.1.27/Documentation/scsi/ |
| D | ChangeLog.sym53c8xx | 41 Earlier chips simply use PCI transactions to access IO
496 since the driver will never performs PCI read transactions, but
497 only PCI write transactions that may be posted.
514 transactions since those early chip revisions may use such on
|
| D | aic7xxx.txt | 49 7. Queuing Registers - Allows queuing of new transactions without
170 the result of some other device issuing PCI transactions
|
| D | sym53c8xx_2.txt | 187 The 896 and 1010 chips support 64 bit PCI transactions and addressing,
188 while the 895A supports 32 bit PCI transactions and 64 bit addressing.
|
| D | ncr53c8xx.txt | 212 The 896 chip supports 64 bit PCI transactions and addressing, while the
213 895A supports 32 bit PCI transactions and 64 bit addressing.
|
| /linux-4.1.27/arch/arm/mach-tegra/ |
| D | sleep-tegra20.S | 405 mov r1, #0 @ unstall all transactions
|
| D | sleep-tegra30.S | 514 mov r1, #0 @ unstall all transactions
|
| /linux-4.1.27/Documentation/arm/ |
| D | vlocks.txt | 159 case. The number of transactions is still fewer than would be
|
| /linux-4.1.27/Documentation/dmaengine/ |
| D | client.txt | 156 The transactions in the pending queue can be activated by calling the
|
| D | provider.txt | 351 additional transactions added to it in the async-tx API
|
| /linux-4.1.27/Documentation/spi/ |
| D | pxa2xx | 15 (pump_transfer) is responsible for queuing SPI transactions and setting up and
|
| D | spi-summary | 451 I/O buffers into a group of protocol transactions. These can
|
| /linux-4.1.27/Documentation/PCI/ |
| D | pci.txt | 541 pci_set_mwi() Enable Memory-Write-Invalidate transactions.
542 pci_clear_mwi() Disable Memory-Write-Invalidate transactions.
603 already do this. I/O Port space guarantees write transactions reach the PCI
|
| D | pcieaer-howto.txt | 21 or on behalf of transactions initiated on the link. PCI Express
|
| D | pci-error-recovery.txt | 371 wild addresses or bogus split transactions due to programming
|
| /linux-4.1.27/arch/arm64/ |
| D | Kconfig | 314 …bool "Cortex-A53: 827319: Data cache clean instructions might cause overlapping transactions to th…
324 interconnect reorders the two transactions.
|
| /linux-4.1.27/arch/powerpc/boot/dts/ |
| D | virtex440-ml510.dts | 347 * that inbound and outbound pci transactions work
|
| /linux-4.1.27/arch/arm/boot/dts/ |
| D | exynos5420.dtsi | 400 * AXI transactions. When this is enabled in the kernel
|
| /linux-4.1.27/drivers/misc/ |
| D | Kconfig | 516 of generating transactions on this bus.
|
| /linux-4.1.27/Documentation/cdrom/ |
| D | ide-cd | 261 properly handle simultaneous transactions on multiple interfaces.
|
| /linux-4.1.27/Documentation/power/ |
| D | devices.txt | 367 At the end of these phases, drivers should have stopped all I/O transactions
|
| /linux-4.1.27/drivers/android/ |
| D | binder.c | 3652 BINDER_DEBUG_ENTRY(transactions);
|
| /linux-4.1.27/Documentation/filesystems/cifs/ |
| D | CHANGES | 689 Active smb transactions should never go negative (fix double FreeXid). Fix
|
| /linux-4.1.27/arch/arm/ |
| D | Kconfig | 1074 situation in which recent store transactions to the L2 cache are lost
|
| /linux-4.1.27/Documentation/RCU/ |
| D | RTFP.txt | 2249 Distributed hash table with transactions, using elliptic
|