Home
last modified time | relevance | path

Searched full:lay (Results 1 – 25 of 37) sorted by relevance

12

/Linux-v5.15/drivers/net/ethernet/mellanox/mlx5/core/
Dcmd.c219 ent->lay->sig = ~xor8_buf(ent->lay, 0, sizeof(*ent->lay)); in set_signature()
232 own = READ_ONCE(ent->lay->status_own); in poll_timeout()
251 sig = xor8_buf(ent->lay, 0, sizeof(*ent->lay)); in verify_signature()
797 u16 op = MLX5_GET(mbox_in, ent->lay->in, opcode); in dump_command()
820 dump_buf(ent->lay->in, sizeof(ent->lay->in), 1, offset, ent->idx); in dump_command()
821 offset += sizeof(ent->lay->in); in dump_command()
823 dump_buf(ent->lay->out, sizeof(ent->lay->out), 1, offset, ent->idx); in dump_command()
824 offset += sizeof(ent->lay->out); in dump_command()
827 dump_buf(ent->lay, sizeof(*ent->lay), 0, offset, ent->idx); in dump_command()
828 offset += sizeof(*ent->lay); in dump_command()
[all …]
Dpagealloc.c631 struct mlx5_cmd_layout *lay; in optimal_reclaimed_pages() local
634 ret = (sizeof(lay->out) + MLX5_BLKS_FOR_RECLAIM_PAGES * sizeof(block->data) - in optimal_reclaimed_pages()
/Linux-v5.15/drivers/media/v4l2-core/
Dv4l2-ctrls-defs.c893 case V4L2_CID_MPEG_VIDEO_H264_HIER_CODING_L0_BR: return "H264 Hierarchical Lay 0 Bitrate"; in v4l2_ctrl_get_name()
894 case V4L2_CID_MPEG_VIDEO_H264_HIER_CODING_L1_BR: return "H264 Hierarchical Lay 1 Bitrate"; in v4l2_ctrl_get_name()
895 case V4L2_CID_MPEG_VIDEO_H264_HIER_CODING_L2_BR: return "H264 Hierarchical Lay 2 Bitrate"; in v4l2_ctrl_get_name()
896 case V4L2_CID_MPEG_VIDEO_H264_HIER_CODING_L3_BR: return "H264 Hierarchical Lay 3 Bitrate"; in v4l2_ctrl_get_name()
897 case V4L2_CID_MPEG_VIDEO_H264_HIER_CODING_L4_BR: return "H264 Hierarchical Lay 4 Bitrate"; in v4l2_ctrl_get_name()
898 case V4L2_CID_MPEG_VIDEO_H264_HIER_CODING_L5_BR: return "H264 Hierarchical Lay 5 Bitrate"; in v4l2_ctrl_get_name()
899 case V4L2_CID_MPEG_VIDEO_H264_HIER_CODING_L6_BR: return "H264 Hierarchical Lay 6 Bitrate"; in v4l2_ctrl_get_name()
977 case V4L2_CID_MPEG_VIDEO_HEVC_HIER_CODING_L0_BR: return "HEVC Hierarchical Lay 0 BitRate"; in v4l2_ctrl_get_name()
978 case V4L2_CID_MPEG_VIDEO_HEVC_HIER_CODING_L1_BR: return "HEVC Hierarchical Lay 1 BitRate"; in v4l2_ctrl_get_name()
979 case V4L2_CID_MPEG_VIDEO_HEVC_HIER_CODING_L2_BR: return "HEVC Hierarchical Lay 2 BitRate"; in v4l2_ctrl_get_name()
[all …]
/Linux-v5.15/fs/xfs/libxfs/
Dxfs_log_format.h260 * This is the structure used to lay out an inode log item in the
472 * This is the structure used to lay out a buf log item in the log. The data
574 * This is the structure used to lay out an efi log item in the
603 * This is the structure used to lay out an efd log item in the
663 * This is the structure used to lay out an rui log item in the
684 * This is the structure used to lay out an rud log item in the
711 * This is the structure used to lay out a cui log item in the
732 * This is the structure used to lay out a cud log item in the
759 * This is the structure used to lay out an bui log item in the
780 * This is the structure used to lay out an bud log item in the
/Linux-v5.15/Documentation/userspace-api/media/v4l/
Dvidioc-g-selection.rst77 rectangle. The original rectangle must lay inside the adjusted one.
80 rectangle. The adjusted rectangle must lay inside the original one.
/Linux-v5.15/include/uapi/linux/
Dcm4000_cs.h27 * will lay out the structure members differently than the 64bit kernel.
/Linux-v5.15/scripts/
Dcheckstack.pl99 # 100092: e3 f0 ff c8 ff 71 lay %r15,-56(%r15)
100 $re = qr/.*(?:lay|ag?hi).*\%r15,-(([0-9]{2}|[3-9])[0-9]{2})
/Linux-v5.15/Documentation/filesystems/ext4/
Dgroup_descr.rst17 property to group several block groups into a flex group and lay out all
/Linux-v5.15/include/linux/
Dmemory.h76 * lay at the beginning of the memory block.
/Linux-v5.15/Documentation/devicetree/bindings/mtd/
Dbrcm,brcmnand.yaml129 determines how the hardware BCH engine will lay
/Linux-v5.15/Documentation/core-api/
Dpacking.rst45 logically. The question is: where do we lay this bit out in memory?
/Linux-v5.15/arch/parisc/kernel/
Dprocess.c92 /* Wait for RESET to lay us to rest. */ in machine_restart()
/Linux-v5.15/drivers/gpu/drm/amd/display/dc/clk_mgr/dce100/
Ddce_clk_mgr.c176 /* do not check under lay */ in dce_get_max_pixel_clock_for_all_paths()
/Linux-v5.15/lib/zstd/
Dfse_decompress.c106 /* Init, lay down lowprob symbols */ in FSE_buildDTable_wksp()
/Linux-v5.15/arch/s390/tools/
Dopcodes.txt799 e371 lay RXY_RRRD
/Linux-v5.15/drivers/gpu/drm/i915/gt/
Dintel_migrate.c66 * We lay the ppGTT out as: in migrate_vm()
/Linux-v5.15/Documentation/devicetree/
Dusage-model.rst258 About now is a good time to lay out an example. Here is part of the
/Linux-v5.15/Documentation/driver-api/
Dxillybus.rst304 to lay around in the DMA buffers between read() and write() anyhow.
/Linux-v5.15/include/rdma/
Dib_mad.h166 * lay them out wrong otherwise. (And unfortunately they are sent on
/Linux-v5.15/Documentation/process/
D2.Process.rst493 you can lay your hands on". Usually the way to do this is to work
/Linux-v5.15/arch/mips/kernel/
Dvpe.c178 /* Lay out the SHF_ALLOC sections in a way not dissimilar to how ld
/Linux-v5.15/drivers/infiniband/hw/hfi1/
Dqp.c916 * state. It is generally called to force upper lay apps to abandon stale qps
/Linux-v5.15/include/linux/mlx5/
Ddriver.h827 struct mlx5_cmd_layout *lay; member
/Linux-v5.15/Documentation/scsi/
DChangeLog.sym53c8xx460 - Revamp slightly the Symbios NVRAM lay-out based on the excerpt of
/Linux-v5.15/drivers/gpu/drm/amd/display/dc/dce/
Ddce_clk_mgr.c195 /* do not check under lay */ in get_max_pixel_clock_for_all_paths()

12