| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-class-fpga-manager | 13 wrong during FPGA programming (something that the driver can't
30 * write init = preparing FPGA for programming
31 * write init error = Error while preparing FPGA for programming
33 * write error = Error while programming
34 * write complete = Doing post programming steps
35 * write complete error = Error while doing post programming
43 If FPGA programming operation fails, it could be caused by crc
46 programming errors to userspace. This is a list of strings for
|
| /Linux-v5.10/Documentation/driver-api/fpga/ |
| D | fpga-programming.rst | 1 In-kernel API for FPGA Programming
7 The in-kernel API for FPGA programming is a combination of APIs from
9 trigger FPGA programming is fpga_region_program_fpga().
31 bridges to control during programming or it has a pointer to a function that
71 /* Add info to region and do the programming */
84 API for programming an FPGA
|
| D | fpga-region.rst | 20 enumeration after programming.
24 * which FPGA manager to use to do the programming
26 * which bridges to disable before programming and enable afterwards.
54 Manager it will be using to do the programming. This usually would happen
62 The FPGA region will need to specify which bridges to control while programming
65 the list of bridges to program just before programming
|
| D | intro.rst | 26 If you are adding a new FPGA or a new method of programming an FPGA,
36 region of an FPGA during programming. They are disabled before
37 programming begins and re-enabled afterwards. An FPGA bridge may be
|
| D | fpga-mgr.rst | 7 The FPGA manager core exports a set of functions for programming an FPGA with
18 The particulars for programming the image are presented in a structure (struct
73 do the programming sequence for this particular FPGA. These ops return 0 for
76 The programming sequence is::
|
| /Linux-v5.10/drivers/net/wireless/rsi/ |
| D | rsi_boot_params.h | 58 /* structure to store configs related to TAPLL programming */
64 /* structure to store configs related to PLL960 programming */
71 /* structure to store configs related to AFEPLL programming */
92 /* structure to store configs related to UMAC clk programming */
149 /* WDT programming values */
|
| /Linux-v5.10/tools/memory-model/Documentation/ |
| D | references.txt | 34 Proceedings of the 32Nd ACM SIGPLAN Conference on Programming
41 ACM SIGPLAN Conference on Programming Language Design and
56 SIGPLAN-SIGACT Symposium on Principles of Programming Languages
63 Principles of Programming Languages (POPL 2017). ACM, New York,
69 Proceedings of the ACM on Programming Languages, Volume 2, Issue
92 Programming Languages and Operating Systems (ASPLOS 2018). ACM,
|
| /Linux-v5.10/Documentation/devicetree/bindings/fpga/ |
| D | fpga-region.txt | 130 * image-specific information needed to to the programming.
147 one bridge to control during FPGA programming, the region will also contain a
181 controlled during FPGA programming along with the parent FPGA bridge.
198 - child nodes : devices in the FPGA after programming.
202 programming: the parent fpga_bridge0 and fpga_bridge1. Because the region is
204 fpga-bridges property. During programming, these bridges are disabled, the
206 specified in the region. If FPGA programming succeeds, the bridges are
208 are then populated. If FPGA programming fails, the bridges are left disabled
329 to handle programming the FPGA. If the FPGA Region is the child of another FPGA
332 FPGA programming, the FPGA Region will disable the bridges that are in its
[all …]
|
| /Linux-v5.10/Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 16 Improvements could be invalidating an entire programming sequence and
22 that bus clashes due to programming errors (two streams using the same bit
34 be applied. In case of a bad programming (command sent to non-existent
38 backtracking and restarting the entire programming sequence might be a
|
| /Linux-v5.10/Documentation/misc-devices/ |
| D | c2port.rst | 26 C2 Interface used for in-system programming of micro controllers.
38 - AN127: FLASH Programming via the C2 Interface at
45 banging) designed to enable in-system programming, debugging, and
47 this code supports only flash programming but extensions are easy to
|
| /Linux-v5.10/drivers/net/ethernet/intel/i40e/ |
| D | i40e_txrx_common.h | 84 * i40e_rx_is_programming_status - check for programming status descriptor
88 * is a programming status descriptor for flow director or FCoE
94 /* The Rx filter programming status and SPH bit occupy the same in i40e_rx_is_programming_status()
97 * programming status descriptor. in i40e_rx_is_programming_status()
|
| /Linux-v5.10/drivers/gpu/drm/ |
| D | drm_vblank_work.c | 18 * simply do said time-sensitive programming in the driver's IRQ handler,
21 * time-critical programming independently of the CPU.
24 * doesn't need to be concerned with extremely time-sensitive programming,
26 * hardware may require that certain time-sensitive programming be handled
27 * completely by the CPU, and said programming may even take too long to
41 * time-sensitive hardware programming on time, even when the system is under
|
| /Linux-v5.10/drivers/usb/dwc2/ |
| D | core.c | 65 * @hsotg: Programming view of the DWC_otg controller
97 * @hsotg: Programming view of the DWC_otg controller
133 * @hsotg: Programming view of the DWC_otg controller
187 * @hsotg: Programming view of the DWC_otg controller
247 * @hsotg: Programming view of the DWC_otg controller
315 * @hsotg: Programming view of the DWC_otg controller
382 * @hsotg: Programming view of the DWC_otg controller.
423 * @hsotg: Programming view of DWC_otg controller
456 * @hsotg: Programming view of the DWC_otg controller
475 * @hsotg: Programming view of the DWC_otg controller
[all …]
|
| /Linux-v5.10/drivers/misc/c2port/ |
| D | core.c | 497 /* Target the C2 flash programming control register for C2 data in __c2port_store_flash_access()
501 /* Write the first keycode to enable C2 Flash programming */ in __c2port_store_flash_access()
506 /* Write the second keycode to enable C2 Flash programming */ in __c2port_store_flash_access()
512 * C2 flash programming */ in __c2port_store_flash_access()
535 dev_err(c2dev->dev, "cannot enable %s flash programming\n", in c2port_store_flash_access()
550 /* Target the C2 flash programming data register for C2 data register in __c2port_write_flash_erase()
570 /* Read flash programming interface status */ in __c2port_write_flash_erase()
644 /* Target the C2 flash programming data register for C2 data register in __c2port_read_flash_data()
663 /* Read flash programming interface status */ in __c2port_read_flash_data()
695 /* Read flash programming interface status */ in __c2port_read_flash_data()
[all …]
|
| /Linux-v5.10/Documentation/input/ |
| D | input_kapi.rst | 15 input-programming
16 gameport-programming
|
| /Linux-v5.10/drivers/ata/ |
| D | pata_optidma.c | 164 /* Commence primary programming sequence */ in optidma_mode_setup()
178 /* Programming sequence complete, timing 0 dev 0, timing 1 dev 1 */ in optidma_mode_setup()
184 /* Note: at this point our programming is incomplete. We are in optidma_mode_setup()
235 * DMA programming. The architecture of the Firestar makes it easier
250 * DMA programming. The architecture of the Firestar makes it easier
265 * DMA programming. The architecture of the Firestar makes it easier
280 * DMA programming. The architecture of the Firestar makes it easier
|
| /Linux-v5.10/drivers/nvmem/ |
| D | sprd-efuse.c | 202 * allow programming, and block other programming until we clear the in sprd_efuse_raw_prog()
217 * Enable the auto-check function to validate if the programming is in sprd_efuse_raw_prog()
225 /* Disable auto-check and data double after programming */ in sprd_efuse_raw_prog()
231 * Check the efuse error status, if the programming is successful, in sprd_efuse_raw_prog()
232 * we should lock this efuse block to avoid programming again. in sprd_efuse_raw_prog()
|
| /Linux-v5.10/Documentation/devicetree/bindings/usb/ |
| D | dwc3.txt | 94 non-zero value 1-16 (DWC_usb31 programming guide
98 1-16 (DWC_usb31 programming guide section 1.2.4) to
102 non-zero value 1-16 (DWC_usb31 programming guide
106 1-16 (DWC_usb31 programming guide section 1.2.3) to
|
| /Linux-v5.10/drivers/gpu/drm/amd/display/dc/dce/ |
| D | dce_audio.c | 502 /* those are unsupported, skip programming */ in dce_aud_az_configure()
792 /*DTO0 Programming goal: in dce_aud_wall_dto_setup()
812 programming DTO modulo and DTO phase. These bits must be in dce_aud_wall_dto_setup()
815 Caution when changing this programming sequence. in dce_aud_wall_dto_setup()
832 /*DTO1 Programming goal: in dce_aud_wall_dto_setup()
844 /* Program DTO select before programming DTO modulo and DTO in dce_aud_wall_dto_setup()
884 /*DTO0 Programming goal: in dce60_aud_wall_dto_setup()
904 programming DTO modulo and DTO phase. These bits must be in dce60_aud_wall_dto_setup()
907 Caution when changing this programming sequence. in dce60_aud_wall_dto_setup()
924 /*DTO1 Programming goal: in dce60_aud_wall_dto_setup()
[all …]
|
| D | Makefile | 24 # HW object file under this folder follow similar pattern for HW programming
26 # - register programming through common macros that look up register
|
| /Linux-v5.10/Documentation/devicetree/bindings/phy/ |
| D | calxeda-combophy.yaml | 14 Programming the PHYs is typically handled by those device drivers,
31 description: device ID for programming the ComboPHY.
|
| /Linux-v5.10/drivers/staging/rtl8192u/ |
| D | r8180_93cx6.c | 3 * This files contains card eeprom (93c46 or 93c56) programming routines,
115 /* enable EPROM programming */ in eprom_read()
166 /* disable EPROM programming */ in eprom_read()
|
| /Linux-v5.10/Documentation/driver-api/driver-model/ |
| D | class.rst | 13 Each device class defines a set of semantics and a programming interface
15 implementation of that programming interface for a particular device on
22 Programming Interface
|
| /Linux-v5.10/tools/perf/Documentation/ |
| D | perf-list.txt | 81 Manual Volume 2: System Programming, 13.3 Instruction-Based
94 … and IA-32 Architectures Software Developer's Manual Volume 3B: System Programming Guide] Figure 3…
95 …s PerfEvtSeln (see [AMD64 Architecture Programmer’s Manual Volume 2: System Programming], Page 344,
314 …Intel® 64 and IA-32 Architectures Software Developer's Manual Volume 3B: System Programming Guide],
315 …ssor_TechDocs/24593_APM_v2.pdf[AMD64 Architecture Programmer’s Manual Volume 2: System Programming]
|
| /Linux-v5.10/Documentation/devicetree/bindings/virtio/ |
| D | iommu.txt | 3 When virtio-iommu uses the PCI transport, its programming interface is
34 /* The IOMMU programming interface uses slot 00:01.0 */
|
