| /linux/Documentation/devicetree/bindings/media/ |
| H A D | microchip,csi2dc.yaml | 16 IDI interface or from a parallel bus interface.
17 It filters IDI packets based on their data type and virtual channel
21 IDI interface is Synopsys proprietary.
30 32-bit IDI interface or a parallel interface.
143 # and the input is received from Synopsys IDI interface
156 csi2dc_in: endpoint { /* input from IDI interface */
172 # and the input is received from Synopsys IDI interface
188 csi2dc_input: endpoint { /* input from IDI interface */
|
| /linux/drivers/gpio/ |
| H A D | gpio-104-idi-48.c | 3 * GPIO driver for the ACCES 104-IDI-48 family
6 * This driver supports the following ACCES devices: 104-IDI-48A,
7 * 104-IDI-48AC, 104-IDI-48B, and 104-IDI-48BC.
29 MODULE_PARM_DESC(base, "ACCES 104-IDI-48 base addresses");
34 MODULE_PARM_DESC(irq, "ACCES 104-IDI-48 interrupt line numbers");
182 .name = "104-idi-48"
188 MODULE_DESCRIPTION("ACCES 104-IDI-48 GPIO driver");
|
| H A D | Kconfig | 983 tristate "ACCES 104-IDI-48 GPIO support"
991 Enables GPIO support for the ACCES 104-IDI-48 family (104-IDI-48A,
992 104-IDI-48AC, 104-IDI-48B, 104-IDI-48BC). The base port addresses for
1855 PCIe-IDI-24, PCIe-IDO-24, PCIe-IDIO-12). An interrupt is generated
|
| /linux/drivers/mtd/ |
| H A D | ssfdc.c | 24 int cis_block; /* block n. containing CIS/IDI */
96 /* These bytes are the signature for the CIS/IDI sector */
116 * Look for CIS/IDI sector on the first GOOD block (give up after 4 bad in get_valid_cis_sector()
128 "SSFDC_RO:can't read CIS/IDI sector\n"); in get_valid_cis_sector()
134 pr_debug("SSFDC_RO: CIS/IDI sector not found" in get_valid_cis_sector()
293 /* Check for SSDFC format by reading CIS/IDI sector */ in ssfdcr_add_mtd()
|
| /linux/drivers/comedi/drivers/ |
| H A D | adl_pci7x3x.c | 86 .nsubdevs = 4, /* IDI, IDO, IRQ_IDI0, IRQ_IDI1 */
234 /* enable LINTi1 == IDI sdi[0] Ch 0 IRQ ActHigh */ in adl_pci7x3x_asy_cmd()
237 /* enable LINTi2 == IDI sdi[0] Ch 1 IRQ ActHigh */ in adl_pci7x3x_asy_cmd()
381 /* 0x52 PCI + IDI Ch 1 Ch 0 IRQ Off ActHigh */ in adl_pci7x3x_auto_attach()
|
| H A D | adv_pci_dio.c | 115 /* DI, IDI, DO, IDO, ID, IRQ_DI0, IRQ_DI1, IRQ_IDI0, IRQ_IDI1 */
|
| /linux/drivers/media/platform/microchip/ |
| H A D | Kconfig | 57 that converts IDI interface byte stream to a parallel pixel stream.
|
| /linux/drivers/usb/storage/ |
| H A D | ene_ub6250.c | 171 #define MS_SYSENT_TYPE_CIS_IDI 0x0a /* CIS/IDI */
389 struct ms_bootblock_idi idi; member
391 } idi; member
1033 } else if (i == 1) { /* CIS/IDI */ in ms_lib_process_bootblock()
1034 struct ms_bootblock_idi *idi; in ms_lib_process_bootblock() local
1049 … idi = &((struct ms_bootblock_cis_idi *)(PageBuffer + (EntryOffset % MS_BYTES_PER_PAGE)))->idi.idi; in ms_lib_process_bootblock()
1050 if (le16_to_cpu(idi->wIDIgeneralConfiguration) != MS_IDI_GENERAL_CONF) in ms_lib_process_bootblock()
1053 info->MS_Lib.BytesPerSector = le16_to_cpu(idi->wIDIbytesPerSector); in ms_lib_process_bootblock()
|
| /linux/tools/perf/pmu-events/arch/x86/silvermont/ |
| H A D | cache.json | 7 … due to a full or nearly full condition, indicating back pressure from the IDI link. The L2Q may …
24 … full or near full condition which likely indicates back pressure from the IDI link. The XQ may re…
|
| /linux/tools/perf/pmu-events/arch/x86/goldmontplus/ |
| H A D | cache.json | 7 … due to a full or nearly full condition, indicating back pressure from the IDI link. The L2Q may a…
33 …tion which likely indicates back pressure from the intra-die interconnect (IDI) fabric. The XQ may…
|
| /linux/tools/perf/pmu-events/arch/x86/goldmont/ |
| H A D | cache.json | 7 … due to a full or nearly full condition, indicating back pressure from the IDI link. The L2Q may a…
33 …tion which likely indicates back pressure from the intra-die interconnect (IDI) fabric. The XQ may…
|
| /linux/tools/perf/pmu-events/arch/x86/elkhartlake/ |
| H A D | cache.json | 7 … due to a full or nearly full condition, indicating back pressure from the IDI link. The L2Q may …
24 … full or near full condition which likely indicates back pressure from the IDI link. The XQ may r…
|
| /linux/tools/perf/pmu-events/arch/x86/snowridgex/ |
| H A D | cache.json | 7 … due to a full or nearly full condition, indicating back pressure from the IDI link. The L2Q may …
24 … full or near full condition which likely indicates back pressure from the IDI link. The XQ may r…
|
| H A D | uncore-interconnect.json | 1831 …als are asserted. : If TGR egress is full, then agents will throttle outgoing AD IDI transactions",
1842 …als are asserted. : If IRQ egress is full, then agents will throttle outgoing AD IDI transactions",
7219 "BriefDescription": "IDI Lock/SplitLock Cycles",
7225 …"PublicDescription": "IDI Lock/SplitLock Cycles : Number of times an IDI Lock/SplitLock sequence w…
|
| H A D | uncore-cache.json | 1277 …als are asserted. : If TGR egress is full, then agents will throttle outgoing AD IDI transactions",
1288 …als are asserted. : If IRQ egress is full, then agents will throttle outgoing AD IDI transactions",
|
| H A D | uncore-io.json | 6237 …als are asserted. : If TGR egress is full, then agents will throttle outgoing AD IDI transactions",
6248 …als are asserted. : If IRQ egress is full, then agents will throttle outgoing AD IDI transactions",
|
| /linux/tools/perf/pmu-events/arch/x86/lunarlake/ |
| H A D | cache.json | 7 … due to a full or nearly full condition, indicating back pressure from the IDI link. The L2Q may …
259 … full or near full condition which likely indicates back pressure from the IDI link. The XQ may r…
|
| /linux/tools/perf/pmu-events/arch/x86/arrowlake/ |
| H A D | cache.json | 7 … due to a full or nearly full condition, indicating back pressure from the IDI link. The L2Q may …
207 … full or near full condition which likely indicates back pressure from the IDI link. The XQ may r…
|
| /linux/tools/perf/pmu-events/arch/x86/jaketown/ |
| H A D | uncore-interconnect.json | 1857 "BriefDescription": "IDI Lock/SplitLock Cycles",
1862 "PublicDescription": "Number of times an IDI Lock/SplitLock sequence was started",
|
| /linux/tools/perf/pmu-events/arch/x86/icelakex/ |
| H A D | uncore-interconnect.json | 2064 …als are asserted. : If TGR egress is full, then agents will throttle outgoing AD IDI transactions",
2097 …als are asserted. : If IRQ egress is full, then agents will throttle outgoing AD IDI transactions",
9343 …als are asserted. : If TGR egress is full, then agents will throttle outgoing AD IDI transactions",
9376 …als are asserted. : If IRQ egress is full, then agents will throttle outgoing AD IDI transactions",
17675 "BriefDescription": "IDI Lock/SplitLock Cycles",
17681 …"PublicDescription": "IDI Lock/SplitLock Cycles : Number of times an IDI Lock/SplitLock sequence w…
|
| H A D | uncore-io.json | 6207 …als are asserted. : If TGR egress is full, then agents will throttle outgoing AD IDI transactions",
6240 …als are asserted. : If IRQ egress is full, then agents will throttle outgoing AD IDI transactions",
|
| /linux/tools/perf/pmu-events/arch/x86/ivytown/ |
| H A D | uncore-interconnect.json | 3566 "BriefDescription": "IDI Lock/SplitLock Cycles",
3571 "PublicDescription": "Number of times an IDI Lock/SplitLock sequence was started",
|
| /linux/tools/perf/pmu-events/arch/x86/skylakex/ |
| H A D | uncore-cache.json | 4719 "PublicDescription": "Counts the number of entries successfully inserted into the TOR that match qualifications specified by the subevent.; Misses. (a miss is defined to be any transaction from the IRQ, PRQ, RRQ, IPQ or (in the victim case) the ISMQ, that required the CHA to spawn a new UPI/SMI3 request on the UPI fabric (including UPI snoops and/or any RD/WR to a local memory controller, in the event that the CHA is the home node)). Basically, if the LLC/SF/MLC complex were not able to service the request without involving another agent...it is a miss. If only IDI snoops were required, it is not a miss (that means the SF/MLC com",
5132 "PublicDescription": "For each cycle, this event accumulates the number of valid entries in the TOR that match qualifications specified by the subevent. T; Misses. (a miss is defined to be any transaction from the IRQ, PRQ, RRQ, IPQ or (in the victim case) the ISMQ, that required the CHA to spawn a new UPI/SMI3 request on the UPI fabric (including UPI snoops and/or any RD/WR to a local memory controller, in the event that the CHA is the home node)). Basically, if the LLC/SF/MLC complex were not able to service the request without involving another agent...it is a miss. If only IDI snoops were required, it is not a miss (that means the SF/MLC com",
|
| /linux/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| H A D | uncore-cache.json | 4842 "PublicDescription": "Counts the number of entries successfully inserted into the TOR that match qualifications specified by the subevent.; Misses. (a miss is defined to be any transaction from the IRQ, PRQ, RRQ, IPQ or (in the victim case) the ISMQ, that required the CHA to spawn a new UPI/SMI3 request on the UPI fabric (including UPI snoops and/or any RD/WR to a local memory controller, in the event that the CHA is the home node)). Basically, if the LLC/SF/MLC complex were not able to service the request without involving another agent...it is a miss. If only IDI snoops were required, it is not a miss (that means the SF/MLC com",
5266 "PublicDescription": "For each cycle, this event accumulates the number of valid entries in the TOR that match qualifications specified by the subevent. T; Misses. (a miss is defined to be any transaction from the IRQ, PRQ, RRQ, IPQ or (in the victim case) the ISMQ, that required the CHA to spawn a new UPI/SMI3 request on the UPI fabric (including UPI snoops and/or any RD/WR to a local memory controller, in the event that the CHA is the home node)). Basically, if the LLC/SF/MLC complex were not able to service the request without involving another agent...it is a miss. If only IDI snoops were required, it is not a miss (that means the SF/MLC com",
|
| H A D | uncore-interconnect.json | 13799 "BriefDescription": "IDI Lock/SplitLock Cycles",
13805 "PublicDescription": "Number of times an IDI Lock/SplitLock sequence was started",
|