/openbmc/openbmc/meta-openembedded/meta-oe/recipes-dbs/mysql/mariadb/ |
H A D | 0001-Remove-the-compile_time_assert-lines.patch | 4 Subject: [PATCH] Remove the compile_time_assert lines 6 Remove the problematic compile_time_assert lines to fix the below build
|
/openbmc/linux/Documentation/devicetree/bindings/interrupt-controller/ |
H A D | microchip,sama7g5-eic.yaml | 14 support for handling up to 2 external interrupt lines. 34 Contains the GIC SPI IRQs mapped to the external interrupt lines. They
|
H A D | actions,owl-sirq.yaml | 15 and S900) and provides support for handling up to 3 external interrupt lines. 37 Contains the GIC SPI IRQs mapped to the external interrupt lines.
|
/openbmc/openbmc/meta-phosphor/recipes-phosphor/ipmi/ |
H A D | phosphor-ipmi-net_git.bb | 1 # To add another RMCPP interface, add similar lines to the 2 # following lines in a bbappend:
|
/openbmc/linux/drivers/mtd/nand/raw/ |
H A D | nandsim.c | 350 } lines; member 1620 if (ns->lines.wp) { in ns_do_state_action() 1660 if (ns->lines.wp) { in ns_do_state_action() 1869 if (!ns->lines.ce) { in ns_nand_read_byte() 1873 if (ns->lines.ale || ns->lines.cle) { in ns_nand_read_byte() 1929 if (!ns->lines.ce) { in ns_nand_write_byte() 1933 if (ns->lines.ale && ns->lines.cle) { in ns_nand_write_byte() 2118 if (ns->lines.ale || ns->lines.cle) { in ns_nand_read_buf() 2181 ns->lines.ce = 1; in ns_exec_op() 2185 ns->lines.cle = 0; in ns_exec_op() [all …]
|
/openbmc/linux/drivers/gpu/drm/nouveau/nvkm/subdev/gpio/ |
H A D | base.c | 139 for (i = 0; (hi | lo) && i < gpio->func->lines; i++) { in nvkm_gpio_intr() 150 u32 mask = (1ULL << gpio->func->lines) - 1; in nvkm_gpio_fini() 236 return nvkm_event_init(&nvkm_gpio_intr_func, &gpio->subdev, 2, func->lines, &gpio->event); in nvkm_gpio_new_()
|
/openbmc/linux/Documentation/devicetree/bindings/connector/ |
H A D | usb-connector.yaml | 273 # Micro-USB connector with HS lines routed via controller (MUIC). 283 # USB-C connector attached to CC controller (s2mm005), HS lines routed 284 # to companion PMIC (max77865), SS lines to USB3 PHY and SBU to DisplayPort. 285 # DisplayPort video lines are routed to the connector via SS mux in USB3 PHY. 349 # with SS 2:1 MUX. HS lines routed to SoC, SS lines routed to the MUX and 375 # USB connector with GPIO control lines 388 # Micro-USB connector with HS lines routed via controller (MUIC) and MHL 389 # lines connected to HDMI-MHL bridge (sii8620) on Samsung Exynos5433-based
|
/openbmc/linux/drivers/gpu/drm/gud/ |
H A D | gud_pipe.c | 322 unsigned int i, lines; in gud_flush_damage() local 332 lines = drm_rect_height(damage); in gud_flush_damage() 334 if (gdrm->bulk_len < lines * pitch) in gud_flush_damage() 335 lines = gdrm->bulk_len / pitch; in gud_flush_damage() 337 for (i = 0; i < DIV_ROUND_UP(drm_rect_height(damage), lines); i++) { in gud_flush_damage() 340 rect.y1 += i * lines; in gud_flush_damage() 341 rect.y2 = min_t(u32, rect.y1 + lines, damage->y2); in gud_flush_damage()
|
/openbmc/linux/Documentation/devicetree/bindings/input/ |
H A D | matrix-keymap.yaml | 32 description: Number of row lines connected to the keypad controller. 36 description: Number of column lines connected to the keypad controller.
|
H A D | brcm,bcm-keypad.txt | 4 keypad device. The keypad controller supports multiple row and column lines. 23 - keypad,num-rows: Number of row lines connected to the keypad 26 - keypad,num-columns: Number of column lines connected to the
|
H A D | st-keyscan.txt | 22 - keypad,num-rows: Number of row lines connected to the keypad controller. 24 - keypad,num-columns: Number of column lines connected to the keypad
|
/openbmc/openpower-hw-diags/util/ |
H A D | ffdc.cpp | 128 FFDCFile createFFDCTraceFile(const std::vector<std::string>& lines) in createFFDCTraceFile() argument 136 for (const std::string& line : lines) in createFFDCTraceFile()
|
/openbmc/linux/arch/arm64/boot/dts/actions/ |
H A D | s900-bubblegum-96.dts | 78 * For the lines routed to the external connectors the 79 * lines are named after the 96Boards CE Specification 1.0, 86 * UART2. Only exception is the I2C lines for which the schematic 88 * lines i.e. "[FOO]", the GPIO named lines "GPIO-A" thru "GPIO-L"
|
/openbmc/u-boot/lib/efi_selftest/ |
H A D | efi_selftest_block_device.c | 47 struct line lines[]; member 152 if (!img.lines[i].line) in decompress() 154 addr = img.lines[i].addr; in decompress() 158 boottime->copy_mem(buf + addr, img.lines[i].line, len); in decompress()
|
/openbmc/u-boot/doc/ |
H A D | README.kwbimage | 46 2. This file can have empty lines and lines starting with "#" as first 48 3. This file can have configuration command lines as mentioned below,
|
/openbmc/openbmc-tools/dbus-vis/ |
H A D | boost_handler_timeline_vis.js | 41 const lines = content.split('\n'); 45 for (let lidx = 0; lidx < lines.length; lidx++) { 46 const line = lines[lidx];
|
/openbmc/linux/scripts/ |
H A D | leaking_addresses.pl | 611 my $lines = $ref->{$_}; 612 my $length = @$lines; 613 printf "[%d %s] %s", $length, $_, @$lines[0];
|
/openbmc/linux/Documentation/devicetree/bindings/timestamp/ |
H A D | nvidia,tegra194-hte.yaml | 15 IRQ lines for the state change respectively, upon detection it will record 19 GPIO lines from the AON (always on) GPIO controller. 47 HTE lines are arranged in 32 bit slice where each bit represents different
|
/openbmc/linux/kernel/debug/kdb/ |
H A D | kdb_main.c | 2086 int lines = 0; in kdb_dmesg() local 2100 lines = 0; in kdb_dmesg() 2119 if (lines < 0) { in kdb_dmesg() 2123 else if (adjust - lines >= n) in kdb_dmesg() 2127 lines = abs(lines); in kdb_dmesg() 2128 } else if (lines > 0) { in kdb_dmesg() 2129 skip = n - lines - adjust; in kdb_dmesg() 2130 lines = abs(lines); in kdb_dmesg() 2136 lines += skip; in kdb_dmesg() 2142 lines = n; in kdb_dmesg() [all …]
|
/openbmc/linux/drivers/media/pci/ivtv/ |
H A D | ivtv-streams.c | 378 int lines; in ivtv_vbi_setup() local 396 lines = itv->vbi.count * 2; in ivtv_vbi_setup() 398 lines = itv->is_60hz ? 24 : 38; in ivtv_vbi_setup() 400 lines += 2; in ivtv_vbi_setup() 403 itv->vbi.enc_size = lines * (raw ? itv->vbi.raw_size : itv->vbi.sliced_size); in ivtv_vbi_setup() 430 data[5] = lines; in ivtv_vbi_setup() 443 data[5] = lines; in ivtv_vbi_setup() 445 data[6] = itv->vbi.enc_size / lines; in ivtv_vbi_setup()
|
/openbmc/linux/drivers/gpu/drm/ |
H A D | drm_format_helper.c | 51 unsigned long lines = drm_rect_height(clip); in __drm_fb_xfrm() local 72 for (i = 0; i < lines; ++i) { in __drm_fb_xfrm() 94 unsigned long lines = drm_rect_height(clip); in __drm_fb_xfrm_toio() local 116 for (i = 0; i < lines; ++i) { in __drm_fb_xfrm_toio() 182 unsigned int i, y, lines = drm_rect_height(clip); in drm_fb_memcpy() local 199 for (y = 0; y < lines; y++) { in drm_fb_memcpy() 1011 unsigned int lines = drm_rect_height(clip); in drm_fb_xrgb8888_to_mono() local 1052 for (y = 0; y < lines; y++) { in drm_fb_xrgb8888_to_mono()
|
/openbmc/openbmc/poky/meta/lib/oeqa/selftest/cases/ |
H A D | rust.py | 14 lines = f.readlines() 15 for line in lines:
|
/openbmc/linux/Documentation/admin-guide/device-mapper/ |
H A D | statistics.rst | 140 If omitted, all lines are returned. 143 The number of lines to include in the output. 144 If omitted, all lines are returned. 184 If omitted, all lines are printed and then cleared. 187 The number of lines to process. 188 If omitted, all lines are printed and then cleared.
|
/openbmc/linux/Documentation/driver-api/ |
H A D | reset.rst | 36 Control method that determines the state of one or multiple reset lines. 42 carefully timed sequence of pulses on multiple reset lines. 47 number of reset lines. 60 Functions are provided to assert and deassert the controlled reset lines, 95 functions to assert and deassert reset lines. 149 Some drivers need to assert a bunch of reset lines in no particular order.
|
/openbmc/linux/Documentation/devicetree/bindings/media/ |
H A D | video-interfaces.yaml | 57 between two devices, e.g. there are logic signal inverters on the lines. 63 and data-shift properties can be used to assign physical data lines to each 104 Number of data lines actively used, valid for the parallel busses. 111 data lines, data-shift can be used to specify which data lines are used, 112 e.g. "bus-width=<8>; data-shift=<2>;" means, that lines 9:2 are used.
|