| /openbmc/linux/Documentation/mhi/ |
| H A D | mhi.rst | 55 Channel context array: All channel configurations are organized in channel
59 transfer rings are organized as a circular queue of Transfer Descriptors (TD).
61 Event context array: All event configurations are organized in the event context
67 Command context array: All command configurations are organized in command
71 rings are organized as a circular queue of Command Descriptors (CD).
90 Transfers between the host and device are organized by channels and defined by
116 Events from the device to host are organized in event rings and defined by Event
|
| /openbmc/entity-manager/configurations/ |
| H A D | VENDORS.md | 4 organized into vendor-specific subdirectories. This begs the question "what is a
36 is intended to be organized. The overriding principle should be: if someone
|
| /openbmc/linux/arch/m68k/include/asm/ |
| H A D | mcfgpio.h | 94 /* These parts have GPIO organized by 8 bit ports */
103 /* These parts have GPIO organized by 16 bit ports */
112 /* These parts have GPIO organized by 32 bit ports */
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | sysv-fs.rst | 111 Free blocks are organized in a "free list". Maybe a misleading term,
113 the next free block. Rather, the free blocks are organized in chunks
209 * Regular file data blocks are organized as
|
| /openbmc/linux/drivers/w1/slaves/ |
| H A D | Kconfig | 74 organized as 7 pages of 16 bytes each with 64bit
82 This EEPROM is organized as one page of 32 bytes for random
|
| /openbmc/u-boot/drivers/w1-eeprom/ |
| H A D | Kconfig | 26 This device has 128 bytes of data memory, organized as 4 pages of
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/tokyocabinet/ |
| H A D | tokyocabinet_1.4.48.bb | 11 Records are organized in hash table, B+ tree, or fixed-length array."
|
| /openbmc/u-boot/arch/x86/include/asm/ |
| H A D | cmos_layout.h | 10 * The RTC internal registers and RAM is organized as two banks of 128 bytes
|
| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | berlin,pinctrl.txt | 6 controlled are organized in groups, so no actual pin information is
|
| H A D | sprd,pinctrl.txt | 3 The Spreadtrum pin controller are organized in 3 blocks (types).
|
| /openbmc/phosphor-dbus-monitor/src/ |
| H A D | propertywatch.cpp | 27 * An optimal start implementation requires objects organized in the
|
| /openbmc/linux/Documentation/arch/x86/x86_64/ |
| H A D | machinecheck.rst | 11 Machine checks are organized in banks (normally associated with
|
| /openbmc/linux/Documentation/devicetree/bindings/gpio/ |
| H A D | sprd,gpio.yaml | 16 The controller's registers are organized as sets of sixteen 16-bit
|
| H A D | gpio-mxs.yaml | 15 The GPIOs are organized in port/bank, each port consists of 32 GPIOs.
|
| H A D | brcm,brcmstb-gpio.yaml | 10 The controller's registers are organized as sets of eight 32-bit
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | index.rst | 8 of device drivers. This document is an only somewhat organized collection
|
| /openbmc/openbmc/poky/documentation/kernel-dev/ |
| H A D | concepts-appx.rst | 149 The features are tagged and organized by way of a branching strategy
179 organized to be specific for particular functionality, single kernel
229 are organized and tagged.
232 common to every kernel type and BSP that is organized further along in
|
| /openbmc/linux/include/linux/irqchip/ |
| H A D | irq-bcm2836.h | 41 * these bits are organized by mailbox number and then CPU number. We
|
| /openbmc/linux/Documentation/devicetree/bindings/clock/ |
| H A D | renesas,cpg-mstp-clocks.yaml | 14 organized in groups of up to 32 gates.
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | pixfmt-m420.rst | 17 (YUV 4:2:0). Pixels are organized as interleaved luma and chroma planes.
|
| /openbmc/entity-manager/schemas/ |
| H A D | README.md | 10 in a single file, or can be organized into several smaller files. Thus, the top
|
| /openbmc/qemu/include/hw/ppc/ |
| H A D | spapr_ovec.h | 4 * Each architecture option is organized/documented by the following
|
| /openbmc/linux/sound/firewire/dice/ |
| H A D | dice-interface.h | 27 * The registers are organized in several sections, which are organized
|
| /openbmc/openbmc/poky/documentation/toaster-manual/ |
| H A D | intro.rst | 21 interface are organized into projects. When you create a project, you
|
| /openbmc/linux/Documentation/driver-api/driver-model/ |
| H A D | device.rst | 77 organized as follows into a group::
|