/linux/Documentation/devicetree/bindings/powerpc/fsl/ |
H A 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
|
/linux/Documentation/ABI/testing/ |
H A D | sysfs-bus-mdio | 32 Total number of write transactions for this MDIO bus. 40 Total number of read transactions for this MDIO bus. 64 Total number of write transactions for this MDIO bus address. 72 Total number of read transactions for this MDIO bus address.
|
H A D | sysfs-fs-xfs | 25 outstanding transactions in bytes. 35 outstanding transactions, including regrants due to 36 rolling transactions in bytes.
|
H A D | sysfs-driver-fsi-master-gpio | 8 driver performs FSI bus transactions, 1 sets external mode,
|
/linux/Documentation/filesystems/xfs/ |
H A D | xfs-delayed-logging-design.rst | 15 We begin with an overview of transactions in XFS, followed by describing how 17 guarantee forwards progress for long running transactions with finite initial 57 XFS has two types of high level transactions, defined by the type of log space 59 transactions. Permanent transaction reservations can take reservations that span 60 commit boundaries, whilst "one shot" transactions are for a single atomic 64 place. This means that permanent transactions can be used for one-shot 66 transactions. 82 transactions, and the pattern looks like this:: 99 transactions together:: 105 This results in a series of "rolling transactions" where the inode is locked [all …]
|
/linux/sound/firewire/ |
H A D | fcp.c | 187 static LIST_HEAD(transactions); 246 list_add_tail(&t.list, &transactions); in fcp_avc_transaction() 304 list_for_each_entry(t, &transactions, list) { in fcp_bus_reset() 350 list_for_each_entry(t, &transactions, list) { in fcp_response() 396 WARN_ON(!list_empty(&transactions)); in fcp_module_exit()
|
/linux/sound/firewire/fireface/ |
H A D | ff-transaction.c | 40 container_of(callback_data, struct snd_ff, transactions[0]); in finish_transmit_midi0_msg() 49 container_of(callback_data, struct snd_ff, transactions[1]); in finish_transmit_midi1_msg() 108 fw_send_request(fw_dev->card, &ff->transactions[port], tcode, in transmit_midi_msg() 111 callback, &ff->transactions[port]); in transmit_midi_msg()
|
/linux/drivers/net/ethernet/freescale/fman/ |
H A D | Kconfig | 25 read or write transactions into multiple smaller transactions 26 such that more than 17 AXI transactions are in flight from FMAN
|
/linux/Documentation/i2c/ |
H A D | i2c-protocol.rst | 5 This document is an overview of the basic I2C transactions and the kernel 41 Combined transactions 46 They are just like the above transactions, but instead of a stop 53 Modified transactions
|
H A D | dev-interface.rst | 94 transactions (mixing read and write messages in the same transaction) 120 Used only for SMBus transactions. This request only has an effect if the 147 You can do plain I2C transactions by using read(2) and write(2) calls. 151 You can do SMBus level transactions (see documentation file smbus-protocol.rst 168 All these transactions return -1 on failure; you can read errno to see 169 what happened. The 'write' transactions return 0 on success; the 170 'read' transactions return the read value, except for read_block, which 196 checking on future transactions.)
|
H A D | functionality.rst | 72 A typical SMBus-only adapter would list all the SMBus transactions it 90 I2C_FUNC_SMBUS_EMUL includes all the SMBus transactions (with the 91 addition of I2C block transactions) which i2c-core can emulate using 117 and SMBus word data transactions. If not, then the driver won't work on 129 i2c-core will transparently implement SMBus transactions on top of I2C
|
H A D | i2c-address-translators.rst | 15 forwards transactions from upstream to the appropriate downstream port 34 all I2C transactions directed to devices on the child buses. 51 each other. The ATR receives the transactions initiated on bus A and
|
/linux/drivers/firmware/arm_scmi/transports/ |
H A D | Kconfig | 59 transactions on the TX path, answer Y. 61 transport to optionally ask for atomic SCMI transactions and operate 116 transactions on the TX path, answer Y. 119 transport to optionally ask for atomic SCMI transactions and operate
|
/linux/Documentation/arch/powerpc/ |
H A D | transactional_memory.rst | 17 instructions are presented to delimit transactions; transactions are 72 - See the ISA for full documentation of everything that will abort transactions. 90 Care must be taken when relying on syscalls to abort during active transactions 100 Delivery of signals (both sync and async) during transactions provides a second 103 abort transactions. The usual ucontext_t passed to the signal handler 120 However, basic signal handlers don't need to be aware of transactions 203 in parts within transactions.
|
/linux/drivers/gpu/drm/tests/ |
H A D | drm_dp_mst_helper_test.c | 350 .u.i2c_read.transactions = { 452 txin = &IN.transactions[i]; in sideband_msg_req_equal() 453 txout = &OUT.transactions[i]; in sideband_msg_req_equal() 544 kfree(out->u.i2c_read.transactions[i].bytes); in drm_test_dp_mst_sideband_msg_req_decode()
|
/linux/Documentation/arch/xtensa/ |
H A D | atomctl.rst | 20 which can implement RCW transactions. For FPGA cards with an External 31 don't support atomic RCW memory transactions and will likely want to
|
/linux/drivers/xen/xenbus/ |
H A D | xenbus_dev_frontend.c | 102 struct list_head transactions; member 320 list_for_each_entry_safe(trans, tmp, &u->transactions, list) { in xenbus_worker() 356 list_for_each_entry(trans, &u->transactions, list) in xenbus_get_transaction() 463 list_add(&trans->list, &u->transactions); in xenbus_write_transaction() 664 INIT_LIST_HEAD(&u->transactions); in xenbus_file_open()
|
/linux/Documentation/filesystems/ |
H A D | journalling.rst | 31 transactions in the journal and similarly jbd2_journal_load() will 39 by wrapping them into transactions. Additionally you also need to wrap 67 checkpoint all your transactions. 78 journal. Since transactions can't be nested/batched across differing 85 for transactions to complete and be committed from other tasks, so 191 as a whole, and those which are used to manage transactions
|
/linux/Documentation/admin-guide/perf/ |
H A D | alibaba_pmu.rst | 45 receives transactions Host Interface (HIF) which is custom-defined by Synopsys. 46 These transactions are queued internally and scheduled for access while 48 dependencies between the transactions. The DDRCTL in turn issues commands on
|
/linux/Documentation/i2c/busses/ |
H A D | i2c-viapro.rst | 73 VT8231), this driver supports I2C block transactions. Such transactions
|
/linux/Documentation/driver-api/pci/ |
H A D | p2pdma.rst | 10 make P2P transactions tricky to do in a perfectly safe way. 13 transactions between hierarchy domains, and in PCIe, each Root Port 19 domain, and the spec guarantees that all transactions within the 24 memory that is used for P2P transactions needs to be backed by struct
|
/linux/Documentation/networking/device_drivers/ethernet/meta/ |
H A D | fbnic.rst | 58 - ``pcie_ob_rd_dword``: DWORDs transferred in outbound read transactions 61 transactions
|
/linux/Documentation/devicetree/bindings/interrupt-controller/ |
H A D | marvell,icu.txt | 7 requests on input wires to MSG memory mapped transactions to the GIC. 41 transactions.
|
/linux/Documentation/devicetree/bindings/iommu/ |
H A D | iommu.txt | 92 tagging DMA transactions with an address space identifier. By default, 101 accepts a limited number of simultaneous stalled transactions before 103 transactions. 107 transactions have to complete before a time limit. More generally it
|
/linux/Documentation/hwmon/ |
H A D | lm90.rst | 510 * SMBus PEC support for Write Byte and Receive Byte transactions. 515 * SMBus PEC support for Write Byte and Receive Byte transactions. 612 not support PEC on all transactions though, so some care must be taken. 623 These transactions will be used to read register values, instead of 630 on SMBus Send Byte transactions in the lm90 driver. 632 PEC on byte data transactions represents a significant increase in bandwidth 635 two transactions will typically mean twice as much delay waiting for
|