Home
last modified time | relevance | path

Searched full:itself (Results 1 – 25 of 3725) sorted by relevance

12345678910>>...149

/openbmc/openpower-hw-diags/analyzer/
H A Dresolution.hpp34 * chip. An empty string refers to the chip itself.
45 * refers to the chip itself. */
66 * other chip. An empty string refers to the chip itself,
83 * empty string refers to the chip itself, which generally means this chip
108 * other chip. An empty string refers to the chip itself,
125 * empty string refers to the chip itself, which generally means this chip
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-hypervisor-xen22 "self" The guest can profile itself
23 "hv" The guest can profile itself and, if it is
25 "all" The guest can profile itself, the hypervisor
H A Dsysfs-firmware-dmi-entries10 The kernel itself does not rely on the majority of the
45 assigned entry handles as the kernel itself makes no
58 entry itself. Note that this is _not the
/openbmc/linux/drivers/xen/
H A Dxen-front-pgdir-shbuf.c89 * shared by the frontend itself) or map the provided granted
110 * shared by the frontend itself) or unmap the provided granted
154 * Get the number of pages the page directory consumes itself.
171 /* Only for pages the page directory consumes itself. */ in backend_calc_num_grefs()
184 * Number of pages the page directory consumes itself in guest_calc_num_grefs()
268 * so buf->num_grefs has number of pages in the page directory itself. in backend_map()
325 * page directory itself.
341 /* Fill only grefs for the page directory itself. */ in backend_fill_page_dir()
369 * granted for the page directory itself. in guest_fill_page_dir()
/openbmc/u-boot/scripts/kconfig/tests/warn_recursive_dep/
H A DKconfig1 # depends on itself
7 # select itself
/openbmc/u-boot/doc/driver-model/
H A DMIGRATION.txt14 The subsystem itself has been converted and maintainers should submit patches
24 The subsystem itself has been converted along with many of the host controller
34 The subsystem itself has been converted along with many of the host controller
H A Dusb-info.txt67 call ehci_register() to register itself as an EHCI device. It should call
69 does not by itself cause the bus to be scanned.
85 this structure, even the root hub. The controller itself does not
117 root hub attached to it. This hub, which is itself a USB device, can provide
134 time, and each is given sufficient time to wake up and announce itself. The
150 device itself - i.e. they don't pass down the stack to the controller.
291 uclass and declares itself as follows:
/openbmc/linux/scripts/kconfig/tests/err_recursive_dep/
H A DKconfig3 # depends on itself
9 # select itself
/openbmc/openbmc/poky/meta/files/common-licenses/
H A DGPL-3-with-bison-exception5itself a parser generator using the skeleton or a modified version thereof as a parser skeleton. A…
H A DGPL-2-with-bison-exception5itself a parser generator using the skeleton or a modified version thereof as a parser skeleton. A…
/openbmc/linux/Documentation/tools/rv/
H A Dcommon_ikm.rst12 command itself. If the **rv** command itself generates too many events,
/openbmc/linux/drivers/hwmon/occ/
H A DKconfig14 the P8, not the POWER processor itself. Communications with the OCC are
28 the P9, not the POWER processor itself. Communications with the OCC are
/openbmc/linux/Documentation/ABI/stable/
H A Dsysfs-driver-usb-usbtmc7 by the device itself. The full description of the bitfields
21 by the device itself. The full description of the bitfields
/openbmc/linux/include/linux/
H A Dposix-clock.h99 * A clock driver calls this function to register itself with the
112 * A clock driver calls this function to remove itself from the clock
113 * device subsystem. The posix_clock itself will remain (in an
/openbmc/linux/drivers/char/
H A Dnwbutton.h10 #ifdef __NWBUTTON_C /* Actually compiling the driver itself */
34 #else /* Not compiling the driver itself */
/openbmc/linux/Documentation/security/tpm/
H A Dtpm_ftpm_tee.rst19 implemented in firmware. The driver itself doesn't contain much logic and is
22 The firmware itself is based on the following paper:
/openbmc/u-boot/doc/
H A DREADME.ramboot-ppc85xx7 itself.
43 - In case of SD card and SPI flash bootloader this is done by On Chip BootROM inside the Si itself.
44 - In case of NAND boot SPL/TPL code does it with some support from Si itself.
H A DREADME.arm-relocation53 d) this initialize CPU, RAM, ... and copy itself to RAM
59 the relocation address and copy itself to it
88 which inits the dram, cpu registers, reloacte itself to CONFIG_SPL_TEXT_BASE and loads
93 where it has to copy and relocate itself to this address. If
/openbmc/linux/Documentation/devicetree/bindings/i2c/
H A Di2c-opal.txt5 used by the firmware itself for configuring the port. From the linux
21 The node contains a number of other properties that are used by the FW itself
/openbmc/u-boot/tools/binman/etype/
H A Dtext.py15 The text can be provided either in the node itself or by a command-line
46 The text is not itself nul-terminated. This can be achieved, if required,
/openbmc/linux/Documentation/filesystems/ext4/
H A Dverity.rst12 stored after the end of the file data itself, in the following format:
38 is encrypted as well as the data itself.
/openbmc/u-boot/include/configs/
H A Dtegra30-common.h32 * decompress itself to 0x8000 after the start of RAM, kernel_addr_r
33 * should not overlap that area, or the kernel will have to copy itself
H A Dtegra210-common.h31 * decompress itself to 0x8000 after the start of RAM, kernel_addr_r
32 * should not overlap that area, or the kernel will have to copy itself
/openbmc/linux/tools/perf/pmu-events/arch/arm64/arm/cortex-a73/
H A Dcache.json102 "PublicDescription": "Data cache hit in itself due to VIPT aliasing",
105 "BriefDescription": "Data cache hit in itself due to VIPT aliasing"
/openbmc/linux/Documentation/gpu/rfc/
H A Dxe.rst92 As a key measurable result, the patch series introducing Xe itself shall not
93 depend on any other patch touching drm_scheduler itself that was not yet merged
94 through drm-misc. This, by itself, already includes the reach of an agreement for
149 extent this is already getting addressed itself with the GPUVA where likely the
225 of devcoredump infrastructure itself.

12345678910>>...149