| /OK3568_Linux_fs/kernel/drivers/net/ethernet/mellanox/mlx5/core/ |
| H A D | cmd.c | 224 ent->lay->sig = ~xor8_buf(ent->lay, 0, sizeof(*ent->lay)); in set_signature()
237 own = READ_ONCE(ent->lay->status_own); in poll_timeout()
256 sig = xor8_buf(ent->lay, 0, sizeof(*ent->lay)); in verify_signature()
794 u16 op = MLX5_GET(mbox_in, ent->lay->in, opcode); in dump_command()
816 dump_buf(ent->lay->in, sizeof(ent->lay->in), 1, offset); in dump_command()
817 offset += sizeof(ent->lay->in); in dump_command()
819 dump_buf(ent->lay->out, sizeof(ent->lay->out), 1, offset); in dump_command()
820 offset += sizeof(ent->lay->out); in dump_command()
823 dump_buf(ent->lay, sizeof(*ent->lay), 0, offset); in dump_command()
824 offset += sizeof(*ent->lay); in dump_command()
[all …]
|
| H A D | pagealloc.c | 631 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()
|
| /OK3568_Linux_fs/kernel/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-g-selection.rst | 77 rectangle. The original rectangle must lay inside the adjusted one.
80 rectangle. The adjusted rectangle must lay inside the original one.
|
| /OK3568_Linux_fs/kernel/Documentation/core-api/ |
| H A D | packing.rst | 45 logically. The question is: where do we lay this bit out in memory?
|
| /OK3568_Linux_fs/kernel/Documentation/filesystems/ext4/ |
| H A D | group_descr.rst | 17 property to group several block groups into a flex group and lay out all
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/mtd/ |
| H A D | brcm,brcmnand.txt | 116 determines how the hardware BCH engine will lay
|
| /OK3568_Linux_fs/kernel/include/linux/mlx5/ |
| H A D | driver.h | 762 struct mlx5_cmd_layout *lay; member
|
| /OK3568_Linux_fs/yocto/poky/bitbake/ |
| H A D | ChangeLog | 309 The 1.2.1 release is meant as a intermediate release to lay the
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/ |
| H A D | xillybus.rst | 304 to lay around in the DMA buffers between read() and write() anyhow.
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/ |
| H A D | usage-model.rst | 258 About now is a good time to lay out an example. Here is part of the
|
| /OK3568_Linux_fs/kernel/arch/s390/tools/ |
| H A D | opcodes.txt | 795 e371 lay RXY_RRRD
|
| /OK3568_Linux_fs/kernel/Documentation/process/ |
| H A D | 2.Process.rst | 493 you can lay your hands on". Usually the way to do this is to work
|
| /OK3568_Linux_fs/kernel/Documentation/scsi/ |
| H A D | ChangeLog.sym53c8xx | 460 - Revamp slightly the Symbios NVRAM lay-out based on the excerpt of
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/lib/gcc/aarch64-none-linux-gnu/10.3.1/plugin/include/ |
| H A D | tree.def | 250 layout_type does not know how to lay this out,
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/lib/gcc/arm-none-linux-gnueabihf/10.3.1/plugin/include/ |
| H A D | tree.def | 250 layout_type does not know how to lay this out,
|
| /OK3568_Linux_fs/buildroot/dl/sox/git/ |
| H A D | Doxyfile | 1759 # that lay further from the root node will be omitted. Note that setting this
|
| /OK3568_Linux_fs/external/mpp/tools/ |
| H A D | mpp_doxyfile | 2259 # root by following a path via at most 3 edges will be shown. Nodes that lay
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/ |
| H A D | cgroup-v2.rst | 2528 to lay programs.
|
| /OK3568_Linux_fs/external/xserver/hw/dmx/doxygen/ |
| H A D | doxygen.conf.in | 2356 # root by following a path via at most 3 edges will be shown. Nodes that lay
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/info/ |
| H A D | ld.info | 3943 operation. You use output sections to tell the linker how to lay out
|
| /OK3568_Linux_fs/buildroot/dl/unixbench/git/UnixBench/testdir/ |
| H A D | large.txt | 9027 read(4, "e) If rotation is not 0, the lay"..., 4000) = 4000
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/info/ |
| H A D | ld.info | 3943 operation. You use output sections to tell the linker how to lay out
|
| /OK3568_Linux_fs/external/xserver/ |
| H A D | ChangeLog | 11514 to lay on the same surface than the stylus while proximity_out
14534 Assume coordinates always lay inside the root window for this case,
|
| /OK3568_Linux_fs/device/rockchip/common/images/userdata/userdata_normal/media/ |
| H A D | yuv420_p352x288.yuv | 1354 …^[XRJD;1.-,/0///-.-+,--./../.0100/0//.+,0+"&' %(3?& _oM]SCHUhS?F[dQR5K��~�lay|������������������…
1929 …nbc������������������������ncv�����xcTw������������������u[���}A@���������~lay�����������������^9=…
|