Home
last modified time | relevance | path

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

12345678910>>...12

/linux-6.14.4/rust/kernel/
Dfirmware.rs3 //! Firmware abstraction
28 /// Abstraction around a C `struct firmware`.
30 /// This is a simple abstraction around the C firmware API. Just like with the C API, firmware can
31 /// be requested. Once requested the abstraction provides direct access to the firmware buffer as
Ddevres.rs3 //! Devres abstraction
5 //! [`Devres`] represents an abstraction for the kernel devres (device resource management)
30 /// This abstraction is meant to be used by subsystems to containerize [`Device`] bound resources to
/linux-6.14.4/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
371 Plane Abstraction
425 Connector Abstraction
[all …]
/linux-6.14.4/tools/lib/perf/Documentation/
Dlibperf.txt224 struct perf_cpu_map:: Provides a CPU list abstraction.
226 struct perf_thread_map:: Provides a thread list abstraction.
228 struct perf_evsel:: Provides an abstraction for single a perf event.
232 struct perf_mmap:: Provides an abstraction for accessing perf ring buffer.
/linux-6.14.4/drivers/media/test-drivers/vidtv/
Dvidtv_channel.h7 * This file contains the code for a 'channel' abstraction.
32 * struct vidtv_channel - A 'channel' abstraction
/linux-6.14.4/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.
/linux-6.14.4/drivers/media/platform/mediatek/jpeg/
Dmtk_jpeg_core.h138 * struct mtk_jpegenc_comp_dev - JPEG COREX abstraction
165 * struct mtk_jpegdec_comp_dev - JPEG COREX abstraction
192 * struct mtk_jpeg_dev - JPEG IP abstraction
/linux-6.14.4/Documentation/process/
D4.Coding.rst74 Abstraction layers
78 abstraction layers in the name of flexibility and information hiding.
79 Certainly the kernel makes extensive use of abstraction; no project
81 But experience has shown that excessive or premature abstraction can be
82 just as harmful as premature optimization. Abstraction should be used to
96 Abstraction layers which hide access to hardware - often to allow the bulk
/linux-6.14.4/drivers/mtd/devices/
Dpowernv_flash.c3 * OPAL PNOR flash MTD abstraction
26 * This driver creates the a Linux MTD abstraction for platform PNOR flash
298 MODULE_DESCRIPTION("MTD abstraction for OPAL flash");
/linux-6.14.4/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()
/linux-6.14.4/Documentation/gpu/amdgpu/display/
Dprogramming-model-dcn.rst92 is a low-level abstraction for the connector. One interesting aspect of the
101 wrong impression that this abstraction only deals with physical connections
116 think about it as an abstraction similar to `drm_plane` that represents the
/linux-6.14.4/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:
/linux-6.14.4/arch/powerpc/include/asm/
Dspu_priv1.h3 * Defines an spu hypervisor abstraction layer.
164 /* spu management abstraction */
/linux-6.14.4/include/linux/
Dclocksource.h36 * struct clocksource - hardware abstraction for a free running counter
76 * @base: Hardware abstraction for clock on which a clocksource
317 * struct clocksource_base - hardware abstraction for clock on which a clocksource
/linux-6.14.4/drivers/net/can/ifi_canfd/
DKconfig7 connected to the "platform bus" (Linux abstraction for directly
/linux-6.14.4/arch/powerpc/platforms/cell/
Dspu_priv1_mmio.h3 * spu hypervisor abstraction for direct hardware access.
/linux-6.14.4/drivers/net/can/cc770/
DKconfig20 connected to the "platform bus" (Linux abstraction for directly
/linux-6.14.4/drivers/gpio/
Dgpio-spear-spics.c3 * SPEAr platform SPI chipselect abstraction over gpiolib
40 * @chip: gpio_chip abstraction
/linux-6.14.4/drivers/usb/musb/
Dmusb_dma.h3 * MUSB OTG driver DMA controller abstraction
16 * DMA Controller Abstraction
/linux-6.14.4/Documentation/ABI/removed/
Draw13948 of abstraction that required userspace clients to duplicate much
/linux-6.14.4/Documentation/core-api/irq/
Dirq-domain.rst111 accepts a more general abstraction 'struct fwnode_handle'.
135 accepts a more general abstraction 'struct fwnode_handle'.
213 accepts a more general abstraction 'struct fwnode_handle'.
/linux-6.14.4/drivers/net/can/c_can/
DKconfig12 to the "platform bus" (Linux abstraction for directly to the
/linux-6.14.4/drivers/pps/generators/
DKconfig32 parport abstraction layer and hrtimers to precisely control the signal.
/linux-6.14.4/Documentation/trace/rv/
Dda_monitor_synthesis.rst15 the *RV monitor* abstraction. The RV monitor includes a set of instances
42 The synthesis of automata-based models into the Linux *RV monitor* abstraction
/linux-6.14.4/Documentation/driver-api/
Dmen-chameleon-bus.rst74 A carrier device is just an abstraction for the real world physical bus the
77 device). To provide abstraction from the real hardware bus, an MCB carrier

12345678910>>...12