Searched full:framework (Results 1 – 25 of 254) sorted by relevance
1234567891011
| /Documentation/driver-api/media/ |
| 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.
|
| 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
239 driven) by calling into the framework in the following situations:
280 retrying messages. If set, then the framework assumes that it
318 handling the receive interrupt. The framework expects to see the cec_transmit_done
348 This basic parsing is done in the CEC Framework. It is up to the driver to decide
421 -ENOMSG, otherwise the CEC framework assumes it processed this message and
[all …]
|
| /Documentation/security/ |
| 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 …]
|
| /Documentation/driver-api/fpga/ |
| 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
|
| /Documentation/power/ |
| 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 …]
|
| 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::
52 | Framework |
67 In case of CPU devices the EM framework manages power cost tables per
77 scheduler, also uses RCU to access this memory. The EM framework provides
83 framework will handle the clean-up when it's possible.
106 CONFIG_ENERGY_MODEL must be enabled to use the EM framework.
117 formula in the framework (like it is in 'simple' EM case). It can better reflect
122 Drivers are expected to register performance domains into the EM framework by
[all …]
|
| /Documentation/watchdog/ |
| 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
92 miscdevice'. The framework will create it on watchdog_dev_register() called by
155 necessary information for the framework. The struct is also explained in detail
|
| /Documentation/driver-api/phy/ |
| 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.
101 it. This framework provides the following APIs to get a reference to the PHY.
165 PHY framework provides 2 APIs to release a reference to the PHY.
207 In order to get reference to a PHY without help from DeviceTree, the framework
212 The framework offers the following API for registering and unregistering the
|
| /Documentation/dev-tools/kunit/ |
| D | index.rst | 30 This section details the kernel unit testing framework.
35 KUnit (Kernel unit testing framework) provides a common framework for
42 (C++ unit testing framework).
64 - Provides a framework for writing unit tests.
|
| /Documentation/power/powercap/ |
| D | dtpm.rst | 4 Dynamic Thermal Power Management framework
26 The DTPM framework provides an unified interface to act on the
32 The DTPM framework relies on the powercap framework to create the
125 As stated in the overview, the DTPM framework is built on top of the
126 powercap framework. Thus the sysfs interface is the same, please refer
164 The DTPM framework has no power limiting backend support. It is
|
| /Documentation/devicetree/bindings/firmware/ |
| D | mediatek,geniezone.yaml | 15 Execution Environment) and AVF (Android Virtualization Framework) virtual
17 Android Virtualization Framework (AVF) with Crosvm as the VMM. The driver
|
| /Documentation/driver-api/ |
| D | nvmem.rst | 9 This document explains the NVMEM Framework along with the APIs provided,
18 Before this framework existed, NVMEM drivers like eeprom were stored in
27 This framework aims at solve these problems. It also introduces DT
82 them with the nvmem framework from machine code as shown in the example below::
103 The NVMEM framework provides 3 APIs to read/write NVMEM cells::
123 To facilitate such consumers NVMEM framework provides below apis::
151 The NVMEM framework provides 2 APIs to release a reference to the NVMEM::
|
| D | clk.rst | 2 The Common Clk Framework
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
[all …]
|
| D | regulator.rst | 17 This framework is designed to provide a standard kernel interface to
61 This offers a similar API to the kernel clock framework. Consumer
72 A stub version of this API is provided when the regulator framework is
156 Due to limitations of the kernel documentation framework and the
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-vduse | 7 framework and provides a sysfs interface for configuring
16 of VDUSE framework.
|
| D | rtc-cdev | 45 also supported by the newer RTC class framework. However,
49 by the RTC class framework, but can't be supported by the older
|
| /Documentation/driver-api/hte/ |
| D | hte.rst | 21 engine (HTE) framework. Both consumers and providers must include
24 The HTE framework APIs for the providers
30 The HTE framework APIs for the consumers
36 The HTE framework public structures
|
| D | tegra-hte.rst | 23 consumers timestamp requests go through GPIOLIB CDEV framework to HTE
42 this GTE instance in the HTE framework.
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-ioc-g-mode.rst | 47 When a CEC message is received, then the CEC framework will decide how
50 is waiting for it. In addition the CEC framework will process it.
52 If the message is not a reply, then the CEC framework will process it
54 feature abort is sent back to the initiator if the framework couldn't
57 the new message. The framework expects the follower to make the right
60 The CEC framework will process core messages unless requested otherwise
62 case, the CEC framework will pass on most core messages without
151 framework for that. If someone else is already the exclusive
272 - The CEC framework will make note of the reported physical address
|
| /Documentation/driver-api/thermal/ |
| D | exynos_thermal.rst | 59 When an interrupt occurs, this driver notify kernel thermal framework
69 Kernel Core thermal framework
89 Kernel core thermal framework. They are exynos_unregister_thermal,
|
| /Documentation/devicetree/bindings/sound/ |
| D | ti,tlv320adc3xxx.yaml | 62 GPIO framework, as pin number 0 on the device.
80 GPIO framework, as pin number 1 on the device.
88 When set, the MICBIAS1 pin may be controlled via the GPIO framework,
98 When set, the MICBIAS2 pin may be controlled via the GPIO framework,
|
| /Documentation/mm/damon/ |
| D | index.rst | 7 DAMON is a Linux kernel subsystem that provides a framework for data access
18 Using this framework, therefore, the kernel can operate system in an
|
| /Documentation/power/regulator/ |
| D | overview.rst | 2 Linux voltage and current regulator framework
8 This framework is designed to provide a standard kernel interface to control
138 The framework is designed and targeted at SoC based devices but may also be
174 The framework also exports a lot of useful voltage/current/opmode data to
|
| /Documentation/timers/ |
| D | highres.rst | 47 John Stultz's Generic Time Of Day (GTOD) framework moves a large portion of
49 framework, as illustrated in figure #3 (OLS slides p. 18). The architecture
51 sources, which are registered in the framework and selected on a quality based
58 Further information about the Generic Time Of Day framework is available in the
125 The framework adds about 700 lines of code which results in a 2KB increase of
147 useful function. The initialization of the clock event device framework, the
148 clock source framework (GTOD) and hrtimers itself has to be done and
|
| /Documentation/mhi/ |
| D | topology.rst | 24 * Allocates struct mhi_controller and registers with the MHI bus framework
56 * Registers the driver with the MHI bus framework using mhi_driver_register.
|
1234567891011