Home
last modified time | relevance | path

Searched full:hardware (Results 1 – 25 of 4407) sorted by relevance

12345678910>>...177

/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-kernel/linux/arm-platforms-kmeta/bsp/arm-platforms/
H A Djuno.scc8 kconf hardware juno/juno-board.cfg
9 kconf hardware juno/juno-devfreq.cfg
10 kconf hardware juno/juno-dma.cfg
11 kconf hardware juno/juno-drm.cfg
12 kconf hardware juno/juno-fb.cfg
13 kconf hardware juno/juno-i2c.cfg
14 # kconf hardware juno/juno-mali-midgard.cfg
15 kconf hardware juno/juno-mmc.cfg
16 kconf hardware juno/juno-net.cfg
17 kconf hardware juno/juno-pci.cfg
[all …]
H A Dfvp.scc6 kconf hardware fvp/fvp-board.cfg
7 kconf hardware fvp/fvp-net.cfg
8 kconf hardware fvp/fvp-rtc.cfg
9 kconf hardware fvp/fvp-serial.cfg
10 kconf hardware fvp/fvp-cfi.cfg
11 kconf hardware fvp/fvp-drm.cfg
12 kconf hardware fvp/fvp-watchdog.cfg
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/HardwareIsolation/
H A DEntry.interface.yaml2 Implement to provide the isolated hardware entry attributes.
6 example, isolated hardware inventory path and error log if it caused to
7 isolate hardware. The isolated hardware association of forward and reverse
14 isolated hardware object.
17 xyz.openbmc_project.Time.EpochTime for the isolated hardware creation time.
23 The severity of hardware isolation.
28 The isolated hardware resolution status is used to indicate whether
29 the isolated hardware is repaired or replaced. Setting this to "true"
31 isolated hardware entries may not be deleted and used for further
37 Possible severity for hardware isolation.
[all …]
H A DCreate.interface.yaml4 the information of isolated hardware.
10 the hardware, needs to be isolated. This interface can be used if want
11 to isolate hardware without an error log, for example, the user
12 voluntarily tried to isolate hardware.
17 The hardware inventory path which is needs to isolate.
21 The severity of hardware isolation.
38 the hardware, needs to be isolated. This interface can be used if the
39 system wants to isolate hardware with an error log that is caused to
40 isolate hardware. This method is not going to create an error log and
47 The hardware inventory path which is needs to isolate.
[all …]
/openbmc/linux/tools/testing/selftests/powerpc/pmu/event_code_tests/
Dhw_cache_event_type_test.c
/openbmc/u-boot/include/
H A Dhwspinlock.h11 * Hardware spinlocks are used to perform hardware protection of
18 * struct hwspinlock - A handle to (allowing control of) a single hardware
21 * @dev: The device which implements the hardware spinlock.
22 * @id: The hardware spinlock ID within the provider.
32 * hwspinlock_get_by_index - Get a hardware spinlock by integer index
34 * This looks up and request a hardware spinlock. The index is relative to the
35 * client device; each device is assumed to have n hardware spinlock associated
39 * @index: The index of the hardware spinlock to request, within the
40 * client's list of hardware spinlock.
41 * @hws: A pointer to a hardware spinlock struct to initialize.
[all …]
/openbmc/linux/Documentation/devicetree/bindings/spi/
Dsprd,spi-adi.yaml
/openbmc/openbmc/meta-ibm/recipes-phosphor/logging/
H A Dphosphor-logging_%.bbappend5 SRC_URI:append:p10bmc = " file://com.ibm.Hardware.Chassis.Model.Rainier2U_dev_callouts.json"
6 SRC_URI:append:p10bmc = " file://com.ibm.Hardware.Chassis.Model.Rainier4U_dev_callouts.json"
7 SRC_URI:append:p10bmc = " file://com.ibm.Hardware.Chassis.Model.Everest_dev_callouts.json"
8 SRC_URI:append:p10bmc = " file://com.ibm.Hardware.Chassis.Model.Bonnell_dev_callouts.json"
9 FILES:${PN}:append:p10bmc = " ${datadir}/phosphor-logging/pels/com.ibm.Hardware.Chassis.Model.Raini…
10 FILES:${PN}:append:p10bmc = " ${datadir}/phosphor-logging/pels/com.ibm.Hardware.Chassis.Model.Raini…
11 FILES:${PN}:append:p10bmc = " ${datadir}/phosphor-logging/pels/com.ibm.Hardware.Chassis.Model.Evere…
12 FILES:${PN}:append:p10bmc = " ${datadir}/phosphor-logging/pels/com.ibm.Hardware.Chassis.Model.Bonne…
20 …44 ${UNPACKDIR}/com.ibm.Hardware.Chassis.Model.Rainier2U_dev_callouts.json ${D}/${datadir}/phospho…
21 …44 ${UNPACKDIR}/com.ibm.Hardware.Chassis.Model.Rainier4U_dev_callouts.json ${D}/${datadir}/phospho…
[all …]
/openbmc/docs/designs/
H A Derror-log-handling-for-phal.md1 # Error handling for power Hardware Abstraction Layer (pHAL)
12 power Hardware Abstraction Layer(pHAL) library calls to [Platform Event Log][1]
17 OpenBmc Applications use the pHAL layer for hardware access and hardware
18 initialization, any software/hardware error returned by the pHAL layer need to
24 refers to the action of "guarding" faulty hardware from impacting future system
25 operation. Callout points to a specific hardware with in the server that relates
35 3. libekb for hardware procedure execution
36 4. libpdbg for hardware access
44 pHAL: power Hardware Abstraction Layer. pHAL is group of libraries running in
45 BMC. These libraries are used by Open Power specific application for hardware
[all …]
H A Dredfish-pcie.md35 from hardware. The consumer will retrieve and parse the D-Bus data to provide
42 gathering and caching PCIe hardware data and maintaining the D-Bus interfaces
43 and properties. The actual hardware mechanism that is used to gather the PCIe
44 hardware data will vary.
51 When reading hardware directly, the PCIe daemon must be aware of power state
52 changes and any BIOS timing requirements, so it can check for hardware changes,
66 Possible performance impact on the hardware-scanning and D-Bus updates. The
67 piece that implements hardware scanning should use mechanisms, such as caching
68 of the hardware configuration, to minimize the scanning time and updates to
/openbmc/linux/drivers/hwspinlock/
DKconfig
/openbmc/phosphor-dbus-interfaces/gen/com/meta/Hardware/
H A Dmeson.build8 sdbusplus_current_path = 'com/meta/Hardware'
11 'com/meta/Hardware/BMC__markdown'.underscorify(),
12 input: ['../../../../yaml/com/meta/Hardware/BMC.interface.yaml'],
25 'com/meta/Hardware/BMC',
33 'com/meta/Hardware/Harma__markdown'.underscorify(),
34 input: ['../../../../yaml/com/meta/Hardware/Harma.interface.yaml'],
47 'com/meta/Hardware/Harma',
55 'com/meta/Hardware/Minerva__markdown'.underscorify(),
56 input: ['../../../../yaml/com/meta/Hardware/Minerva.interface.yaml'],
69 'com/meta/Hardware/Minerva',
[all …]
/openbmc/u-boot/drivers/hwspinlock/
H A DKconfig1 menu "Hardware Spinlock Support"
4 bool "Enable U-Boot hardware spinlock support"
6 This option enables U-Boot hardware spinlock support
9 bool "Enable Hardware Spinlock support for Sandbox"
12 Enable hardware spinlock support in Sandbox. This is a dummy device that
17 bool "Enable Hardware Spinlock support for STM32"
20 Enable hardware spinlock support in STM32MP. Hardware spinlocks are
21 hardware mutex which provide a synchronisation mechanism for the
/openbmc/linux/tools/testing/selftests/net/forwarding/
Dfib_offload_lib.sh
/openbmc/linux/tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/
Dcache.json
/openbmc/openbmc-test-automation/gui/test/server_health/
H A Dtest_obmc_gui_hardware_status.robot3 Documentation Test OpenBMC GUI "Hardware status" sub-menu of "Server health".
27 [Documentation] Verify ability to select "Hardware status" sub-menu option
31 Wait Until Page Contains Hardware status
32 Page should contain All hardware in the system
36 [Documentation] Verify ability to export inventory from "Hardware status"
45 [Documentation] Verify search text input allowed from "Hardware status"
57 [Documentation] Verify search text allowed to clear from "Hardware status"
70 ... "Hardware status" sub-menu.
72 [Template] Verify Hardware Inventory Expand
90 Verify Hardware Inventory Expand
[all …]
/openbmc/openbmc/poky/documentation/kernel-dev/
H A Dconcepts-appx.rst35 needs for targeted hardware.
337 Determining Hardware and Non-Hardware Features for the Kernel Configuration Audit Phase
354 warnings, the system only reports missing "hardware" options as they
355 could result in a boot failure or indicate that important hardware is
358 To determine whether or not a given option is "hardware" or
359 "non-hardware", the kernel Metadata in ``yocto-kernel-cache`` contains
360 files that classify individual or groups of options as either hardware
361 or non-hardware. To better show this, consider a situation where the
364 yocto-kernel-cache/features/drm-psb/hardware.cfg
365 yocto-kernel-cache/features/kgdb/hardware.cfg
[all …]
/openbmc/linux/Documentation/networking/devlink/
Ddevlink-dpipe.rst
/openbmc/linux/Documentation/driver-api/usb/
Dgadget.rst
/openbmc/linux/drivers/mtd/nand/raw/ingenic/
DKconfig
/openbmc/linux/arch/mips/boot/dts/brcm/
Dbcm63268-comtrend-vr-3032u.dts
/openbmc/openbmc/poky/meta/recipes-core/busybox/files/
H A Dhwclock.sh9 # Description: Set system clock to hardware clock, according to the UTC
13 # WARNING: If your hardware clock is not in UTC/GMT, this script
31 echo "Setting the System Clock using the Hardware Clock as reference..."
51 # Updates the Hardware Clock with the System Clock time.
52 # This will *override* any changes made to the Hardware Clock.
59 echo "Saving the System Clock time to the Hardware Clock..."
67 echo "Hardware Clock updated to `date`."
79 echo " start sets kernel (system) clock from hardware (RTC) clock" >&2
80 echo " stop and reload set hardware (RTC) clock from kernel (system) clock" >&2
/openbmc/linux/Documentation/driver-api/media/
Dcec-core.rst
/openbmc/linux/drivers/clk/ingenic/
DKconfig
/openbmc/linux/Documentation/arch/x86/
Dsva.rst

12345678910>>...177