| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | speeding-up-build.rst | 11 to gain more speed. See the descriptions in the glossary for each
|
| /openbmc/linux/Documentation/devicetree/bindings/power/supply/ |
| H A D | battery.yaml | 102 for each of the battery capacity lookup table.
|
| /openbmc/linux/Documentation/devicetree/bindings/power/ |
| H A D | mediatek,power-controller.yaml | 101 for each power domain we need to group the clocks by name. BASIC
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/intel/ |
| H A D | fm10k.rst | 85 each jumbo packet. This should help to avoid buffer starvation issues when
|
| /openbmc/linux/Documentation/filesystems/ext4/ |
| H A D | group_descr.rst | 9 standard configuration is for each block group to contain a full copy of
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | s390-drivers.rst | 94 data which is made available by the channel subsystem for each channel
|
| /openbmc/linux/Documentation/devicetree/bindings/interrupt-controller/ |
| H A D | ti,pruss-intc.yaml | 68 Should use one of the above names for each valid host event interrupt
|
| H A D | renesas,rzg2l-irqc.yaml | 16 interrupts output by each IP. And it notifies the interrupt to the GIC
|
| /openbmc/linux/Documentation/devicetree/bindings/usb/ |
| H A D | am33xx-usb.txt | 65 each USB instance.
|
| /openbmc/linux/Documentation/maintainer/ |
| H A D | messy-diffstat.rst | 9 diffstat that shows which files will be touched and how much of each will
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | packing.rst | 90 byte from each 4-byte word is placed at its mirrored position compared to
|
| /openbmc/linux/Documentation/devicetree/bindings/dma/xilinx/ |
| H A D | xilinx_dma.txt | 29 two channels per device. This node specifies the properties of each
|
| /openbmc/linux/arch/powerpc/platforms/8xx/ |
| H A D | Kconfig | 173 On the 8xx, we have 32 instruction TLBs and 32 data TLBs. In each
|
| /openbmc/linux/Documentation/arch/arm/ |
| H A D | microchip.rst | 20 Documentation and detailed datasheet for each product are available on
|
| /openbmc/linux/Documentation/devicetree/bindings/regulator/ |
| H A D | rohm,bd71837-regulator.yaml | 17 definition for each of these nodes is defined using the standard
|
| /openbmc/linux/Documentation/devicetree/bindings/i3c/ |
| H A D | i3c.yaml | 15 and a set of child nodes for each I2C or I3C slave on the bus. Each of them
|
| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | nuvoton,npcm845-pinctrl.yaml | 40 Eight GPIO banks that each contain 32 GPIOs.
|
| /openbmc/linux/Documentation/firmware-guide/acpi/dsd/ |
| H A D | phy.rst | 23 For each MAC node, a device property "phy-handle" is used to reference
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-subdev-g-fmt.rst | 60 same sub-device would thus not interact with each other.
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-ptp | 88 This directory contains one file for each programmable
|
| H A D | sysfs-class-rc | 15 A /sys/class/rc/rcN directory is created for each remote
|
| /openbmc/docs/designs/ |
| H A D | cper-records.md | 45 end that added records do not require manual effort to implement in each
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | NPL-1.1 | 50 … 1.1. "Contributor" means each entity that creates or contributes to the creation of Modifications.
54 …difications or the combination of the Original Code and Modifications, in each case including port…
89 …2.2. Contributor Grant. Subject to third party intellectual property claims, each Contributor here…
115 …3.5. Required Notices. You must duplicate the notice in Exhibit A in each file of the Source Code.…
165 As between Initial Developer and the Contributors, each party is responsible for claims and damages…
|
| /openbmc/linux/Documentation/mm/ |
| H A D | unevictable-lru.rst | 242 However, walking the reverse map for each page when munlocking was ugly and
292 for each VMA in the range specified by the call. In the case of mlockall(),
313 For each PTE (or PMD) being faulted into a VMA, the page add rmap function
489 For each PTE (or PMD) being unmapped from a VMA, page_remove_rmap() calls
514 for each PTE (or PMD) being unmapped from a VMA, page_remove_rmap() calls
|
| /openbmc/linux/Documentation/scheduler/ |
| H A D | sched-util-clamp.rst | 215 The rq has a bucket for each uclamp_id tunables: [UCLAMP_MIN, UCLAMP_MAX].
217 The range of each bucket is 1024/N. For example, for the default value of
218 5 there will be 5 buckets, each of which will cover the following range:
241 The rq then keeps track of its current effective uclamp value for each
537 200 or 1024 is different for each system. Unless there's a specific target
|