Home
last modified time | relevance | path

Searched refs:IOP (Results 1 – 21 of 21) sorted by relevance

/linux-4.1.27/Documentation/scsi/
Dhptiop.txt6 For RR44xx Intel IOP based adapters, the controller IOP is accessed via PCI BAR0 and BAR2:
25 For Intel IOP based adapters, the controller IOP is accessed via PCI BAR0:
40 For Marvell not Frey IOP based adapters, the IOP is accessed via PCI BAR0 and BAR1:
58 For Marvell Frey IOP based adapters, the IOP is accessed via PCI BAR0 and BAR1:
61 0x0 IOP configuration information.
85 A request packet can be allocated in either IOP or host memory.
93 relative to the IOP BAR0.
99 - Post the packet to IOP by writing it to inbound queue. For requests
100 allocated in IOP memory, write the offset to inbound queue port. For
104 - The IOP process the request. When the request is completed, it
[all …]
DChangeLog.megaraid_sas599 i. Support for 1078 type (ppc IOP) controller, device id : 0x60 added.
/linux-4.1.27/drivers/staging/i2o/
DREADME.ioctl25 II. IOP Access
33 III. Determining the IOP Count
43 This function returns the system's active IOP table. count should
46 IOP unit is active, and NULL if it is inactive or non-existent.
63 u32 iop; /* IOP unit number */
70 This function returns the Hardware Resource Table of the IOP specified
80 ENXIO Invalid IOP number
92 u32 iop; /* IOP unit number */
99 This function returns the Logical Configuration Table of the IOP specified
109 ENXIO Invalid IOP number
[all …]
DREADME78 o PCI IOP's without interrupts are not supported yet
DKconfig13 processor (IOP), thus allowing high speeds since the CPU does not
/linux-4.1.27/drivers/scsi/pm8001/
Dpm8001_defs.h101 IOP, /* IO processor */ enumerator
Dpm8001_init.c272 pm8001_ha->memoryMap.region[IOP].num_elements = 1; in pm8001_alloc()
273 pm8001_ha->memoryMap.region[IOP].element_size = PM8001_EVENT_LOG_SIZE; in pm8001_alloc()
274 pm8001_ha->memoryMap.region[IOP].total_len = PM8001_EVENT_LOG_SIZE; in pm8001_alloc()
275 pm8001_ha->memoryMap.region[IOP].alignment = 32; in pm8001_alloc()
Dpm8001_ctl.c426 (*(u32 *)((u8*)pm8001_ha->memoryMap.region[IOP].virt_ptr + (r) * 32 \ in pm8001_ctl_iop_log_show()
Dpm80xx_hwi.c480 pm8001_ha->memoryMap.region[IOP].phys_addr_hi; in init_default_table_values()
482 pm8001_ha->memoryMap.region[IOP].phys_addr_lo; in init_default_table_values()
Dpm8001_hwi.c215 pm8001_ha->memoryMap.region[IOP].phys_addr_hi; in init_default_table_values()
217 pm8001_ha->memoryMap.region[IOP].phys_addr_lo; in init_default_table_values()
/linux-4.1.27/Documentation/watchdog/
Dhpwdt.txt78 ILO IOP NMI 2Ah
/linux-4.1.27/drivers/macintosh/
DKconfig42 bool "Include IOP (IIfx/Quadra 9x0) ADB driver"
45 The I/O Processor (IOP) is an Apple custom IC designed to provide
/linux-4.1.27/Documentation/PCI/
Dpci.txt46 Request MMIO/IOP resources
61 Release MMIO/IOP resources
242 Request MMIO/IOP resources
292 3.2 Request MMIO/IOP resources
/linux-4.1.27/drivers/dma/
DKconfig81 tristate "Intel IOP ADMA support"
86 Enable support for the Intel(R) IOP Series RAID engines.
/linux-4.1.27/Documentation/s390/
DDebugging390.txt1369 Input Output Processors (IOP's) are responsible for communicating between
1374 IOP's can use one or more links ( known as channel paths ) to talk to each
1392 | IOP | IOP | IOP |
1411 IOP = IP Processor
/linux-4.1.27/arch/cris/arch-v32/drivers/
DKconfig355 # suggested uniquely) when an IOP driver emerges for "real" MMC/SD
/linux-4.1.27/fs/proc/
Dbase.c116 #define NOD(NAME, MODE, IOP, FOP, OP) { \ argument
120 .iop = IOP, \
/linux-4.1.27/drivers/watchdog/
DKconfig301 tristate "IOP Watchdog"
311 affect both cores and the peripherals of the IOP. The ATU-X
/linux-4.1.27/drivers/gpio/
DKconfig213 tristate "Intel IOP GPIO"
/linux-4.1.27/
DCREDITS3238 D: XScale(IOP, IXP) porting and other random ARM bits
DMAINTAINERS5176 INTEL IOP-ADMA DMA DRIVER