Home
last modified time | relevance | path

Searched refs:Message (Results 1 – 86 of 86) sorted by relevance

/linux-4.4.14/Documentation/devicetree/bindings/net/can/
Dm_can.txt7 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-4.4.14/Documentation/scsi/
Dhptiop.txt13 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 …]
Dadvansys.txt101 Debugging Message Levels:
DChangeLog.megaraid28 > -----Original Message-----
93 > -----Original Message-----
Darcmsr_spec.txt6 ** 1. Message 0 --> InitThread message and return code
/linux-4.4.14/drivers/staging/wilc1000/
Dwilc_msgqueue.c41 Message *pstrMessge = pHandle->pstrMessageList->pstrNext; in wilc_mq_destroy()
60 Message *pstrMessage = NULL; in wilc_mq_send()
73 pstrMessage = kmalloc(sizeof(Message), GFP_ATOMIC); in wilc_mq_send()
92 Message *pstrTailMsg = pHandle->pstrMessageList; in wilc_mq_send()
117 Message *pstrMessage; in wilc_mq_recv()
Dwilc_msgqueue.h20 } Message; typedef
27 Message *pstrMessageList;
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dmpic-msgr.txt1 * 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
Dsrio-rmu.txt1 Message unit node:
39 Message Unit:
/linux-4.4.14/drivers/scsi/pcmcia/
Dsym53c500_cs.c413 | ((curSC->SCp.Message & 0xff) << 8) | (DID_OK << 16); in SYM53C500_intr()
486 curSC->SCp.Message = inb(port_base + SCSI_FIFO); in SYM53C500_intr()
489 DEB(printk("Status = %02x Message = %02x\n", curSC->SCp.Status, curSC->SCp.Message)); in SYM53C500_intr()
491 if (curSC->SCp.Message == SAVE_POINTERS || curSC->SCp.Message == DISCONNECT) { in SYM53C500_intr()
571 data->current_SC->SCp.Message = 0; in SYM53C500_queue_lck()
Dnsp_cs.c227 SCpnt->SCp.Message = 0; in nsp_queuecommand_lck()
1039 ((tmpSC->SCp.Message & 0xff) << 8) | in nspintr()
1137 …if ((tmpSC->SCp.Message == MSG_COMMAND_COMPLETE)) { /* all command complete and return status … in nspintr()
1139 ((tmpSC->SCp.Message & 0xff) << 8) | in nspintr()
1209 nsp_dbg(NSP_DEBUG_INTR, "message=0x%x status=0x%x", tmpSC->SCp.Message, tmpSC->SCp.Status); in nspintr()
1284 tmpSC->SCp.Message = tmp; in nspintr()
1286 nsp_dbg(NSP_DEBUG_INTR, "message=0x%x len=%d", tmpSC->SCp.Message, data->MsgLen); in nspintr()
/linux-4.4.14/drivers/scsi/
DNCR53c406a.c713 current_SC->SCp.Message = 0; in NCR53c406a_queue_lck()
855 | ((current_SC->SCp.Message & 0xff) << 8) | (DID_OK << 16); in NCR53c406a_intr()
939 current_SC->SCp.Message = inb(SCSI_FIFO); in NCR53c406a_intr()
942 DEB(printk("Status = %02x Message = %02x\n", current_SC->SCp.Status, current_SC->SCp.Message)); in NCR53c406a_intr()
944 if (current_SC->SCp.Message == SAVE_POINTERS || current_SC->SCp.Message == DISCONNECT) { in NCR53c406a_intr()
Dfdomain.c1271 current_SC->SCp.Message = inb(port_base + Read_SCSI_Data); in do_fdomain_16x0_intr()
1273 printk( "Message = %x, ", current_SC->SCp.Message ); in do_fdomain_16x0_intr()
1275 if (!current_SC->SCp.Message) ++done; in do_fdomain_16x0_intr()
1277 if (current_SC->SCp.Message) { in do_fdomain_16x0_intr()
1279 current_SC->SCp.Message ); in do_fdomain_16x0_intr()
1401 | ((current_SC->SCp.Message & 0xff) << 8) | (DID_OK << 16) ); in do_fdomain_16x0_intr()
1455 current_SC->SCp.Message = 0; in fdomain_16x0_queue_lck()
Dsym53c416.c399 …current_command->result = (current_command->SCp.Status & 0xFF) | ((current_command->SCp.Message & … in sym53c416_intr_handle()
489 current_command->SCp.Message = inb(base + SCSI_FIFO); in sym53c416_intr_handle()
490 if(current_command->SCp.Message == SAVE_POINTERS || current_command->SCp.Message == DISCONNECT) in sym53c416_intr_handle()
748 current_command->SCp.Message = 0; in sym53c416_queuecommand_lck()
Dmac53c94.c327 cmd->SCp.Message = readb(&regs->fifo); in mac53c94_interrupt()
336 cmd_done(state, (DID_OK << 16) + (cmd->SCp.Message << 8) in mac53c94_interrupt()
Din2000.c1189 cmd->SCp.Message = msg; in in2000_intr()
1332 cmd->SCp.Message = COMMAND_COMPLETE; in in2000_intr()
1343 cmd->result = cmd->SCp.Status | (cmd->SCp.Message << 8); in in2000_intr()
1426 cmd->result = cmd->SCp.Status | (cmd->SCp.Message << 8); in in2000_intr()
1458 cmd->result = cmd->SCp.Status | (cmd->SCp.Message << 8); in in2000_intr()
Dwd33c93.c1007 cmd->SCp.Message = msg; in wd33c93_intr()
1179 cmd->SCp.Message = COMMAND_COMPLETE; in wd33c93_intr()
1194 cmd->SCp.Status | (cmd->SCp.Message << 8); in wd33c93_intr()
1278 cmd->result = cmd->SCp.Status | (cmd->SCp.Message << 8); in wd33c93_intr()
1314 cmd->SCp.Status | (cmd->SCp.Message << 8); in wd33c93_intr()
Daha152x.c924 SCpnt->SCp.Message = 0; in aha152x_internal_queue()
1394 …done(shpnt, (CURRENT_SC->SCp.Status & 0xff) | ((CURRENT_SC->SCp.Message & 0xff) << 8) | (DID_OK <<… in busfree_run()
1397 …done(shpnt, (CURRENT_SC->SCp.Status & 0xff) | ((CURRENT_SC->SCp.Message & 0xff) << 8) | (DID_ABORT… in busfree_run()
1400 …done(shpnt, (CURRENT_SC->SCp.Status & 0xff) | ((CURRENT_SC->SCp.Message & 0xff) << 8) | (DID_RESET… in busfree_run()
1691 CURRENT_SC->SCp.Message = MSGI(0); in msgi_run()
1700 CURRENT_SC->SCp.Message = MSGI(0); in msgi_run()
Dnsp32.c951 SCpnt->SCp.Message = 0; in nsp32_queuecommand_lck()
1681 SCpnt->SCp.Message = 0; in nsp32_busfree_occur()
1686 (SCpnt->SCp.Message << 8) | in nsp32_busfree_occur()
1694 SCpnt->SCp.Message = 4; in nsp32_busfree_occur()
DNCR5380.c2120 cmd->SCp.Message = tmp;
2153 cmd->result = cmd->SCp.Status | (cmd->SCp.Message << 8);
2185 cmd->result = cmd->SCp.Status | (cmd->SCp.Message << 8);
Datari_NCR5380.c2110 cmd->SCp.Message = tmp; in NCR5380_information_transfer()
2153 cmd->result = cmd->SCp.Status | (cmd->SCp.Message << 8); in NCR5380_information_transfer()
2213 cmd->result = cmd->SCp.Status | (cmd->SCp.Message << 8); in NCR5380_information_transfer()
D53c700.scr171 ; Send a message. Message count should be correctly patched
Dmesh.c599 cmd->result += (cmd->SCp.Message << 8); in mesh_done()
1179 cmd->SCp.Message = code; in handle_msgin()
D53c700_d.h_shipped219 ; Send a message. Message count should be correctly patched
DKconfig483 Module for Marvell Universal Message Interface(UMI) driver
/linux-4.4.14/drivers/pci/
DKconfig9 bool "Message Signaled Interrupts (MSI and MSI-X)"
13 This allows device drivers to enable MSI (Message Signaled
14 Interrupts). Message Signaled Interrupts enable a device to
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Darm,scpi.txt1 System Control and Power Interface (SCPI) Message Protocol
5 ("ARM Compute Subsystem SCP: Message Interface Protocols")[0] can be used
23 Clock bindings for the clocks based on SCPI Message Protocol
75 Sensor bindings for the sensors based on SCPI Message Protocol
/linux-4.4.14/net/bluetooth/cmtp/
DKconfig5 CMTP (CAPI Message Transport Protocol) is a transport layer
/linux-4.4.14/Documentation/PCI/
D00-INDEX4 - the Message Signaled Interrupts (MSI) Driver Guide HOWTO and FAQ.
DMSI-HOWTO.txt12 This guide describes the basics of Message Signaled Interrupts (MSIs),
20 A Message Signaled Interrupt is a write from the device to a special
217 device requested (via the Multiple Message Capable register). The MSI
510 Using 'lspci -v' (as root) may show some devices with "MSI", "Message
Dpci.txt380 MSI and MSI-X are PCI capabilities. Both are "Message Signaled Interrupts"
/linux-4.4.14/Documentation/devicetree/bindings/mailbox/
Darm-mhu.txt4 The ARM's Message-Handling-Unit (MHU) is a mailbox controller that has
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/
Dmarvell,armada-370-xp-mpic.txt7 - msi-controller: Identifies the node as an PCI Message Signaled
Darm,gic-v3.txt55 used to route Message Signalled Interrupts (MSI) to the CPUs.
Dmsi.txt4 Message Signaled Interrupts (MSIs) are a class of interrupts generated by a
/linux-4.4.14/Documentation/filesystems/cifs/
Dcifs.txt2 (CIFS) protocol which is the successor to the Server Message Block
/linux-4.4.14/arch/powerpc/boot/dts/fsl/
Dpq3-mpic-message-B.dtsi2 * PQ3 MPIC Message (Group B) device tree stub [ controller @ offset 0x42400 ]
Dqoriq-rmu-0.dtsi2 * QorIQ RIO Message Unit device tree stub [ controller @ offset 0xd3000 ]
Dpq3-rmu-0.dtsi2 * PQ3 RIO Message Unit device tree stub [ controller @ offset 0xd3000 ]
/linux-4.4.14/Documentation/zh_CN/
Demail-clients.txt106 然后在"Message"菜单条目，选择插入文件，接着选取你的补丁文件。还有一个额外的选项，你可以
/linux-4.4.14/drivers/scsi/aic7xxx/
Daic79xx.reg677 * Data Channel Receive Message 0
688 * CMC Receive Message 0
699 * Overlay Receive Message 0
725 * Data Channel Receive Message 1
735 * CMC Receive Message 1
745 * Overlay Receive Message 1
770 * Data Channel Receive Message 2
780 * CMC Receive Message 2
790 * Overlay Receive Message 2
809 * Data Channel Receive Message 3
[all …]
Daic7xxx.seq1353 * Issue an Ignore Wide Residue Message.
1475 * Message out phase. If MSG_OUT is MSG_IDENTIFYFLAG, build a full
1552 * Message in phase. Bytes are read using Automatic PIO mode.
Daic79xx.seq950 * Message out phase. If MSG_OUT is MSG_IDENTIFYFLAG, build a full
1023 * Message in phase. Bytes are read using Automatic PIO mode.
1764 * Issue an Ignore Wide Residue Message.
Daic7xxx.reg1732 /* WDTR Message values */
/linux-4.4.14/include/scsi/
Dscsi_cmnd.h50 volatile int Message; member
/linux-4.4.14/drivers/firmware/
DKconfig12 tristate "ARM System Control and Power Interface (SCPI) Message Protocol"
15 System Control and Power Interface (SCPI) Message Protocol is
/linux-4.4.14/Documentation/
Demail-clients.txt84 To insert a patch use Message->Insert File (CTRL+i) or an external editor.
125 Then from the "Message" menu item, select insert file and choose your patch.
277 - "View" > "Message Body As" > "Plain Text"
Dmd-cluster.txt48 3.1 Message Types
68 3.2.2 Message: The lock resource which carries the data to
DIntel-IOMMU.txt76 Boot Message Sample
DIPMI.txt239 The Upper Layer Interface (Message Handler)
DSubmittingPatches163 redirector with a Message-Id, to ensure that the links cannot become
Ddevices.txt437 220 = /dev/mptctl Message passing technology (MPT) control
Dkernel-parameters.txt88 MSI Message Signaled Interrupts (PCI).
/linux-4.4.14/Documentation/networking/
Dxfrm_sync.txt33 1) Message Structure
119 4) Message types
Dnetlink_mmap.txt237 Message reception:
300 Message transmission:
De100.txt82 Event Log Message Level: The driver uses the message level flag to log events
Drds.txt167 Message header
Dcs89x0.txt596 5.) Any Error Message displayed.
Dcan.txt229 reason the CAN interface driver can generate so called Error Message
514 called Error Message Frames that can optionally be passed to the user
/linux-4.4.14/net/bluetooth/
DKconfig32 CMTP Module (CAPI Message Transport Protocol)
/linux-4.4.14/drivers/message/fusion/
DKconfig6 Say Y here to get to see options for Fusion Message
/linux-4.4.14/fs/cifs/
DKconfig16 (CIFS) protocol which is the successor to the Server Message Block
179 This enables support for the Server Message Block version 2
/linux-4.4.14/drivers/scsi/fnic/
Dfnic.h97 #define CMD_ABTS_STATUS(Cmnd) ((Cmnd)->SCp.Message)
/linux-4.4.14/Documentation/filesystems/pohmelfs/
Ddesign_notes.txt1 POHMELFS: Parallel Optimized Host Message Exchange Layered File System.
/linux-4.4.14/Documentation/input/
Dsentelic.txt123 Byte 2: Message Type => 0x5A (Enable/Disable status packet)
125 Byte 3: Message Type => 0x00 (Disabled)
202 Byte 2: Message Type => 0xB7 (Multi Finger, Multi Coordinate mode)
296 Byte 2: Message Type => 0xB7 (Multi Finger, Multi Coordinate mode)
400 Byte 2: Message type:
/linux-4.4.14/arch/x86/crypto/
Dsha512-avx-asm.S76 # Message Schedule
102 # Message Schedule (stack frame)
Dsha512-ssse3-asm.S99 # Message Schedule (stack frame)
/linux-4.4.14/drivers/clk/
DKconfig70 This driver uses SCPI Message Protocol to interact with the
/linux-4.4.14/drivers/scsi/csiostor/
Dcsio_scsi.c169 if (likely(scmnd->SCp.Message == 0)) { in csio_scsi_fcp_cmnd()
188 fcp_cmnd->fc_tm_flags = (uint8_t)scmnd->SCp.Message; in csio_scsi_fcp_cmnd()
1857 cmnd->SCp.Message = 0; in csio_queuecommand()
2130 cmnd->SCp.Message = FCP_TMF_LUN_RESET; in csio_eh_lun_reset_handler()
/linux-4.4.14/drivers/cpufreq/
DKconfig.arm210 This driver uses SCPI Message Protocol driver to interact with the
/linux-4.4.14/drivers/scsi/arm/
Dfas216.c1563 info->scsi.SCp.Message = fas216_readb(info, REG_FF); in fas216_funcdone_intr()
2004 result, SCpnt->SCp.Message, SCpnt->SCp.Status); in fas216_rq_sns_done()
2038 SCpnt->result = result << 16 | info->scsi.SCp.Message << 8 | in fas216_std_done()
2109 SCpnt->SCp.Message = 0; in fas216_std_done()
Dacornscsi.c805 SCpnt->result = result << 16 | host->scsi.SCp.Message << 8 | host->scsi.SCp.Status; in acornscsi_done()
1504 host->scsi.SCp.Message = message[0]; in acornscsi_message()
/linux-4.4.14/Documentation/x86/
Dkernel-stacks108 Adapted from Ingo's mail, Message-ID: <20150521101614.GA10889@gmail.com>:
/linux-4.4.14/Documentation/w1/
Dw1.netlink4 Message types.
/linux-4.4.14/Documentation/devicetree/bindings/pci/
Dmvebu-pci.txt18 - msi-parent: Link to the hardware entity that serves as the Message
/linux-4.4.14/Documentation/device-mapper/
Dcache-policies.txt42 Message and constructor argument pairs are:
Ddm-raid.txt199 Message Interface
/linux-4.4.14/Documentation/isdn/
DREADME114 limit is 2000. You will get NO Error-Message,
221 Bit 6: 0 = Special RUNG Message off
222 1 = Special RUNG Message on
DINTERFACE.CAPI298 CAPIMSG_MSGID(m) CAPIMSG_SETMSGID(m, msgid) Message Number (u16)
/linux-4.4.14/crypto/
DKconfig246 Support for Galois/Counter Mode (GCM) and Galois Message
365 Cipher-based Message Authentication Code (CMAC) specified by
376 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
/linux-4.4.14/Documentation/usb/
DWUSB-Design-overview.txt433 *NOTIFICATION* -- Message coming in the NEEP as response to something.
/linux-4.4.14/Documentation/security/
Dcredentials.txt43 - Message queues
/linux-4.4.14/init/
DKconfig243 bool "POSIX Message Queues"
/linux-4.4.14/Documentation/sound/alsa/
DALSA-Configuration.txt890 enable_msi - Enable Message Signaled Interrupt (MSI) (default = off)
/linux-4.4.14/Documentation/RCU/
DRTFP.txt937 ,note="Message ID: 20031222180114.GA2248@in.ibm.com"
/linux-4.4.14/
DMAINTAINERS9408 SYSTEM CONTROL & POWER INTERFACE (SCPI) Message Protocol drivers