Searched full:framework (Results 1 – 25 of 2300) sorted by relevance
12345678910>>...92
| /kernel/linux/linux-4.19/drivers/pwm/ |
| D | Kconfig | 13 This framework provides a generic interface to PWM devices
17 drivers can request PWM devices and use the generic framework
20 This generic framework replaces the legacy PWM framework which
22 all legacy implementations have been ported to the framework
23 yet. The framework provides an API that is backward compatible
24 with the legacy framework so that existing client drivers
39 Generic PWM framework driver for Analog Baseband AB8500.
48 Generic PWM framework driver for Atmel SoC.
58 Generic PWM framework driver for the PWM output of the HLCDC
69 Generic PWM framework driver for Atmel Timer Counter Block.
[all …]
|
| /kernel/linux/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 …]
|
| /kernel/linux/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 …]
|
| /kernel/linux/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 …]
|
| /kernel/linux/linux-4.19/Documentation/media/kapi/ |
| D | v4l2-intro.rst | 15 For a long time the framework was limited to the video_device struct for
17 (note that this document does not discuss the video_buf framework).
24 the lack of a framework.
26 So this framework sets up the basic building blocks that all drivers
27 need and this same framework should make it much easier to refactor
33 framework. It can be used as a template for real PCI video capture driver.
64 Structure of the V4L2 framework
67 The framework closely resembles the driver structure: it has a v4l2_device
72 The V4L2 framework also optionally integrates with the media framework. If a
74 will automatically appear in the media framework as entities.
|
| D | cec-core.rst | 4 The CEC framework provides a unified kernel interface for use with HDMI CEC
6 transmitters, USB dongles). The framework also gives the option to decide
9 feature into the kernel's remote control framework.
22 The CEC framework described here is up to date with the CEC 2.0 specification.
46 adapter operations which are called by the CEC framework and that you
215 driven) by calling into the framework in the following situations:
257 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
386 -ENOMSG, otherwise the CEC framework assumes it processed this message and
[all …]
|
| /kernel/linux/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 …]
|
| /kernel/linux/linux-4.19/drivers/clk/bcm/ |
| D | Kconfig | 7 Enable common clock framework support for Broadcom BCM63xx DSL SoCs
15 Enable common clock framework support for Broadcom SoCs
22 Enable common clock framework support for Broadcom SoCs
31 Enable common clock framework support for the Broadcom Cygnus SoC
39 Enable common clock framework support for the Broadcom Hurricane 2
48 Enable common clock framework support for the Broadcom Northstar and
57 Enable common clock framework support for the Broadcom Northstar 2 SoC
65 Enable common clock framework support for the Broadcom Stingray SoC
|
| /kernel/linux/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 …]
|
| /kernel/linux/linux-4.19/Documentation/power/ |
| D | opp.txt | 46 CONFIG_PM as certain SoCs such as Texas Instrument's OMAP framework allows to
51 SoC framework -> modifies on required cases certain OPPs -> OPP layer
55 framework registers a set of initial OPPs per device with the OPP layer. This
57 This initial list contains a set of OPPs that the framework expects to be safely
62 As the system proceeds to operate, SoC framework may choose to make certain
65 SoC framework might choose to disable a higher frequency OPP to safely continue
79 specific framework which uses the OPP library. Similar care needs to be taken
85 device. It is expected that the SoC framework will register the OPP entries
88 operation. The SoC framework can subsequently control the availability of the
96 used by SoC framework to define a optimal list as per the demands of
[all …]
|
| /kernel/linux/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 */
|
| /kernel/linux/linux-4.19/Documentation/mtd/ |
| D | spi-nor.txt | 1 SPI NOR framework
4 Part I - Why do we need this framework?
19 Part II - How does the framework work?
22 This framework just adds a new layer between the MTD and the SPI bus driver.
26 Before this framework, the layer is like:
36 After this framework, the layer is like:
39 SPI NOR framework
50 SPI NOR framework
56 Part III - How can drivers use the framework?
|
| /kernel/linux/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?
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/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
|
| /kernel/linux/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
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-4.19/Documentation/ |
| D | lsm.txt | 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 is a joint development effort by several security
41 Linux kernel patch that implements this framework. The patch is
44 of the framework and the example capabilities security module provided
47 LSM Framework
50 The LSM kernel patch provides a general kernel framework to support
51 security modules. In particular, the LSM framework is primarily focused
54 framework does not provide any additional security; it merely provides
[all …]
|
| /kernel/linux/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.
|
| /kernel/linux/linux-4.19/Documentation/watchdog/ |
| D | convert_drivers_to_kernel_api.txt | 1 Converting old watchdog drivers to the watchdog framework
5 Before the watchdog framework came into the kernel, every driver had to
6 implement the API on its own. Now, as the framework factored out the common
7 components, those drivers can be lightened making it a user of the framework.
16 etc... These are now handled by the framework and just call the driver when
29 - write: Can simply go, all defined behaviour is taken care of by the framework,
33 the most common ones are handled by the framework, supported by some assistance
69 -ENOIOCTLCMD, the IOCTLs of the framework will be tried, too. Any other error
91 miscdevice'. The framework will create it on watchdog_dev_register() called by
154 necessary information for the framework. The struct is also explained in detail
|
| /kernel/linux/linux-4.19/drivers/remoteproc/ |
| D | Kconfig | 21 on iMX7D) via the remote processor framework.
33 and DSP on OMAP4) via the remote processor framework.
39 offloaded to remote DSP processors using this framework).
62 remote processor framework.
66 offloaded to remote DSP processors using this framework).
82 via the remote processor framework.
178 processor framework.
|
| /kernel/liteos_a/bsd/dev/usb/ |
| D | BUILD.gn | 130 "//drivers/framework/model/input/driver",
131 "//drivers/framework/include/core",
132 "//drivers/framework/core/common/include/host",
133 "//drivers/framework/utils",
134 "//drivers/framework/osal",
135 "//drivers/framework/ability/sbuf/include",
136 "//drivers/framework/include/osal",
|
| /kernel/linux/patches/linux-5.10/rk3568_patch/ |
| D | hdf.patch | 62 +ccflags-$(CONFIG_DRIVERS_HDF_INPUT) += $(HDF_ROOT_DIR)/framework/model/input/driver \
63 + $(HDF_ROOT_DIR)/framework/include/core \
64 + $(HDF_ROOT_DIR)/framework/core/common/include/host \
65 + $(HDF_ROOT_DIR)/framework/include/utils \
66 + $(HDF_ROOT_DIR)/framework/include/osal \
67 + $(HDF_ROOT_DIR)/framework/ability/sbuf/include \
310 +ccflags-y +=-Idrivers/hdf/framework/model/input/driver \
311 + -Idrivers/hdf/framework/model/input/driver/input_bus_ops \
312 + -Idrivers/hdf/framework/include/core \
313 + -Idrivers/hdf/framework/core/common/include/host \
[all …]
|
12345678910>>...92