Home
last modified time | relevance | path

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

1234567891011

/Linux-v5.15/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 …]
/Linux-v5.15/tools/lib/perf/Documentation/
Dlibperf.txt223 struct perf_cpu_map:: Provides a CPU list abstraction.
225 struct perf_thread_map:: Provides a thread list abstraction.
227 struct perf_evsel:: Provides an abstraction for single a perf event.
231 struct perf_mmap:: Provides an abstraction for accessing perf ring buffer.
/Linux-v5.15/tools/arch/ia64/include/asm/
Dbarrier.h6 * in the Processor Abstraction Layer and the System Abstraction Layer
/Linux-v5.15/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
/Linux-v5.15/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-v5.15/Documentation/i2c/
Di2c-sysfs.rst85 Each logical I2C bus may be an abstraction of a physical I2C bus controller, or
86 an abstraction of a channel behind an I2C MUX. In case it is an abstraction of a
89 abstraction.
94 If the logical I2C bus is a direct abstraction of a physical I2C bus controller,
181 abstraction.
/Linux-v5.15/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
/Linux-v5.15/drivers/mtd/devices/
Dpowernv_flash.c3 * OPAL PNOR flash MTD abstraction
26 * This driver creates the a Linux MTD abstraction for platform PNOR flash
295 MODULE_DESCRIPTION("MTD abstraction for OPAL flash");
/Linux-v5.15/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-v5.15/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-v5.15/drivers/net/can/ifi_canfd/
DKconfig7 connected to the "platform bus" (Linux abstraction for directly
/Linux-v5.15/arch/powerpc/platforms/cell/
Dspu_priv1_mmio.h3 * spu hypervisor abstraction for direct hardware access.
/Linux-v5.15/arch/powerpc/include/asm/
Dspu_priv1.h3 * Defines an spu hypervisor abstraction layer.
164 /* spu management abstraction */
/Linux-v5.15/drivers/pps/generators/
DKconfig14 parport abstraction layer and hrtimers to precisely control the signal.
/Linux-v5.15/drivers/net/can/cc770/
DKconfig19 connected to the "platform bus" (Linux abstraction for directly
/Linux-v5.15/drivers/net/can/c_can/
DKconfig12 to the "platform bus" (Linux abstraction for directly to the
/Linux-v5.15/drivers/gpio/
Dgpio-spear-spics.c2 * SPEAr platform SPI chipselect abstraction over gpiolib
43 * @chip: gpio_chip abstraction
/Linux-v5.15/Documentation/ABI/removed/
Draw13948 of abstraction that required userspace clients to duplicate much
/Linux-v5.15/Documentation/core-api/irq/
Dirq-domain.rst114 accepts a more general abstraction 'struct fwnode_handle'.
138 accepts a more general abstraction 'struct fwnode_handle'.
216 accepts a more general abstraction 'struct fwnode_handle'.
/Linux-v5.15/drivers/net/wireless/st/cw1200/
Dhwbus.h3 * Common hwbus abstraction layer interface for cw1200 wireless driver
/Linux-v5.15/drivers/usb/musb/
Dmusb_dma.h3 * MUSB OTG driver DMA controller abstraction
16 * DMA Controller Abstraction
/Linux-v5.15/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
/Linux-v5.15/Documentation/networking/
Dphy.rst2 PHY Abstraction Layer
23 accessed are, in fact, busses, the PHY Abstraction Layer treats them as such.
169 Letting the PHY Abstraction Layer do Everything
407 With the PHY Abstraction Layer, adding support for new PHYs is
416 support, and let the PHY Abstraction Layer's Generic PHY Driver
/Linux-v5.15/drivers/rtc/
Drtc-generic.c2 /* rtc-generic: RTC driver using the generic RTC abstraction

1234567891011