Searched full:framework (Results 1 – 25 of 1210) sorted by relevance
12345678910>>...49
| /linux-5.10/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
80 Generic PWM framework driver for Atmel Timer Counter Block.
[all …]
|
| /linux-5.10/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-5.10/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-5.10/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
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 …]
|
| /linux-5.10/drivers/remoteproc/ |
| 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 …]
|
| /linux-5.10/Documentation/power/ |
| 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 …]
|
| 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 */
|
| /linux-5.10/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:
40 SPI NOR framework
51 SPI NOR framework
57 Part III - How can drivers use the framework?
|
| /linux-5.10/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-5.10/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
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
|
| /linux-5.10/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-5.10/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-5.10/drivers/thermal/ |
| 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.
346 thermal framework.
355 the Linux thermal framework.
364 framework. Only kirkwood 88F6282 and 88F6283 have this sensor.
373 framework.
381 management framework. A thermal zone with several trip points will be
[all …]
|
| /linux-5.10/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-5.10/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-5.10/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
30 framework is based on regmap, so that most of the abstraction available in
86 them with the nvmem framework from machine code as shown in the example below::
107 The NVMEM framework provides 3 APIs to read/write NVMEM cells::
127 To facilitate such consumers NVMEM framework provides below apis::
155 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
267 The common clock framework uses two global locks, the prepare lock and the
298 The clock framework is reentrant, in that a driver is allowed to call clock
[all …]
|
| /linux-5.10/include/linux/ |
| D | clk-provider.h | 14 * top-level framework. custom flags for dealing with hardware specifics
273 * shared between the clock provider and the common clock framework.
283 * @flags: framework-level hints and quirks
309 * with the common clock framework. This pointer will be set to NULL once
359 * framework
363 * @flags: framework-specific flags
371 * the clock framework
375 * @flags: framework-specific flags
384 * the clock framework
388 * @flags: framework-specific flags
[all …]
|
| /linux-5.10/drivers/fpga/ |
| D | Kconfig | 3 # FPGA framework configuration
7 tristate "FPGA Configuration Framework"
10 kernel. The FPGA framework adds a FPGA manager class and FPGA
95 tristate "FPGA Bridge Framework"
163 under Device Feature List (DFL) framework. Select this option to
205 management and virtualization with DFL framework and DFL feature
|
| /linux-5.10/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-5.10/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-5.10/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-5.10/arch/sh/kernel/cpu/ |
| D | clock.c | 3 * arch/sh/kernel/cpu/clock.c - SuperH clock framework
7 * This clock framework is derived from the OMAP version by:
12 * Modified for omap shared clock framework by Tony Lindgren <tony@atomide.com>
|
| /linux-5.10/drivers/dma-buf/ |
| D | Kconfig | 5 bool "Explicit Synchronization Framework"
9 The Sync File Framework adds explicit synchronization via
21 bool "Sync File Validation Framework"
|
12345678910>>...49