/openbmc/u-boot/doc/device-tree-bindings/gpio/ |
H A D | gpio-samsung.txt | 12 [pin number within the gpio controller]
|
/openbmc/u-boot/doc/device-tree-bindings/i2c/ |
H A D | i2c.txt | 4 U-Boot's I2C model has the concept of an offset within a chip (I2C target
|
/openbmc/openbmc/meta-phosphor/recipes-phosphor/skeleton/ |
H A D | obmc-libobmc-intf_git.bb | 29 # Because of that, a link must be created within the
|
/openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
H A D | i2c_compare_byte.md | 14 …and surrounded by double quotes. Specifies which bits should be compared within the byte value. On…
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/htpdate/ |
H A D | htpdate_1.3.7.bb | 9 within 0.5 seconds (better with multiple servers).\
|
/openbmc/linux/drivers/net/ethernet/engleder/ |
H A D | Kconfig | 36 This enables self test support within the TSN endpoint driver.
|
/openbmc/docs/development/ |
H A D | dev-environment.md | 50 another possibility but not covered within this document. See 53 container and launch bitbake within it. This also works within a podman 137 If you are running within a virtual environment where you can use the real
|
/openbmc/linux/drivers/mcb/ |
H A D | Kconfig | 13 FPGA based devices. It is used to identify MCB based IP-Cores within
|
/openbmc/openbmc/poky/meta/recipes-core/meta/ |
H A D | meta-extsdk-toolchain.bb | 10 # within sstate.bbclass, so if you copy or rename this and expect the same
|
/openbmc/inarp/ |
H A D | configure.ac | 29 …STRING([--enable-oe-sdk], [Link testcases absolutely against OE SDK so they can be ran within it.])
|
/openbmc/u-boot/doc/device-tree-bindings/clock/ |
H A D | snps,hsdk-cgu.txt | 4 controllers and peripherals within the SoC.
|
H A D | st,stm32h7-rcc.txt | 137 The index is the bit number within the RCC registers bank, starting from RCC 140 Where bit_offset is the bit offset within the register.
|
/openbmc/linux/scripts/coccinelle/free/ |
H A D | put_device.cocci | 47 + ", but without a corresponding object release within this function.")
|
/openbmc/openbmc/poky/meta/recipes-devtools/gcc/gcc/ |
H A D | 0008-libtool.patch | 9 This patch stops this speading to libdir in the libstdc++.la file within libtool.
|
/openbmc/linux/Documentation/devicetree/bindings/power/ |
H A D | qcom,kpss-acc-v2.yaml | 14 There is one ACC register region per CPU within the KPSS remapped region as
|
/openbmc/linux/drivers/media/usb/au0828/ |
H A D | Kconfig | 33 capture within the au0828 driver.
|
/openbmc/linux/Documentation/devicetree/bindings/leds/ |
H A D | leds-class-multicolor.yaml | 20 within this documentation directory.
|
/openbmc/linux/Documentation/devicetree/bindings/soc/amlogic/ |
H A D | amlogic,canvas.yaml | 19 Many IPs within Amlogic SoCs rely on canvas indexes to read/write pixel data
|
/openbmc/linux/Documentation/filesystems/ext4/ |
H A D | overview.rst | 8 very hard to keep each file's blocks within the same group, thereby
|
/openbmc/linux/fs/bfs/ |
H A D | Kconfig | 12 on your /stand slice from within Linux. You then also need to say Y
|
/openbmc/linux/Documentation/devicetree/bindings/soc/qcom/ |
H A D | qcom,smp2p.yaml | 39 - description: u32 representing offset to the register within the syscon 40 - description: u32 representing the ipc bit within the register
|
/openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
H A D | ingenic,pinctrl.yaml | 15 may be used as GPIOs, multiplexed device functions are configured within the 19 pin within that GPIO port. For example PA0 is the first pin in GPIO port A,
|
/openbmc/linux/tools/scripts/ |
H A D | utilities.mak | 46 # Use this to escape newlines from within a shell call; 62 # Use this to unescape newlines from within a shell call; 109 # within the context of a command line of a makefile rule
|
/openbmc/linux/Documentation/gpu/ |
H A D | drm-usage-stats.rst | 70 Uniqueness of the value shall be either globally unique, or unique within the 90 larger value within a reasonable period. Upon observing a value lower than what 111 larger value within a reasonable period. Upon observing a value lower than what
|
/openbmc/openbmc/poky/documentation/dev-manual/ |
H A D | custom-distribution.rst | 44 and then "require" them from within your distribution configuration 122 distribution provided within the ``meta-poky`` layer and then modifying it. 126 will still apply. This includes override usage within files (e.g. ``:poky``)
|