Searched refs:Message (Results 1 – 25 of 115) sorted by relevance
12345
| /Linux-v5.4/Documentation/driver-api/soundwire/ |
| D | locking.rst | 11 - Message lock
26 Message lock
38 Message transfer.
42 a. Acquire Message lock.
47 c. Release Message lock
59 <-------------------------------+ a. Acquire Message lock
62 +-------------------------------> c. Release Message lock
76 a. Acquire Message lock.
81 c. Release Message lock.
98 <-------------------------------+ a. Acquire Message lock
[all …]
|
| /Linux-v5.4/Documentation/crypto/ |
| D | api-digest.rst | 1 Message Digest Algorithm Definitions
5 :doc: Message Digest Algorithm Definitions
10 Asynchronous Message Digest API
14 :doc: Asynchronous Message Digest API
28 Synchronous Message Digest API
32 :doc: Synchronous Message Digest API
|
| /Linux-v5.4/Documentation/devicetree/bindings/net/can/ |
| D | m_can.txt | 7 registers map and Message RAM
18 - bosch,mram-cfg : Message RAM configuration data.
19 Multiple M_CAN instances can share the same Message
21 number in Message RAM is also configurable,
23 private Message RAM are used by this M_CAN controller.
28 The 'offset' is an address offset of the Message RAM
30 usually set to 0x0 if you're using a private Message
43 Please refer to 2.4.1 Message RAM Configuration in
|
| /Linux-v5.4/Documentation/scsi/ |
| D | hptiop.txt | 13 0x10 Inbound Message Register 0
14 0x14 Inbound Message Register 1
15 0x18 Outbound Message Register 0
16 0x1C Outbound Message Register 1
28 0x10 Inbound Message Register 0
29 0x14 Inbound Message Register 1
30 0x18 Outbound Message Register 0
31 0x1C Outbound Message Register 1
53 0x10 Inbound Message Register
54 0x14 Outbound Message Register
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/mailbox/ |
| D | ti,message-manager.txt | 1 Texas Instruments' Message Manager Driver
4 The Texas Instruments' Message Manager is a mailbox controller that has
5 configurable queues selectable at SoC(System on Chip) integration. The Message
10 Message Manager Device Node:
|
| D | ti,secure-proxy.txt | 6 Message manager is broken up into different address regions that are
11 Message Manager Device Node:
|
| D | arm-mhu.txt | 4 The ARM's Message-Handling-Unit (MHU) is a mailbox controller that has
|
| /Linux-v5.4/Documentation/virt/kvm/devices/ |
| D | vm.txt | 132 u8 kmac[16]; # valid with Message-Security-Assist
133 u8 kmc[16]; # valid with Message-Security-Assist
134 u8 km[16]; # valid with Message-Security-Assist
135 u8 kimd[16]; # valid with Message-Security-Assist
136 u8 klmd[16]; # valid with Message-Security-Assist
137 u8 pckmo[16]; # valid with Message-Security-Assist-Extension 3
138 u8 kmctr[16]; # valid with Message-Security-Assist-Extension 4
139 u8 kmf[16]; # valid with Message-Security-Assist-Extension 4
140 u8 kmo[16]; # valid with Message-Security-Assist-Extension 4
141 u8 pcc[16]; # valid with Message-Security-Assist-Extension 4
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/arm/ |
| D | amlogic,scpi.txt | 1 System Control and Power Interface (SCPI) Message Protocol
20 Sensor bindings for the sensors based on SCPI Message Protocol
|
| D | juno,scpi.txt | 1 System Control and Power Interface (SCPI) Message Protocol
17 Sensor bindings for the sensors based on SCPI Message Protocol
|
| D | arm,scmi.txt | 1 System Control and Management Interface (SCMI) Message Protocol
46 Clock/Performance bindings for the clocks/OPPs based on SCMI Message Protocol
54 Power domain bindings for the power domains based on SCMI Message Protocol
64 Sensor bindings for the sensors based on SCMI Message Protocol
76 Reset signal bindings for the reset domains based on SCMI Message Protocol
|
| D | arm,scpi.txt | 1 System Control and Power Interface (SCPI) Message Protocol
5 ("ARM Compute Subsystem SCP: Message Interface Protocols")[0] can be used
26 Clock bindings for the clocks based on SCPI Message Protocol
74 Sensor bindings for the sensors based on SCPI Message Protocol
87 Power domain bindings for the power domains based on SCPI Message Protocol
|
| /Linux-v5.4/Documentation/devicetree/bindings/arm/freescale/ |
| D | fsl,scu.txt | 65 Power domain bindings based on SCU Message Protocol
82 Clock bindings based on SCU Message Protocol
103 Pinctrl bindings based on SCU Message Protocol
130 RTC bindings based on SCU Message Protocol
136 OCOTP bindings based on SCU Message Protocol
150 Watchdog bindings based on SCU Message Protocol
|
| /Linux-v5.4/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpic-msgr.txt | 1 * FSL MPIC Message Registers
50 // Message registers 0 and 2 in this block can receive interrupts on
59 // Message registers 0 and 2 in this block can receive interrupts on
|
| /Linux-v5.4/drivers/scsi/pcmcia/ |
| D | sym53c500_cs.c | 404 | ((curSC->SCp.Message & 0xff) << 8) | (DID_OK << 16); in SYM53C500_intr()
477 curSC->SCp.Message = inb(port_base + SCSI_FIFO); in SYM53C500_intr()
480 DEB(printk("Status = %02x Message = %02x\n", curSC->SCp.Status, curSC->SCp.Message)); in SYM53C500_intr()
482 if (curSC->SCp.Message == SAVE_POINTERS || curSC->SCp.Message == DISCONNECT) { in SYM53C500_intr()
562 data->current_SC->SCp.Message = 0; in SYM53C500_queue_lck()
|
| D | nsp_cs.c | 227 SCpnt->SCp.Message = 0; in nsp_queuecommand_lck()
1039 ((tmpSC->SCp.Message & 0xff) << 8) | in nspintr()
1138 if (tmpSC->SCp.Message == MSG_COMMAND_COMPLETE) { in nspintr()
1140 ((tmpSC->SCp.Message & 0xff) << 8) | in nspintr()
1210 nsp_dbg(NSP_DEBUG_INTR, "message=0x%x status=0x%x", tmpSC->SCp.Message, tmpSC->SCp.Status); in nspintr()
1285 tmpSC->SCp.Message = tmp; in nspintr()
1287 nsp_dbg(NSP_DEBUG_INTR, "message=0x%x len=%d", tmpSC->SCp.Message, data->MsgLen); in nspintr()
|
| /Linux-v5.4/drivers/media/pci/ddbridge/ |
| D | Kconfig | 36 bool "Enable Message Signaled Interrupts (MSI) per default (EXPERIMENTAL)"
40 Use PCI MSI (Message Signaled Interrupts) per default. Enabling this
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | message-based.rst | 1 Message-based devices
|
| /Linux-v5.4/net/bluetooth/cmtp/ |
| D | Kconfig | 6 CMTP (CAPI Message Transport Protocol) is a transport layer
|
| /Linux-v5.4/drivers/scsi/ |
| D | fdomain.c | 335 cmd->SCp.Message = inb(fd->base + REG_SCSI_DATA); in fdomain_work()
336 if (!cmd->SCp.Message) in fdomain_work()
363 ((cmd->SCp.Message & 0xff) << 8) | in fdomain_work()
403 cmd->SCp.Message = 0; in fdomain_queue()
|
| /Linux-v5.4/Documentation/fault-injection/ |
| D | nvme-fault-injection.rst | 30 Message from dmesg::
88 Message from dmesg::
137 Message from dmesg::
|
| /Linux-v5.4/Documentation/devicetree/bindings/interrupt-controller/ |
| D | al,alpine-msix.txt | 10 - msi-controller: identifies the node as an PCI Message Signaled Interrupt
|
| D | marvell,odmi-controller.txt | 4 Some Marvell SoCs have an On-Die Message Interrupt (ODMI) controller
|
| /Linux-v5.4/drivers/pci/ |
| D | Kconfig | 40 bool "Message Signaled Interrupts (MSI and MSI-X)"
43 This allows device drivers to enable MSI (Message Signaled
44 Interrupts). Message Signaled Interrupts enable a device to
|
| /Linux-v5.4/drivers/firmware/ |
| D | Kconfig | 10 bool "ARM System Control and Management Interface (SCMI) Message Protocol"
44 tristate "ARM System Control and Power Interface (SCPI) Message Protocol"
48 System Control and Power Interface (SCPI) Message Protocol is
262 tristate "TI System Control Interface (TISCI) Message Protocol"
265 TI System Control Interface (TISCI) Message Protocol is used to manage
|
12345
