/linux/Documentation/ABI/testing/ |
H A 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
|
H A D | sysfs-bus-bcma | 23 on their revision. Use it for detailed programming.
|
/linux/Documentation/driver-api/fpga/ |
H A D | fpga-programming.rst | 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
|
H A 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
|
H A D | index.rst | 14 fpga-programming
|
/linux/Documentation/input/ |
H A D | input_kapi.rst | 12 input-programming 13 gameport-programming
|
/linux/drivers/gpu/drm/amd/display/dc/dml2/dml21/ |
H A D | dml21_translation_helper.c | 1154 …context->bw_ctx.bw.dcn.clk.dispclk_khz = in_ctx->v21.mode_programming.programming->min_clocks.dcn4… in dml21_copy_clocks_to_dc_state() 1155 …context->bw_ctx.bw.dcn.clk.dcfclk_khz = in_ctx->v21.mode_programming.programming->min_clocks.dcn4x… in dml21_copy_clocks_to_dc_state() 1156 …context->bw_ctx.bw.dcn.clk.dramclk_khz = in_ctx->v21.mode_programming.programming->min_clocks.dcn4… in dml21_copy_clocks_to_dc_state() 1157 …context->bw_ctx.bw.dcn.clk.fclk_khz = in_ctx->v21.mode_programming.programming->min_clocks.dcn4x.a… in dml21_copy_clocks_to_dc_state() 1158 …context->bw_ctx.bw.dcn.clk.idle_dramclk_khz = in_ctx->v21.mode_programming.programming->min_clocks… in dml21_copy_clocks_to_dc_state() 1159 …context->bw_ctx.bw.dcn.clk.idle_fclk_khz = in_ctx->v21.mode_programming.programming->min_clocks.dc… in dml21_copy_clocks_to_dc_state() 1160 …context->bw_ctx.bw.dcn.clk.dcfclk_deep_sleep_khz = in_ctx->v21.mode_programming.programming->min_c… in dml21_copy_clocks_to_dc_state() 1161 …context->bw_ctx.bw.dcn.clk.fclk_p_state_change_support = in_ctx->v21.mode_programming.programming-… in dml21_copy_clocks_to_dc_state() 1162 …context->bw_ctx.bw.dcn.clk.p_state_change_support = in_ctx->v21.mode_programming.programming->uclk… in dml21_copy_clocks_to_dc_state() 1163 …context->bw_ctx.bw.dcn.clk.dtbclk_en = in_ctx->v21.mode_programming.programming->min_clocks.dcn4x.… in dml21_copy_clocks_to_dc_state() [all …]
|
/linux/Documentation/driver-api/soundwire/ |
H A 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/Documentation/misc-devices/ |
H A D | c2port.rst | 26 C2 Interface used for in-system programming of micro controllers. 45 banging) designed to enable in-system programming, debugging, and 47 this code supports only flash programming but extensions are easy to
|
/linux/Documentation/devicetree/bindings/clock/ |
H A D | keystone-pll.txt | 46 - bit-mask : arbitrary bitmask for programming the mux 68 - bit-mask : arbitrary bitmask for programming the divider
|
/linux/Documentation/driver-api/ |
H A 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
|
/linux/Documentation/arch/ |
H A D | index.rst | 6 These books provide programming details about architecture-specific
|
/linux/Documentation/trace/coresight/ |
H A D | coresight-ect.rst | 30 The CTI driver enables the programming of the CTI to attach triggers to 38 programming registers in the CTI. 89 * ``channels``: Contains the channel API - CTI main programming interface. 189 * ``chan_xtrigs_reset``: Write 1 to clear all channel / trigger programming.
|
H A D | coresight-etm4x-reference.rst | 2 ETMv4 sysfs linux driver programming reference. 26 in this will cause equivalent programming of trace config and 42 Reset all programming to trace nothing / no logic programmed. 622 *Note:* When programming any address comparator the driver will tag the 638 To remove programming on all the comparators (and all the other hardware) use 817 Once the reset parameter has been used, and/or custom programming has been
|
H A D | coresight-dummy.rst | 17 not have any programming interfaces, so that paths can be created in the driver.
|
/linux/Documentation/process/ |
H A D | programming-language.rst | 6 The kernel is written in the C programming language [c-language]_. 37 The kernel has experimental support for the Rust programming language
|
H A D | development-process.rst | 12 discussion which does not require a deep knowledge of kernel programming to
|
/linux/Documentation/translations/zh_TW/process/ |
H A D | index.rst | 33 programming-language
|
/linux/Documentation/devicetree/bindings/spi/ |
H A D | jcore,spi.txt | 16 programming is relative to the frequency of the indicated clock.
|
/linux/Documentation/hwmon/ |
H A 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
|
/linux/Documentation/spi/ |
H A D | butterfly.rst | 19 This is more powerful than "ISP programming" cables since it lets kernel 29 side this is like "sp12" programming cables.
|
/linux/Documentation/iio/ |
H A D | iio_tools.rst | 24 yet complete programming interface that can be used for advanced projects.
|
/linux/Documentation/translations/zh_CN/process/ |
H A D | index.rst | 33 programming-language
|
/linux/Documentation/arch/openrisc/ |
H A D | openrisc_port.rst | 51 The OpenRISC community typically uses FuseSoC to manage building and programming 52 an SoC into an FPGA. The below is an example of programming a De0 Nano
|
/linux/drivers/bcma/ |
H A D | README | 2 however from programming point of view there is nothing AMBA specific we use.
|