| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/vk-gl-cts/files/ |
| H A D | 0001-use-library-sonames-for-linking.patch | 14 framework/egl/egluGLContextFactory.cpp | 4 ++--
15 framework/egl/wrapper/eglwLibrary.cpp | 2 +-
16 framework/platform/android/tcuAndroidPlatform.cpp | 2 +-
17 framework/platform/lnx/X11/tcuLnxX11EglDisplayFactory.cpp | 2 +-
19 framework/platform/surfaceless/tcuSurfacelessPlatform.cpp | 6 +++---
22 --- a/framework/egl/egluGLContextFactory.cpp
23 +++ b/framework/egl/egluGLContextFactory.cpp
42 --- a/framework/egl/wrapper/eglwLibrary.cpp
43 +++ b/framework/egl/wrapper/eglwLibrary.cpp
53 --- a/framework/platform/android/tcuAndroidPlatform.cpp
[all …]
|
| H A D | fix-musl.patch | 3 --- a/framework/delibs/dethread/CMakeLists.txt
4 +++ b/framework/delibs/dethread/CMakeLists.txt
13 --- a/framework/qphelper/CMakeLists.txt
14 +++ b/framework/qphelper/CMakeLists.txt
|
| H A D | 0001-cmake-Define-WAYLAND_SCANNER-and-WAYLAND_PROTOCOLS_D.patch | 13 framework/platform/CMakeLists.txt | 8 ++++++--
16 --- a/framework/platform/CMakeLists.txt
17 +++ b/framework/platform/CMakeLists.txt
|
| /openbmc/linux/drivers/clk/bcm/ |
| H A D | Kconfig | 11 Enable common clock framework support for the Broadcom BCM2711
20 Enable common clock framework support for Broadcom BCM2835
29 Enable common clock framework support for Broadcom BCM63xx DSL SoCs
37 Enable common clock framework support for Broadcom BCM63xx DSL SoCs
54 Enable common clock framework support for Broadcom SoCs
61 Enable common clock framework support for Broadcom SoCs
70 Enable common clock framework support for the Broadcom Cygnus SoC
78 Enable common clock framework support for the Broadcom Hurricane 2
87 Enable common clock framework support for the Broadcom Northstar and
96 Enable common clock framework support for the Broadcom Northstar 2 SoC
[all …]
|
| /openbmc/linux/Documentation/driver-api/mtd/ |
| H A D | spi-nor.rst | 2 SPI NOR framework
5 Part I - Why do we need this framework?
20 Part II - How does the framework work?
23 This framework just adds a new layer between the MTD and the SPI bus driver.
27 Before this framework, the layer is like::
37 After this framework, the layer is like::
41 SPI NOR framework
53 SPI NOR framework
59 Part III - How can drivers use the framework?
|
| /openbmc/linux/drivers/pwm/ |
| H A D | Kconfig | 14 This framework provides a generic interface to PWM devices
18 drivers can request PWM devices and use the generic framework
21 This generic framework replaces the legacy PWM framework which
23 all legacy implementations have been ported to the framework
24 yet. The framework provides an API that is backward compatible
25 with the legacy framework so that existing client drivers
49 Generic PWM framework driver for Analog Baseband AB8500.
58 Generic PWM framework driver for PWM controller present on
71 Generic PWM framework driver for Atmel SoC.
81 Generic PWM framework driver for the PWM output of the HLCDC
[all …]
|
| /openbmc/linux/Documentation/driver-api/media/ |
| H A D | v4l2-intro.rst | 17 For a long time the framework was limited to the video_device struct for
19 (note that this document does not discuss the video_buf framework).
26 the lack of a framework.
28 So this framework sets up the basic building blocks that all drivers
29 need and this same framework should make it much easier to refactor
35 framework. It can be used as a template for real PCI video capture driver.
66 Structure of the V4L2 framework
69 The framework closely resembles the driver structure: it has a v4l2_device
74 The V4L2 framework also optionally integrates with the media framework. If a
76 will automatically appear in the media framework as entities.
|
| /openbmc/linux/Documentation/security/ |
| H A D | lsm.rst | 28 remarks that described a security framework he would be willing to
30 general framework that would provide a set of security hooks to control
33 framework could then be used by loadable kernel modules to implement any
38 such a framework. LSM was a joint development effort by several security
41 Linux kernel patch that implements this framework. The work was
43 report provides an overview of the framework and the capabilities
49 The LSM framework provides a general kernel framework to support
50 security modules. In particular, the LSM framework is primarily focused
53 framework does not provide any additional security; it merely provides
54 the infrastructure to support security modules. The LSM framework is
[all …]
|
| /openbmc/linux/Documentation/driver-api/fpga/ |
| H A D | intro.rst | 15 framework functionality that can be added that will benefit
17 seek out a solution that expands the framework for broad reuse.
21 The framework in the kernel is divided into:
29 includes the framework in fpga-mgr.c and the low level drivers that
46 If you are adding a new interface to the FPGA framework, add it on top
49 The FPGA Region framework (fpga-region.c) associates managers and
|
| /openbmc/linux/Documentation/power/ |
| H A D | opp.rst | 52 Instrument's OMAP framework allows to optionally boot at a certain OPP without
58 SoC framework -> modifies on required cases certain OPPs -> OPP layer
62 framework registers a set of initial OPPs per device with the OPP layer. This
64 This initial list contains a set of OPPs that the framework expects to be safely
70 As the system proceeds to operate, SoC framework may choose to make certain
73 SoC framework might choose to disable a higher frequency OPP to safely continue
89 the SoC specific framework which uses the OPP library. Similar care needs
95 device. It is expected that the SoC framework will register the OPP entries
98 operation. The SoC framework can subsequently control the availability of the
107 This function may be used by SoC framework to define a optimal list
[all …]
|
| H A D | energy-model.rst | 10 The Energy Model (EM) framework serves as an interface between drivers knowing
19 possible source of information on its own, the EM framework intervenes as an
40 framework, and interested clients reading the data from it::
67 In case of CPU devices the EM framework manages power cost tables per
81 CONFIG_ENERGY_MODEL must be enabled to use the EM framework.
92 formula in the framework (like it is in 'simple' EM case). It can better reflect
97 Drivers are expected to register performance domains into the EM framework by
119 The EM can also be registered using OPP framework and information in DT
141 and provide .get_cost() callback. The EM framework would handle such platform
149 The 'simple' EM is registered using the framework helper function
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-core/initrdscripts/ |
| H A D | initramfs-module-setup-live_1.0.bb | 1 SUMMARY = "initramfs-framework module for live booting"
4 RDEPENDS:${PN} = "initramfs-framework-base udev-extraconf"
9 FILESEXTRAPATHS:prepend := "${THISDIR}/initramfs-framework:"
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/mbedtls/ |
| H A D | mbedtls_3.6.2.bb | 27 …git://github.com/Mbed-TLS/mbedtls-framework.git;protocol=https;branch=main;destsuffix=git/framewor…
77 install -d ${D}${PTEST_PATH}/framework
80 cp -fR ${S}/framework/data_files ${D}${PTEST_PATH}/framework/
|
| /openbmc/linux/tools/perf/Documentation/ |
| H A D | Build.txt | 22 main makefile of the build framework
25 build framework generic definitions
31 information about build framework.
36 The Makefile.perf triggers the build framework for build objects:
49 focusing on build framework outcomes
|
| /openbmc/linux/drivers/remoteproc/ |
| H A D | Kconfig | 21 framework. Userspace can boot/shutdown remote processors through
33 processor framework.
44 processor framework.
63 the remote processor framework.
75 and DSP on OMAP4) via the remote processor framework.
81 offloaded to remote DSP processors using this framework).
116 remote processor framework.
120 offloaded to remote DSP processors using this framework).
136 via the remote processor framework.
158 subsystem via the remote processor framework.
[all …]
|
| /openbmc/linux/drivers/thermal/st/ |
| H A D | Kconfig | 16 tristate "Thermal framework support on STMicroelectronics STM32 series of SoCs"
20 Support for thermal framework on STMicroelectronics STM32 series of
21 SoCs. This thermal driver allows to access to general thermal framework
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
| H A D | testing.md | 6 [GoogleTest](https://github.com/google/googletest) framework. These tests are
22 ## Mock framework
38 The GoogleTest mock framework is used to implement mocking. This allows the
42 The mock framework typically relies on a class hierarchy of the following form:
|
| /openbmc/linux/Documentation/watchdog/ |
| H A D | convert_drivers_to_kernel_api.rst | 2 Converting old watchdog drivers to the watchdog framework
7 Before the watchdog framework came into the kernel, every driver had to
8 implement the API on its own. Now, as the framework factored out the common
9 components, those drivers can be lightened making it a user of the framework.
18 etc... These are now handled by the framework and just call the driver when
31 - write: Can simply go, all defined behaviour is taken care of by the framework,
35 the most common ones are handled by the framework, supported by some assistance
71 -ENOIOCTLCMD, the IOCTLs of the framework will be tried, too. Any other error
93 miscdevice'. The framework will create it on watchdog_dev_register() called by
156 necessary information for the framework. The struct is also explained in detail
|
| /openbmc/linux/drivers/media/cec/platform/ |
| H A D | Kconfig | 24 generic CEC framework interface.
39 It uses the generic CEC framework interface.
62 generic CEC framework interface.
73 generic CEC framework interface.
85 generic CEC framework interface.
96 generic CEC framework interface.
|
| /openbmc/u-boot/drivers/pinctrl/aspeed/ |
| H A D | Kconfig | 7 Generic Pinctrl framework and is compatible with the Linux driver,
16 Generic Pinctrl framework and is compatible with the Linux driver,
25 Generic Pinctrl framework and is compatible with the Linux driver,
|
| /openbmc/u-boot/drivers/phy/ |
| H A D | Kconfig | 10 This framework is designed to provide a generic interface for PHY
17 compatible as possible with the equivalent framework found in the
26 This framework is designed to provide a generic interface for PHY
33 compatible as possible with the equivalent framework found in the
42 the unit tests for the phy framework
50 This is useful when a driver uses the PHY framework but no real PHY
59 This is useful when a driver uses the PHY framework but no real PHY
|
| /openbmc/linux/Documentation/dev-tools/kunit/ |
| H A D | index.rst | 21 This section details the kernel unit testing framework.
26 KUnit (Kernel unit testing framework) provides a common framework for
33 (C++ unit testing framework).
55 - Provides a framework for writing unit tests.
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-aiohttp_3.11.11.bb | 1 SUMMARY = "Async http client/server framework"
2 DESCRIPTION = "Asynchronous HTTP client/server framework for asyncio and Python"
|
| /openbmc/openbmc/poky/meta/recipes-devtools/dejagnu/ |
| H A D | dejagnu_1.6.3.bb | 1 SUMMARY = "GNU unit testing framework, written in Expect and Tcl"
2 DESCRIPTION = "DejaGnu is a framework for testing other programs. Its purpose \
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | clk.rst | 7 This document endeavours to explain the common clk framework details,
8 and how to port a platform over to this framework. It is not yet a
15 The common clk framework is an interface to control the clock nodes
17 gating, rate adjustment, muxing or other operations. This framework is
22 clk which unifies the framework-level accounting and infrastructure that
122 framework code and struct clk_core.
245 data and then passes the common struct clk parameters to the framework
272 The common clock framework uses two global locks, the prepare lock and the
303 The clock framework is reentrant, in that a driver is allowed to call clock
304 framework functions from within its implementation of clock operations. This
[all …]
|