Home
last modified time | relevance | path

Searched refs:transactions (Results 1 – 87 of 87) sorted by relevance

/linux-4.4.14/tools/perf/Documentation/
Ditrace.txt5 x synthesize transactions events
23 transactions events can be specified.
26 instructions or transactions events can be specified.
Dintel-bts.txt54 "instructions" events nor "transactions" events (and consequently call
Dintel-pt.txt668 x synthesize "transactions" events
682 "Transactions" events correspond to the start or end of transactions. The
717 transactions events can be specified. e.g.
723 transactions events can be specified. e.g.
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dsrio.txt64 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
Draideng.txt64 transactions from this JR and than be able to do address
Dmsi-pic.txt97 intercepts transactions and reroutes them to the true physical address.
Dsrio-rmu.txt32 The LIODN value is associated with all RMU transactions
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-fs-xfs25 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.4.14/sound/firewire/
Dfcp.c181 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.4.14/Documentation/devicetree/bindings/mfd/
Dcros-ec.txt26 additional processing time in order to accept new transactions. If the delay
27 between transactions is not long enough the EC may not be able to respond
28 properly to subsequent transactions and cause them to hang. This property
29 specifies the delay, in usecs, introduced between transactions to account
/linux-4.4.14/Documentation/powerpc/
Dtransactional_memory.txt16 instructions are presented to delimit transactions; transactions are
71 - See the ISA for full documentation of everything that will abort transactions.
89 Care must be taken when relying on syscalls to abort during active transactions
99 Delivery of signals (both sync and async) during transactions provides a second
102 abort transactions. The usual ucontext_t passed to the signal handler
119 However, basic signal handlers don't need to be aware of transactions
198 in parts within transactions.
Dpci_iov_resource_on_powernv.txt29 The interesting part is how the various PCIe transactions (MMIO, DMA, ...)
/linux-4.4.14/Documentation/filesystems/pohmelfs/
Ddesign_notes.txt28 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.4.14/Documentation/i2c/
Dfunctionality64 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
Ddev-interface90 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.)
Di2c-protocol37 Combined transactions
42 They are just like the above transactions, but instead of a stop bit P
49 Modified transactions
Dwriting-clients341 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
Dsmbus-protocol243 The following I2C block transactions are supported by the
247 I2C block transactions do not limit the number of bytes transferred
Dfault-codes51 fault is only reported on read transactions; the SMBus slave
Dslave-interface177 byte-based transactions as the ultimate fallback because this is how the
/linux-4.4.14/drivers/xen/xenbus/
Dxenbus_dev_frontend.c101 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.4.14/Documentation/filesystems/
Dxfs-delayed-logging-design.txt27 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 …]
Dext4.txt84 * 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.4.14/Documentation/xtensa/
Datomctl.txt16 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.4.14/Documentation/i2c/busses/
Di2c-viapro69 VT8231), this driver supports I2C block transactions. Such transactions
Di2c-ali153524 Additionally, the sequencing of the SMBus transactions has been modified to
/linux-4.4.14/Documentation/devicetree/bindings/pci/
Darm,juno-r1-pcie.txt9 - dma-coherent: The host controller bridges the AXI transactions into PCIe bus
/linux-4.4.14/Documentation/hwmon/
Dlm90174 * 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
Dlm9326 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.4.14/Documentation/devicetree/bindings/power_supply/
Dsbs_sbs-battery.txt8 - sbs,i2c-retry-count : The number of times to retry i2c transactions on i2c
/linux-4.4.14/drivers/staging/octeon-usb/
Docteon-hcd.c330 struct list_head transactions; member
1137 INIT_LIST_HEAD(&pipe->transactions); in cvmx_usb_open_pipe()
1384 list_first_entry(&pipe->transactions, typeof(*transaction), in cvmx_usb_start_channel_control()
1530 list_first_entry(&pipe->transactions, typeof(*transaction), in cvmx_usb_start_channel()
1880 list_first_entry(&pipe->transactions, typeof(*t), in cvmx_usb_find_ready_pipe()
2127 if (list_empty(&pipe->transactions)) in cvmx_usb_perform_complete()
2194 if (!list_empty(&pipe->transactions)) { in cvmx_usb_submit_transaction()
2195 list_add_tail(&transaction->node, &pipe->transactions); in cvmx_usb_submit_transaction()
2197 list_add_tail(&transaction->node, &pipe->transactions); in cvmx_usb_submit_transaction()
2344 if (list_first_entry(&pipe->transactions, typeof(*transaction), node) == in cvmx_usb_cancel()
[all …]
/linux-4.4.14/Documentation/usb/
Dehci.txt19 (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
Ddma.txt95 DMA transactions:
Dusbmon.txt12 usbmon may not correspond to bus transactions precisely. This is the same
Dusb-serial.txt411 The driver was put together by looking at the usb bus transactions
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dbrcm,unimac-mdio.txt8 larger than 16-bits MDIO transactions
/linux-4.4.14/Documentation/devicetree/bindings/mtd/
Dfsmc-nand.txt21 Only valid for write transactions. Zero means zero cycles,
/linux-4.4.14/drivers/gpu/drm/
Ddrm_dp_mst_topology.c268 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()
2987 msg.u.i2c_read.transactions[i].i2c_dev_id = msgs[i].addr; in drm_dp_mst_i2c_xfer()
2988 msg.u.i2c_read.transactions[i].num_bytes = msgs[i].len; in drm_dp_mst_i2c_xfer()
2989 msg.u.i2c_read.transactions[i].bytes = msgs[i].buf; in drm_dp_mst_i2c_xfer()
/linux-4.4.14/Documentation/rapidio/
Dtsi721.txt10 To generate SRIO maintenance transactions this driver uses one of Tsi721 DMA
Dsysfs.txt47 the RapidIO maintenance transactions:
Drapidio.txt36 packets (transactions). In the RapidIO subsystem each master port is represented
185 The enumeration and discovery routines use RapidIO maintenance transactions
/linux-4.4.14/Documentation/devicetree/bindings/iommu/
Dsamsung,sysmmu.txt15 master), but one System MMU can handle transactions from only one peripheral
/linux-4.4.14/drivers/scsi/aic7xxx/
DKconfig.aic79xx21 This is an upper bound value for the number of tagged transactions
DKconfig.aic7xxx26 This is an upper bound value for the number of tagged transactions
Daic7xxx.seq362 * 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
Daic79xx.seq457 * 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.4.14/Documentation/networking/
Dcxgb.txt281 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
Ds2io.txt102 max-split-transactions(MOST) and MMRBC (use setpci command).
/linux-4.4.14/include/drm/
Ddrm_dp_mst_helper.h265 } transactions[DP_REMOTE_I2C_READ_MAX_TRANSACTIONS]; member
/linux-4.4.14/drivers/media/usb/msi2500/
Dmsi2500.c261 unsigned int i, j, transactions, dst_len = 0; in msi2500_convert_stream() local
265 transactions = src_len / 1024; in msi2500_convert_stream()
267 for (i = 0; i < transactions; i++) { in msi2500_convert_stream()
/linux-4.4.14/Documentation/
DIntel-IOMMU.txt64 The same is true for peer to peer transactions. Hence we reserve the
Dvfio.txt56 transactions between devices to reach the IOMMU. Examples of this
408 /* Waiting for pending PCI transactions to be completed and don't
508 [4] In this case the device is below a PCI bridge, so transactions
Ddynamic-debug-howto.txt246 will show early Embedded Controller transactions during ACPI setup if
DDMA-API-HOWTO.txt158 support 64-bit addressing (DAC) for all transactions. And at least
Dmemory-barriers.txt2541 between PCI transactions.
/linux-4.4.14/Documentation/w1/masters/
Dds249028 - The number of USB bus transactions could be reduced if w1_reset_send
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dl2cc.txt72 non-cacheable transactions" into "cacheable no allocate" (for reads) or
Dcci.txt7 transactions and manage coherency, TLB invalidations and memory barriers.
Dvexpress.txt85 of generating transactions on the configuration bus.
/linux-4.4.14/Documentation/video4linux/cx2341x/
Dfw-memory.txt55 0x1c - always 0x20 or 32, smaller values slow down DMA transactions
/linux-4.4.14/Documentation/networking/dsa/
Dbcm_sf2.txt72 transactions, since they are at the same address (30), resulting in some kind of
/linux-4.4.14/tools/perf/util/
Dauxtrace.h77 bool transactions; member
Dauxtrace.c936 synth_opts->transactions = true; in itrace_synth_opts__set_default()
1017 synth_opts->transactions = true; in itrace_parse_synth_opts()
Dintel-pt.c1894 if (pt->synth_opts.transactions) { in intel_pt_synth_events()
/linux-4.4.14/Documentation/scsi/
DChangeLog.sym53c8xx41 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
Daic7xxx.txt49 7. Queuing Registers - Allows queuing of new transactions without
170 the result of some other device issuing PCI transactions
Dsym53c8xx_2.txt187 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.
Dncr53c8xx.txt212 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.4.14/arch/arm/mach-tegra/
Dsleep-tegra20.S405 mov r1, #0 @ unstall all transactions
Dsleep-tegra30.S514 mov r1, #0 @ unstall all transactions
/linux-4.4.14/Documentation/arm/
Dvlocks.txt159 case. The number of transactions is still fewer than would be
/linux-4.4.14/Documentation/spi/
Dpxa2xx15 (pump_transfer) is responsible for queuing SPI transactions and setting up and
Dspi-summary451 I/O buffers into a group of protocol transactions. These can
/linux-4.4.14/Documentation/dmaengine/
Dclient.txt156 The transactions in the pending queue can be activated by calling the
/linux-4.4.14/Documentation/PCI/
Dpci.txt541 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
Dpcieaer-howto.txt21 or on behalf of transactions initiated on the link. PCI Express
Dpci-error-recovery.txt371 wild addresses or bogus split transactions due to programming
/linux-4.4.14/arch/arm64/
DKconfig238 …bool "Cortex-A53: 827319: Data cache clean instructions might cause overlapping transactions to th…
248 interconnect reorders the two transactions.
/linux-4.4.14/arch/powerpc/boot/dts/
Dvirtex440-ml510.dts347 * that inbound and outbound pci transactions work
/linux-4.4.14/arch/arm/boot/dts/
Dexynos5420.dtsi389 * AXI transactions. When this is enabled in the kernel
/linux-4.4.14/drivers/misc/
DKconfig526 of generating transactions on this bus.
/linux-4.4.14/Documentation/cdrom/
Dide-cd261 properly handle simultaneous transactions on multiple interfaces.
/linux-4.4.14/Documentation/power/
Ddevices.txt374 At the end of these phases, drivers should have stopped all I/O transactions
/linux-4.4.14/drivers/android/
Dbinder.c3652 BINDER_DEBUG_ENTRY(transactions);
/linux-4.4.14/Documentation/filesystems/cifs/
DCHANGES689 Active smb transactions should never go negative (fix double FreeXid). Fix
/linux-4.4.14/arch/arm/
DKconfig1087 situation in which recent store transactions to the L2 cache are lost
/linux-4.4.14/Documentation/RCU/
DRTFP.txt2249 Distributed hash table with transactions, using elliptic