| /OK3568_Linux_fs/kernel/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.
59 Generic PWM framework driver for Atmel SoC.
69 Generic PWM framework driver for the PWM output of the HLCDC
80 Generic PWM framework driver for Atmel Timer Counter Block.
[all …]
|
| /OK3568_Linux_fs/yocto/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 diff --git a/framework/egl/egluGLContextFactory.cpp b/framework/egl/egluGLContextFactory.cpp
24 --- a/framework/egl/egluGLContextFactory.cpp
25 +++ b/framework/egl/egluGLContextFactory.cpp
44 diff --git a/framework/egl/wrapper/eglwLibrary.cpp b/framework/egl/wrapper/eglwLibrary.cpp
46 --- a/framework/egl/wrapper/eglwLibrary.cpp
[all …]
|
| /OK3568_Linux_fs/kernel/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
45 Enable common clock framework support for Broadcom SoCs
52 Enable common clock framework support for Broadcom SoCs
61 Enable common clock framework support for the Broadcom Cygnus SoC
69 Enable common clock framework support for the Broadcom Hurricane 2
78 Enable common clock framework support for the Broadcom Northstar and
87 Enable common clock framework support for the Broadcom Northstar 2 SoC
[all …]
|
| /OK3568_Linux_fs/kernel/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
46 LSM Framework
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
[all …]
|
| /OK3568_Linux_fs/kernel/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.
|
| H A D | cec-core.rst | 6 The CEC framework provides a unified kernel interface for use with HDMI CEC
8 transmitters, USB dongles). The framework also gives the option to decide
11 feature into the kernel's remote control framework.
24 The CEC framework described here is up to date with the CEC 2.0 specification.
49 adapter operations which are called by the CEC framework and that you
212 driven) by calling into the framework in the following situations:
253 retrying messages. If set, then the framework assumes that it
291 handling the receive interrupt. The framework expects to see the cec_transmit_done
321 This basic parsing is done in the CEC Framework. It is up to the driver to decide
383 -ENOMSG, otherwise the CEC framework assumes it processed this message and
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/power/ |
| H A D | opp.rst | 52 CONFIG_PM as certain SoCs such as Texas Instrument's OMAP framework allows to
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
25 framework, and interested clients reading the data from it::
37 | Framework |
52 In case of CPU devices the EM framework manages power cost tables per
66 CONFIG_ENERGY_MODEL must be enabled to use the EM framework.
72 Drivers are expected to register performance domains into the EM framework by
114 performance domain in the Energy Model framework using the (fake) 'foo'
116 EM framework::
135 16 /* Return the values to the EM framework */
|
| /OK3568_Linux_fs/kernel/drivers/remoteproc/ |
| H A D | Kconfig | 21 framework. Userspace can boot/shutdown remote processors through
31 on iMX7D) via the remote processor framework.
50 the remote processor framework.
62 and DSP on OMAP4) via the remote processor framework.
68 offloaded to remote DSP processors using this framework).
103 remote processor framework.
107 offloaded to remote DSP processors using this framework).
123 via the remote processor framework.
244 processor framework.
257 remote processor framework.
[all …]
|
| /OK3568_Linux_fs/kernel/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:
40 SPI NOR framework
51 SPI NOR framework
57 Part III - How can drivers use the framework?
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v2/export-ta_arm32/include/ |
| H A D | tee_ta_api.h | 21 * are the entry points called by the Trusted Core Framework to create the
30 * constructor, which the Framework calls when it creates a new instance of
40 * The Framework MUST reclaim all resources and dereference all objects
51 * destructor, which the Framework calls when the instance is being
54 * When the function TA_DestroyEntryPoint is called, the Framework
72 * The Framework calls the function TA_OpenSessionEntryPoint when a client
85 * commands. When the client disconnects, the Framework will eventually
88 * If the function returns any error, the Framework rejects the connection
94 * by the Framework, and is simply passed back to other TA_ functions
97 * anything else, like an integer, a handle etc. The Framework will not
[all …]
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v2/export-ta_arm64/host_include/ |
| H A D | tee_ta_api.h | 21 * are the entry points called by the Trusted Core Framework to create the
30 * constructor, which the Framework calls when it creates a new instance of
40 * The Framework MUST reclaim all resources and dereference all objects
51 * destructor, which the Framework calls when the instance is being
54 * When the function TA_DestroyEntryPoint is called, the Framework
72 * The Framework calls the function TA_OpenSessionEntryPoint when a client
85 * commands. When the client disconnects, the Framework will eventually
88 * If the function returns any error, the Framework rejects the connection
94 * by the Framework, and is simply passed back to other TA_ functions
97 * anything else, like an integer, a handle etc. The Framework will not
[all …]
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v2/export-ta_arm64/include/ |
| H A D | tee_ta_api.h | 21 * are the entry points called by the Trusted Core Framework to create the
30 * constructor, which the Framework calls when it creates a new instance of
40 * The Framework MUST reclaim all resources and dereference all objects
51 * destructor, which the Framework calls when the instance is being
54 * When the function TA_DestroyEntryPoint is called, the Framework
72 * The Framework calls the function TA_OpenSessionEntryPoint when a client
85 * commands. When the client disconnects, the Framework will eventually
88 * If the function returns any error, the Framework rejects the connection
94 * by the Framework, and is simply passed back to other TA_ functions
97 * anything else, like an integer, a handle etc. The Framework will not
[all …]
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v2/export-ta_arm32/host_include/ |
| H A D | tee_ta_api.h | 21 * are the entry points called by the Trusted Core Framework to create the
30 * constructor, which the Framework calls when it creates a new instance of
40 * The Framework MUST reclaim all resources and dereference all objects
51 * destructor, which the Framework calls when the instance is being
54 * When the function TA_DestroyEntryPoint is called, the Framework
72 * The Framework calls the function TA_OpenSessionEntryPoint when a client
85 * commands. When the client disconnects, the Framework will eventually
88 * If the function returns any error, the Framework rejects the connection
94 * by the Framework, and is simply passed back to other TA_ functions
97 * anything else, like an integer, a handle etc. The Framework will not
[all …]
|
| /OK3568_Linux_fs/external/xserver/hw/xquartz/mach-startup/ |
| H A D | Makefile.am | 38 -Wl,-framework,Carbon \
39 -Wl,-framework,Cocoa \
40 -Wl,-framework,CoreAudio \
41 -Wl,-framework,IOKit
50 -Wl,-framework,OpenGL
55 -Wl,-framework,Sparkle
73 -Wl,-framework,CoreServices
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v1/export-user_ta/include/ |
| H A D | tee_ta_api.h | 43 * are the entry points called by the Trusted Core Framework to create the
52 * constructor, which the Framework calls when it creates a new instance of
62 * The Framework MUST reclaim all resources and dereference all objects
73 * destructor, which the Framework calls when the instance is being
76 * When the function TA_DestroyEntryPoint is called, the Framework
94 * The Framework calls the function TA_OpenSessionEntryPoint when a client
107 * commands. When the client disconnects, the Framework will eventually
110 * If the function returns any error, the Framework rejects the connection
116 * by the Framework, and is simply passed back to other TA_ functions
119 * anything else, like an integer, a handle etc. The Framework will not
[all …]
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v1/export-user_ta/host_include/ |
| H A D | tee_ta_api.h | 43 * are the entry points called by the Trusted Core Framework to create the
52 * constructor, which the Framework calls when it creates a new instance of
62 * The Framework MUST reclaim all resources and dereference all objects
73 * destructor, which the Framework calls when the instance is being
76 * When the function TA_DestroyEntryPoint is called, the Framework
94 * The Framework calls the function TA_OpenSessionEntryPoint when a client
107 * commands. When the client disconnects, the Framework will eventually
110 * If the function returns any error, the Framework rejects the connection
116 * by the Framework, and is simply passed back to other TA_ functions
119 * anything else, like an integer, a handle etc. The Framework will not
[all …]
|
| /OK3568_Linux_fs/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
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/drivers/gpu/arm/bifrost/backend/gpu/ |
| H A D | mali_kbase_model_linux.h | 23 * Model Linux Framework interfaces.
25 * This framework is used to provide generic Kbase Models interfaces.
28 * - Without Model Linux Framework:
35 * - With Model Linux Framework:
39 * | Model Linux Framework |
125 * This hook is global to the model Linux framework.
135 * This hook is global to the model Linux framework.
144 * This hook is global to the model Linux framework.
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/drivers/thermal/ |
| H A D | Kconfig | 24 The thermal framework has a netlink interface to do thermal
59 framework, this option will also register it
239 thermal framework. cpufreq is used as the cooling device to throttle
313 thermal framework.
324 framework.
356 thermal framework.
365 the Linux thermal framework.
374 framework. Only kirkwood 88F6282 and 88F6283 have this sensor.
383 framework.
391 management framework. A thermal zone with several trip points will be
[all …]
|
| /OK3568_Linux_fs/kernel/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.
|
| /OK3568_Linux_fs/kernel/drivers/acpi/dptf/ |
| H A D | Kconfig | 4 bool "Intel DPTF (Dynamic Platform and Thermal Framework) Support"
7 Intel Dynamic Platform and Thermal Framework (DPTF) is a platform
15 <https://01.org/intel%C2%AE-dynamic-platform-and-thermal-framework-dptf-chromium-os/overview>
23 This driver adds support for Dynamic Platform and Thermal Framework
39 This driver adds support for Dynamic Platform and Thermal Framework
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/phy/ |
| H A D | phy.rst | 7 This document explains the Generic PHY Framework along with the APIs provided,
21 The intention of creating this framework is to bring the PHY drivers spread
25 This framework will be of use only to devices that use external PHY (PHY
33 the PHY, the framework provides its own implementation of of_xlate in
78 to make use of it. The PHY framework provides 2 APIs to create the PHY.
100 it. This framework provides the following APIs to get a reference to the PHY.
138 PHY framework provides 2 APIs to release a reference to the PHY.
180 In order to get reference to a PHY without help from DeviceTree, the framework
185 The framework offers the following API for registering and unregistering the
|