Searched full:concrete (Results 1 – 25 of 28) sorted by relevance
12
/linux-5.10/fs/notify/fanotify/ |
D | fanotify.h | 127 * Common structure for fanotify events. Concrete structs are allocated in 130 * be freed and which concrete struct it may be cast to.
|
/linux-5.10/arch/riscv/include/asm/ |
D | barrier.h | 65 * any concrete reason we need a full IO fence, it seems safer to just upgrade
|
/linux-5.10/Documentation/driver-api/ |
D | io_ordering.rst | 15 A more concrete example from a hypothetical device driver::
|
/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/ |
D | sifive,plic-1.0.0.yaml | 33 "sifive,plic-1.0.0" device is a concrete implementation of the PLIC that
|
/linux-5.10/drivers/tty/ |
D | tty_port.c | 105 * a concrete tty specified by @index. Use this or tty_port_install (or both). 126 * linked to a concrete tty specified by @index. Use this or tty_port_install 651 * to a concrete tty specified by @tty. Use this or tty_port_register_device
|
/linux-5.10/drivers/media/test-drivers/vidtv/ |
D | vidtv_encoder.h | 100 * @id: So we can cast to a concrete implementation when needed.
|
/linux-5.10/drivers/gpu/drm/amd/amdkfd/ |
D | kfd_mqd_manager.h | 36 * @load_mqd: Loads the mqd to a concrete hqd slot. Used only for no cp
|
D | kfd_device_queue_manager.h | 167 * concrete device. This class is the only class in the queues scheduler
|
D | kfd_mqd_manager_cik.c | 301 * HIQ MQD Implementation, concrete implementation for HIQ MQD implementation.
|
/linux-5.10/drivers/net/ethernet/qlogic/qed/ |
D | qed_hw.h | 234 * @brief qed_vfid_to_concrete - build a concrete FID for a
|
D | qed.h | 888 * the concrete value.
|
D | qed_sriov.c | 429 u32 concrete; in qed_iov_setup_vfdb() local 447 concrete = qed_vfid_to_concrete(p_hwfn, vf->abs_vf_id); in qed_iov_setup_vfdb() 448 vf->concrete_fid = concrete; in qed_iov_setup_vfdb()
|
/linux-5.10/drivers/staging/fbtft/ |
D | fb_st7789v.c | 78 * Nonetheless, this sequence can be used as a template for concrete
|
/linux-5.10/Documentation/filesystems/ |
D | journalling.rst | 176 The journalling layer uses typedefs to 'hide' the concrete definitions
|
/linux-5.10/drivers/net/ethernet/mellanox/mlx5/core/ |
D | en_stats.h | 111 /* Concrete NIC Stats */
|
D | en_stats.c | 100 /* Concrete NIC Stats */
|
/linux-5.10/include/linux/qed/ |
D | common_hsi.h | 1075 /* Concrete Function ID */ 1090 /* Concrete Function ID */
|
/linux-5.10/drivers/i2c/busses/ |
D | i2c-iop3xx.c | 188 * Concrete compare_funcs
|
/linux-5.10/Documentation/fb/ |
D | framebuffer.rst | 100 thus doesn't need to know, for example, how the color registers of the concrete
|
/linux-5.10/drivers/pinctrl/aspeed/ |
D | pinmux-aspeed.h | 197 * As a concrete example: 255 * Here's a complete, concrete "pre-processed" example of the table structures
|
/linux-5.10/fs/nilfs2/ |
D | ioctl.c | 31 * @dofunc: concrete function of get/set metadata info 1148 * @dofunc: concrete function of getting metadata info
|
/linux-5.10/include/linux/ |
D | printk.h | 99 * should be able to fix this issue or at least get a concrete idea of the
|
D | jbd2.h | 461 * struct jbd2_journal_handle - The jbd2_journal_handle type is the concrete 764 * struct journal_s - The journal_s type is the concrete type associated with
|
/linux-5.10/tools/lib/bpf/ |
D | btf.c | 3745 * compatible structurally, one of which has FWD field, while other is concrete 3774 * - Both types in canonical and candidate graphs are concrete STRUCT/UNION, 3776 * - Type in canonical graph is FWD, while type in candidate is concrete 3785 * - Type in canonical graph is concrete STRUCT/UNION, while type in candidate 3789 * a concrete STRUCT/UNION from canonical graph. If the rest of type graphs 3790 * turn out equivalent, we'll re-resolve FWD to concrete STRUCT/UNION from
|
/linux-5.10/drivers/usb/dwc2/ |
D | core.h | 1038 * @fifo_map: Each bit intend for concrete fifo. If that bit is set,
|
12