Home
last modified time | relevance | path

Searched refs:stashing (Results 1 – 13 of 13) sorted by relevance

/kernel/linux/linux-5.10/drivers/soc/fsl/qbman/
DKconfig60 bool "QMan 'hot potato' data-stashing self-test"
66 DQRR, data and context stashing always on.
/kernel/linux/linux-5.10/include/soc/fsl/
Dqman.h375 struct qm_fqd_stashing stashing; member
461 struct qm_fqd_stashing *st = &fqd->context_a.stashing; in qm_fqd_set_stashing()
470 return fqd->context_a.stashing.cl; in qm_fqd_get_stashing()
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/
Dfsl-tsec-phy.txt68 - bd-stash : If present, indicates that the hardware supports stashing
/kernel/linux/linux-5.10/fs/hmdfs/
Dhmdfs_client.c260 bool stashing; in hmdfs_remote_write_to_remote() local
267 stashing = (info->stash_status == HMDFS_REMOTE_INODE_STASHING); in hmdfs_remote_write_to_remote()
270 return !stashing; in hmdfs_remote_write_to_remote()
Dstash.c844 LIST_HEAD(stashing); in hmdfs_stash_offline_do_stash()
863 list_add_tail(&info->stash_node, &stashing); in hmdfs_stash_offline_do_stash()
867 if (list_empty(&stashing)) in hmdfs_stash_offline_do_stash()
870 hmdfs_stash_remote_inodes(conn, &stashing); in hmdfs_stash_offline_do_stash()
/kernel/linux/linux-5.10/drivers/gpu/drm/msm/
DNOTES69 have a better way than just stashing the platform device in a global
/kernel/linux/patches/linux-5.10/imx8mm_patch/patches/drivers/
D0033_linux_drivers_soc_scsi_spi_tee_thermal.patch300 0, /* EQCR_CI stashing threshold */
304 1, /* mem stashing priority enable */
305 1, /* mem stashing enable */
306 1, /* dequeue stashing priority enable */
307 - 0, /* dequeue stashing enable enable */
308 + 1, /* dequeue stashing enable enable */
309 0); /* EQCR_CI stashing priority enable */
315 1, /* EQCR_CI stashing threshold */
319 1, /* mem stashing priority enable */
320 1, /* mem stashing enable */
[all …]
D0036_linux_drivers_staging.patch22976 + * - the calls to qm_set_memory() hard-code the priority and CPC-stashing for
23794 + .txt = "Context-A stashing",
24040 + /* Any stashing configured */
24041 + if ((fqd.context_a.stashing.exclusive & 0x7) == 0)
24054 + fqd.context_a.stashing.annotation_cl);
24056 + fqd.context_a.stashing.data_cl);
24058 + fqd.context_a.stashing.context_cl);
25679 + * 'struct device' in order to get the PAMU stashing setup and the QMan
25680 + * portal [driver] won't function at all without ring stashing
25875 + /* Bind stashing LIODNs to the CPU we are currently executing on, and
[all …]
D0016_linux_drivers_crypto.patch6987 opts.fqd.context_a.stashing.exclusive = QM_STASHING_EXCL_CTX |
6990 + opts.fqd.context_a.stashing.data_cl = 1;
6991 + opts.fqd.context_a.stashing.context_cl = 1;
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/powerpc/fsl/
Dinterlaken-lac.txt96 0010 if stashing is enabled; otherwise, WIMG can be 0000 or 0010.
/kernel/linux/linux-5.10/drivers/crypto/caam/
Dqi.c642 opts.fqd.context_a.stashing.exclusive = QM_STASHING_EXCL_CTX | in alloc_rsp_fq_cpu()
/kernel/linux/linux-5.10/drivers/net/ethernet/freescale/dpaa/
Ddpaa_eth.c1112 initfq.fqd.context_a.stashing.exclusive = in dpaa_fq_init()
/kernel/linux/patches/linux-5.10/imx8mm_patch/patches/
D0005_linux_include.patch5031 + * Within that, the 'stashing' and 'taildrop' pieces are also factored out, the
5133 + /* Treat it as s/w portal stashing config */
5137 + struct qm_fqd_stashing stashing;
5145 + struct qm_fqd_stashing stashing;
5210 +#define QM_FQCTRL_CTXASTASHING 0x0080 /* Context-A stashing */
6314 + /* If the caller enables DQRR stashing (and thus wishes to operate the
6316 + * will stash to. Whether stashing is enabled or not, this setting is
6389 + * qman_create_fq(), as this allows stashing of caller-provided demux callback
6390 + * pointers at no extra cost to stashing of (driver-internal) FQ state. If the
6391 + * caller wishes to add per-FQ state and have it benefit from dequeue-stashing,
[all …]