Searched full:programming (Results 1 – 25 of 169) sorted by relevance
1234567
| /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
32 programming
34 * write error = Error while programming
35 * write complete = Doing post programming steps
36 * write complete error = Error while doing post programming
44 If FPGA programming operation fails, it could be caused by crc
47 programming errors to userspace. This is a list of strings for
|
| /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 :c:func:`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::
|
| D | index.rst | 14 fpga-programming
|
| /Documentation/input/ |
| D | input_kapi.rst | 15 input-programming
16 gameport-programming
|
| /Documentation/misc-devices/ |
| D | c2port.txt | 22 C2 Interface used for in-system programming of micro controllers.
34 - AN127: FLASH Programming via the C2 Interface at
41 banging) designed to enable in-system programming, debugging, and
43 this code supports only flash programming but extensions are easy to
|
| /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
|
| /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 …]
|
| /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 */
|
| /Documentation/crypto/ |
| D | api.rst | 1 Programming Interface
|
| D | index.rst | 10 for cryptographic use cases, as well as programming examples.
|
| /Documentation/devicetree/bindings/usb/ |
| D | dwc3.txt | 90 non-zero value 1-16 (DWC_usb31 programming guide
94 1-16 (DWC_usb31 programming guide section 1.2.4) to
98 non-zero value 1-16 (DWC_usb31 programming guide
102 1-16 (DWC_usb31 programming guide section 1.2.3) to
|
| /Documentation/driver-api/ |
| D | i2c.rst | 16 The Linux I2C programming interfaces support the master side of bus
17 interactions and the slave side. The programming interface is
|
| /Documentation/process/ |
| D | programming-language.rst | 3 Programming Language
6 The kernel is written in the C programming language [c-language]_.
|
| D | development-process.rst | 27 discussion which does not require a deep knowledge of kernel programming to
|
| /Documentation/devicetree/bindings/phy/ |
| D | calxeda-combophy.txt | 7 - phydev: device ID for programming the combophy.
|
| /Documentation/devicetree/bindings/clock/ti/ |
| D | mux.txt | 15 results in programming the register as follows:
47 - ti,index-starts-at-one : valid input select programming starts at 1, not
|
| /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
|
| /Documentation/devicetree/bindings/clock/ |
| D | keystone-pll.txt | 48 - bit-mask : arbitrary bitmask for programming the mux
70 - bit-mask : arbitrary bitmask for programming the divider
|
| /Documentation/devicetree/bindings/spi/ |
| D | jcore,spi.txt | 16 programming is relative to the frequency of the indicated clock.
|
| /Documentation/devicetree/bindings/pci/ |
| D | pci.txt | 32 root port to downstream device and host bridge drivers can do programming
33 which depends on CLKREQ signal existence. For example, programming root port
|
| /Documentation/translations/zh_CN/process/ |
| D | index.rst | 29 programming-language
|
| /Documentation/hwmon/ |
| D | ina209.rst | 85 to be done in the BIOS. In the absence of BIOS programming, the shunt resistor
97 Output pin programming is a board feature which depends on the BIOS. It is
|
1234567