| /linux/tools/lib/perf/Documentation/ |
| H A D | libperf.txt | 227 struct perf_cpu_map:: Provides a CPU list abstraction.
229 struct perf_thread_map:: Provides a thread list abstraction.
231 struct perf_evsel:: Provides an abstraction for single a perf event.
235 struct perf_mmap:: Provides an abstraction for accessing perf ring buffer.
|
| /linux/drivers/media/test-drivers/vidtv/ |
| H A D | vidtv_channel.h | 7 * This file contains the code for a 'channel' abstraction.
32 * struct vidtv_channel - A 'channel' abstraction
|
| /linux/Documentation/i2c/ |
| H A D | i2c-sysfs.rst | 84 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/arch/x86/kernel/cpu/resctrl/ |
| H A D | internal.h | 61 * Members of this structure are accessed via helpers that provide abstraction.
76 * Members of this structure are accessed via helpers that provide abstraction.
132 * e.g. mbm_width, or accessed via helpers that provide abstraction. e.g.
|
| /linux/include/net/libeth/ |
| H A D | xsk.h | 105 * @sq: XDPSQ abstraction for the queue
181 * @sq: XDPSQ abstraction for the queue
218 * @sq: XDPSQ abstraction for the queue
237 * @sq: XDPSQ abstraction for the queue
382 * Internal inline abstraction to run XDP program on XSk Rx path. Handles
434 * Inline abstraction, XSk's counterpart of __libeth_xdp_run_pass(), see its
|
| H A D | xdp.h | 406 * struct libeth_xdpsq - abstraction for an XDPSQ
416 * Abstraction for driver-independent implementation of Tx. Placed on the stack
434 * struct libeth_xdp_tx_desc - abstraction for an XDP Tx descriptor
504 * Internal abstraction for placing @n XDP Tx frames on the HW XDPSQ. Used for
707 * @sq: XDPSQ abstraction for the queue
765 * Internal abstraction to create bulk flush functions for drivers. Used for
980 * @sq: XDPSQ abstraction for the queue
1348 * Internal inline abstraction to run XDP program. Handles ``XDP_DROP``
1396 * Internal inline abstraction to run XDP program and additionally handle
1455 * Inline abstraction that does the following (non-XSk path):
|
| /linux/Documentation/process/ |
| H A D | 4.Coding.rst | 74 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/rust/kernel/ |
| H A D | firmware.rs | 3 //! Firmware abstraction
39 /// Abstraction around a C `struct firmware`.
41 /// This is a simple abstraction around the C firmware API. Just like with the C API, firmware can
42 /// be requested. Once requested the abstraction provides direct access to the firmware buffer as
|
| H A D | device.rs | 26 /// This structure represents the Rust abstraction for a C `struct device`. A [`Device`] can either
170 /// Creates a new reference-counted abstraction instance of an existing `struct device` pointer.
479 /// which provides access to internal bus abstraction methods on [`Device`] that are not available
514 /// abstraction.
518 /// abstraction.
527 /// abstraction.
531 /// abstraction.
533 /// This context exists for cases where the bus abstraction needs access to internal device
547 /// Any abstraction that can guarantee a scope where the corresponding bus device is bound, should
575 /// require internal bus abstraction access to a bound device to be generic over both contexts.
|
| /linux/drivers/mtd/devices/ |
| H A D | powernv_flash.c | 3 * 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/Documentation/core-api/ |
| H A D | genericirq.rst | 14 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/drivers/gpio/ |
| H A D | gpio-spear-spics.c | 3 * SPEAr platform SPI chipselect abstraction over gpiolib
40 * @chip: gpio_chip abstraction
|
| /linux/drivers/usb/musb/ |
| H A D | musb_dma.h | 3 * MUSB OTG driver DMA controller abstraction
16 * DMA Controller Abstraction
|
| /linux/drivers/net/can/ifi_canfd/ |
| H A D | Kconfig | 7 connected to the "platform bus" (Linux abstraction for directly
|
| /linux/drivers/net/can/cc770/ |
| H A D | Kconfig | 20 connected to the "platform bus" (Linux abstraction for directly
|
| /linux/Documentation/driver-api/ |
| H A D | men-chameleon-bus.rst | 74 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/Documentation/ABI/removed/ |
| H A D | raw1394 | 8 of abstraction that required userspace clients to duplicate much
|
| /linux/drivers/net/can/c_can/ |
| H A D | Kconfig | 12 to the "platform bus" (Linux abstraction for directly to the
|
| /linux/drivers/net/wireless/st/cw1200/ |
| H A D | hwbus.h | 3 * Common hwbus abstraction layer interface for cw1200 wireless driver
|
| /linux/drivers/rtc/ |
| H A D | rtc-generic.c | 2 /* rtc-generic: RTC driver using the generic RTC abstraction
|
| /linux/drivers/net/wireless/silabs/wfx/ |
| H A D | bus.h | 3 * Common bus abstraction layer.
|
| /linux/Documentation/userspace-api/media/mediactl/ |
| H A D | media-controller-intro.rst | 27 Kernel abstraction APIs such as V4L2 and ALSA provide means for
|
| /linux/lib/crypto/mpi/ |
| H A D | generic_mpih-mul3.c | 9 * way the data is stored; this is to support the abstraction
|
| H A D | generic_mpih-mul2.c | 9 * way the data is stored; this is to support the abstraction
|
| H A D | generic_mpih-mul1.c | 9 * way the data is stored; this is to support the abstraction
|