Home
last modified time | relevance | path

Searched full:abstraction (Results 1 – 25 of 543) sorted by relevance

12345678910>>...22

/kernel/linux/linux-5.10/Documentation/gpu/
Ddrm-kms.rst59 see `Frame Buffer Abstraction`_) feed into planes. Planes are represented by
60 :c:type:`struct drm_plane <drm_plane>`, see `Plane Abstraction`_ for more
62 (represented by :c:type:`struct drm_crtc <drm_crtc>`, see `CRTC Abstraction`_)
67 :c:type:`struct drm_encoder <drm_encoder>`, see `Encoder Abstraction`_). Those
80 Abstraction`_). Connectors can have different possible encoders, but the kernel
162 Modeset Base Object Abstraction
307 CRTC Abstraction
322 Frame Buffer Abstraction
358 Plane Abstraction
382 Connector Abstraction
[all …]
/kernel/linux/linux-6.6/Documentation/gpu/
Ddrm-kms.rst59 see `Frame Buffer Abstraction`_) feed into planes. Planes are represented by
60 :c:type:`struct drm_plane <drm_plane>`, see `Plane Abstraction`_ for more
62 (represented by :c:type:`struct drm_crtc <drm_crtc>`, see `CRTC Abstraction`_)
67 :c:type:`struct drm_encoder <drm_encoder>`, see `Encoder Abstraction`_). Those
80 Abstraction`_). Connectors can have different possible encoders, but the kernel
164 Modeset Base Object Abstraction
309 CRTC Abstraction
333 Frame Buffer Abstraction
369 Plane Abstraction
408 Connector Abstraction
[all …]
/kernel/linux/linux-6.6/tools/lib/perf/Documentation/
Dlibperf.txt225 struct perf_cpu_map:: Provides a CPU list abstraction.
227 struct perf_thread_map:: Provides a thread list abstraction.
229 struct perf_evsel:: Provides an abstraction for single a perf event.
233 struct perf_mmap:: Provides an abstraction for accessing perf ring buffer.
/kernel/linux/linux-5.10/tools/lib/perf/Documentation/
Dlibperf.txt220 struct perf_cpu_map:: Provides a CPU list abstraction.
222 struct perf_thread_map:: Provides a thread list abstraction.
224 struct perf_evsel:: Provides an abstraction for single a perf event.
228 struct perf_mmap:: Provides an abstraction for accessing perf ring buffer.
/kernel/linux/linux-5.10/tools/arch/ia64/include/asm/
Dbarrier.h6 * in the Processor Abstraction Layer and the System Abstraction Layer
/kernel/linux/linux-6.6/tools/arch/ia64/include/asm/
Dbarrier.h6 * in the Processor Abstraction Layer and the System Abstraction Layer
/kernel/linux/linux-6.6/drivers/media/test-drivers/vidtv/
Dvidtv_channel.h7 * This file contains the code for a 'channel' abstraction.
32 * struct vidtv_channel - A 'channel' abstraction
/kernel/linux/linux-5.10/drivers/media/test-drivers/vidtv/
Dvidtv_channel.h7 * This file contains the code for a 'channel' abstraction.
32 * struct vidtv_channel - A 'channel' abstraction
/kernel/linux/linux-5.10/arch/ia64/include/asm/
Dbarrier.h4 * in the Processor Abstraction Layer and the System Abstraction Layer
Dswitch_to.h4 * the Processor Abstraction Layer and the System Abstraction Layer
/kernel/linux/linux-6.6/arch/ia64/include/asm/
Dswitch_to.h4 * the Processor Abstraction Layer and the System Abstraction Layer
Dbarrier.h4 * in the Processor Abstraction Layer and the System Abstraction Layer
/kernel/liteos_m/
DREADME.md12abstraction layer, optional components, and project directory. The LiteOS-M kernel is divided into…
56 ├── kal # Kernel abstraction layer
/kernel/linux/linux-5.10/Documentation/driver-api/
Dio-mapping.rst8 The io_mapping functions in linux/io-mapping.h provide an abstraction for
81 mechanisms and so provides only an abstraction layer and no new
/kernel/linux/linux-6.6/Documentation/i2c/
Di2c-sysfs.rst84 Each logical I2C bus may be an abstraction of a physical I2C bus controller, or
85 an abstraction of a channel behind an I2C MUX. In case it is an abstraction of a
88 abstraction.
93 If the logical I2C bus is a direct abstraction of a physical I2C bus controller,
178 abstraction.
/kernel/linux/linux-6.6/drivers/media/platform/mediatek/jpeg/
Dmtk_jpeg_core.h138 * struct mtk_jpegenc_comp_dev - JPEG COREX abstraction
166 * struct mtk_jpegdec_comp_dev - JPEG COREX abstraction
193 * struct mtk_jpeg_dev - JPEG IP abstraction
/kernel/linux/linux-6.6/Documentation/process/
D4.Coding.rst70 Abstraction layers
74 abstraction layers in the name of flexibility and information hiding.
75 Certainly the kernel makes extensive use of abstraction; no project
77 But experience has shown that excessive or premature abstraction can be
78 just as harmful as premature optimization. Abstraction should be used to
92 Abstraction layers which hide access to hardware - often to allow the bulk
/kernel/linux/linux-5.10/Documentation/process/
D4.Coding.rst70 Abstraction layers
74 abstraction layers in the name of flexibility and information hiding.
75 Certainly the kernel makes extensive use of abstraction; no project
77 But experience has shown that excessive or premature abstraction can be
78 just as harmful as premature optimization. Abstraction should be used to
92 Abstraction layers which hide access to hardware - often to allow the bulk
/kernel/linux/linux-5.10/drivers/mtd/devices/
Dpowernv_flash.c3 * OPAL PNOR flash MTD abstraction
26 * This driver creates the a Linux MTD abstraction for platform PNOR flash
292 MODULE_DESCRIPTION("MTD abstraction for OPAL flash");
/kernel/linux/linux-6.6/drivers/mtd/devices/
Dpowernv_flash.c3 * OPAL PNOR flash MTD abstraction
26 * This driver creates the a Linux MTD abstraction for platform PNOR flash
300 MODULE_DESCRIPTION("MTD abstraction for OPAL flash");
/kernel/linux/linux-5.10/arch/mips/dec/prom/
Dinit.c53 * Set up prom abstraction structure with REX entry points. in which_prom()
77 * Set up prom abstraction structure with non-REX entry points. in which_prom()
/kernel/linux/linux-6.6/arch/mips/dec/prom/
Dinit.c53 * Set up prom abstraction structure with REX entry points. in which_prom()
77 * Set up prom abstraction structure with non-REX entry points. in which_prom()
/kernel/linux/linux-5.10/Documentation/core-api/
Dgenericirq.rst14 abstraction of interrupt handling for device drivers. It is able to
64 A more natural abstraction is the clean separation of the 'irq flow' and
97 Abstraction layers
100 There are three main levels of abstraction in the interrupt code:
/kernel/linux/linux-6.6/Documentation/core-api/
Dgenericirq.rst14 abstraction of interrupt handling for device drivers. It is able to
64 A more natural abstraction is the clean separation of the 'irq flow' and
97 Abstraction layers
100 There are three main levels of abstraction in the interrupt code:
/kernel/linux/linux-6.6/drivers/net/can/ifi_canfd/
DKconfig7 connected to the "platform bus" (Linux abstraction for directly

12345678910>>...22