Home
last modified time | relevance | path

Searched full:idi (Results 1 – 25 of 42) sorted by relevance

12

/kernel/linux/linux-6.6/Documentation/devicetree/bindings/media/
Dmicrochip,csi2dc.yaml16 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 */
/kernel/linux/linux-6.6/drivers/gpio/
Dgpio-104-idi-48.c3 * 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");
DKconfig886 tristate "ACCES 104-IDI-48 GPIO support"
894 Enables GPIO support for the ACCES 104-IDI-48 family (104-IDI-48A,
895 104-IDI-48AC, 104-IDI-48B, 104-IDI-48BC). The base port addresses for
1678 PCIe-IDI-24, PCIe-IDO-24, PCIe-IDIO-12). An interrupt is generated
DMakefile23 obj-$(CONFIG_GPIO_104_IDI_48) += gpio-104-idi-48.o
Dgpio-pcie-idio-24.c7 * PCIe-IDI-24, PCIe-IDO-24, and PCIe-IDIO-12.
/kernel/linux/linux-5.10/drivers/gpio/
Dgpio-104-idi-48.c3 * 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.
30 MODULE_PARM_DESC(base, "ACCES 104-IDI-48 base addresses");
34 MODULE_PARM_DESC(irq, "ACCES 104-IDI-48 interrupt line numbers");
188 .name = "104-idi-48",
322 .name = "104-idi-48"
328 MODULE_DESCRIPTION("ACCES 104-IDI-48 GPIO driver");
DKconfig771 tristate "ACCES 104-IDI-48 GPIO support"
776 Enables GPIO support for the ACCES 104-IDI-48 family (104-IDI-48A,
777 104-IDI-48AC, 104-IDI-48B, 104-IDI-48BC). The base port addresses for
1502 PCIe-IDI-24, PCIe-IDO-24, PCIe-IDIO-12). An interrupt is generated
DMakefile22 obj-$(CONFIG_GPIO_104_IDI_48) += gpio-104-idi-48.o
Dgpio-pcie-idio-24.c16 * PCIe-IDI-24, PCIe-IDO-24, and PCIe-IDIO-12.
/kernel/linux/linux-5.10/drivers/mtd/
Dssfdc.c25 int cis_block; /* block n. containing CIS/IDI */
97 /* These bytes are the signature for the CIS/IDI sector */
117 * Look for CIS/IDI sector on the first GOOD block (give up after 4 bad in get_valid_cis_sector()
129 "SSFDC_RO:can't read CIS/IDI sector\n"); in get_valid_cis_sector()
135 pr_debug("SSFDC_RO: CIS/IDI sector not found" in get_valid_cis_sector()
294 /* Check for SSDFC format by reading CIS/IDI sector */ in ssfdcr_add_mtd()
/kernel/linux/linux-6.6/drivers/mtd/
Dssfdc.c25 int cis_block; /* block n. containing CIS/IDI */
97 /* These bytes are the signature for the CIS/IDI sector */
117 * Look for CIS/IDI sector on the first GOOD block (give up after 4 bad in get_valid_cis_sector()
129 "SSFDC_RO:can't read CIS/IDI sector\n"); in get_valid_cis_sector()
135 pr_debug("SSFDC_RO: CIS/IDI sector not found" in get_valid_cis_sector()
294 /* Check for SSDFC format by reading CIS/IDI sector */ in ssfdcr_add_mtd()
/kernel/linux/linux-6.6/drivers/comedi/drivers/
Dadl_pci7x3x.c86 .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()
Dadv_pci_dio.c115 /* DI, IDI, DO, IDO, ID, IRQ_DI0, IRQ_DI1, IRQ_IDI0, IRQ_IDI1 */
/kernel/linux/linux-6.6/drivers/media/platform/microchip/
DKconfig57 that converts IDI interface byte stream to a parallel pixel stream.
/kernel/linux/linux-5.10/drivers/usb/storage/
Dene_ub6250.c171 #define MS_SYSENT_TYPE_CIS_IDI 0x0a /* CIS/IDI */
389 struct ms_bootblock_idi idi; member
391 } idi; member
1032 } else if (i == 1) { /* CIS/IDI */ in ms_lib_process_bootblock()
1033 struct ms_bootblock_idi *idi; in ms_lib_process_bootblock() local
1048 … idi = &((struct ms_bootblock_cis_idi *)(PageBuffer + (EntryOffset % MS_BYTES_PER_PAGE)))->idi.idi; in ms_lib_process_bootblock()
1049 if (le16_to_cpu(idi->wIDIgeneralConfiguration) != MS_IDI_GENERAL_CONF) in ms_lib_process_bootblock()
1052 info->MS_Lib.BytesPerSector = le16_to_cpu(idi->wIDIbytesPerSector); in ms_lib_process_bootblock()
/kernel/linux/linux-6.6/drivers/usb/storage/
Dene_ub6250.c171 #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()
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/silvermont/
Dcache.json6 … due to a full or nearly full condition, indicating back pressure from the IDI link. The L2Q may …
21 … full or near full condition which likely indicates back pressure from the IDI link. The XQ may re…
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/silvermont/
Dcache.json3 … full or near full condition which likely indicates back pressure from the IDI link. The XQ may re…
12 … due to a full or nearly full condition, indicating back pressure from the IDI link. The L2Q may …
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/elkhartlake/
Dcache.json6 … due to a full or nearly full condition, indicating back pressure from the IDI link. The L2Q may …
21 … full or near full condition which likely indicates back pressure from the IDI link. The XQ may r…
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/snowridgex/
Dcache.json6 … due to a full or nearly full condition, indicating back pressure from the IDI link. The L2Q may …
21 … full or near full condition which likely indicates back pressure from the IDI link. The XQ may r…
Duncore-interconnect.json1495 …als are asserted. : If TGR egress is full, then agents will throttle outgoing AD IDI transactions",
1504 …als are asserted. : If IRQ egress is full, then agents will throttle outgoing AD IDI transactions",
5856 "BriefDescription": "IDI Lock/SplitLock Cycles",
5860 …"PublicDescription": "IDI Lock/SplitLock Cycles : Number of times an IDI Lock/SplitLock sequence w…
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/goldmontplus/
Dcache.json6 … due to a full or nearly full condition, indicating back pressure from the IDI link. The L2Q may a…
29 …tion which likely indicates back pressure from the intra-die interconnect (IDI) fabric. The XQ may…
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/goldmont/
Dcache.json6 … due to a full or nearly full condition, indicating back pressure from the IDI link. The L2Q may a…
29 …tion which likely indicates back pressure from the intra-die interconnect (IDI) fabric. The XQ may…
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/goldmont/
Dcache.json24 …tion which likely indicates back pressure from the intra-die interconnect (IDI) fabric. The XQ may…
34 … due to a full or nearly full condition, indicating back pressure from the IDI link. The L2Q may a…
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/goldmontplus/
Dcache.json28 …tion which likely indicates back pressure from the intra-die interconnect (IDI) fabric. The XQ may…
40 … due to a full or nearly full condition, indicating back pressure from the IDI link. The L2Q may a…

12