Searched full:framework (Results 1 – 25 of 1342) sorted by relevance
12345678910>>...54
| /Linux-v6.1/drivers/pwm/ |
| 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
81 Generic PWM framework driver for Atmel Timer Counter Block.
[all …]
|
| /Linux-v6.1/drivers/clk/bcm/ |
| 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 …]
|
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/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
226 driven) by calling into the framework in the following situations:
267 retrying messages. If set, then the framework assumes that it
305 handling the receive interrupt. The framework expects to see the cec_transmit_done
335 This basic parsing is done in the CEC Framework. It is up to the driver to decide
397 -ENOMSG, otherwise the CEC framework assumes it processed this message and
[all …]
|
| /Linux-v6.1/drivers/remoteproc/ |
| 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 …]
|
| /Linux-v6.1/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
81 CONFIG_ENERGY_MODEL must be enabled to use the EM framework.
92 formula in the framework (like it's 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
[all …]
|
| /Linux-v6.1/Documentation/driver-api/mtd/ |
| 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?
|
| /Linux-v6.1/drivers/thermal/ |
| D | Kconfig | 24 The thermal framework has a netlink interface to do thermal
59 framework, this option will also register it
119 information about the thermal framework events.
241 thermal framework. cpufreq is used as the cooling device to throttle
315 thermal framework.
326 framework.
348 thermal framework.
357 the Linux thermal framework.
366 thermal framework.
375 framework. Only kirkwood 88F6282 and 88F6283 have this sensor.
[all …]
|
| /Linux-v6.1/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
|
| /Linux-v6.1/drivers/media/cec/platform/ |
| 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.
|
| /Linux-v6.1/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
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
|
| /Linux-v6.1/include/linux/ |
| D | clk-provider.h | 14 * top-level framework. custom flags for dealing with hardware specifics
285 * shared between the clock provider and the common clock framework.
295 * @flags: framework-level hints and quirks
321 * with the common clock framework. This pointer will be set to NULL once
371 * framework
375 * @flags: framework-specific flags
384 * framework
388 * @flags: framework-specific flags
396 * the clock framework
400 * @flags: framework-specific flags
[all …]
|
| /Linux-v6.1/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.
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
|
| /Linux-v6.1/tools/perf/Documentation/ |
| 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
|
| /Linux-v6.1/drivers/acpi/dptf/ |
| D | Kconfig | 4 bool "Intel DPTF (Dynamic Platform and Thermal Framework) Support"
7 Intel Dynamic Platform and Thermal Framework (DPTF) is a platform
20 This driver adds support for Dynamic Platform and Thermal Framework
36 This driver adds support for Dynamic Platform and Thermal Framework
|
| /Linux-v6.1/tools/testing/selftests/resctrl/ |
| D | README | 15 resctrl_tests can be run with or without kselftest framework.
17 WITH KSELFTEST FRAMEWORK
31 Using kselftest framework will run all supported tests within resctrl_tests:
35 More details about kselftest framework can be found in
38 WITHOUT KSELFTEST FRAMEWORK
|
| /Linux-v6.1/tools/build/Documentation/ |
| D | Build.txt | 1 Build Framework
4 The perf build framework was adopted from the kernel build system, hence the
15 Build framework makefiles
18 The build framework consists of 2 Makefiles:
63 The build framework does not create the 'ex' and 'libex.a' binaries for you, it
126 The build framework provides standard compilation rules to handle .S and .c
|
| /Linux-v6.1/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::
|
| /Linux-v6.1/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
|
| /Linux-v6.1/drivers/thermal/st/ |
| D | Kconfig | 20 tristate "Thermal framework support on STMicroelectronics STM32 series of SoCs"
24 Support for thermal framework on STMicroelectronics STM32 series of
25 SoCs. This thermal driver allows to access to general thermal framework
|
| /Linux-v6.1/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
|
| /Linux-v6.1/Documentation/dev-tools/kunit/ |
| D | index.rst | 22 This section details the kernel unit testing framework.
27 KUnit (Kernel unit testing framework) provides a common framework for
34 (C++ unit testing framework).
56 - Provides a framework for writing unit tests.
|
| /Linux-v6.1/drivers/fpga/ |
| D | Kconfig | 3 # FPGA framework configuration
7 tristate "FPGA Configuration Framework"
10 kernel. The FPGA framework adds an FPGA manager class and FPGA
95 tristate "FPGA Bridge Framework"
170 under Device Feature List (DFL) framework. Select this option to
223 management and virtualization with DFL framework and DFL feature
|
12345678910>>...54
