Home
last modified time | relevance | path

Searched full:apps (Results 1 – 25 of 221) sorted by relevance

123456789

/linux-6.8/Documentation/devicetree/bindings/mailbox/
Dqcom,apcs-kpss-global.yaml21 - qcom,ipq5018-apcs-apps-global
22 - qcom,ipq5332-apcs-apps-global
23 - qcom,ipq8074-apcs-apps-global
24 - qcom,ipq9574-apcs-apps-global
25 - const: qcom,ipq6018-apcs-apps-global
28 - qcom,qcs404-apcs-apps-global
59 - qcom,ipq6018-apcs-apps-global
150 - qcom,ipq6018-apcs-apps-global
183 - qcom,ipq6018-apcs-apps-global
218 compatible = "qcom,qcs404-apcs-apps-global",
/linux-6.8/drivers/net/ethernet/netronome/nfp/
Dnfp_app.c18 static const struct nfp_app_type *apps[] = { variable
232 if (id >= ARRAY_SIZE(apps) || !apps[id]) { in nfp_app_alloc()
237 if (WARN_ON(!apps[id]->name || !apps[id]->vnic_alloc)) in nfp_app_alloc()
239 if (WARN_ON(!apps[id]->ctrl_msg_rx && apps[id]->ctrl_msg_rx_raw)) in nfp_app_alloc()
249 app->type = apps[id]; in nfp_app_alloc()
/linux-6.8/Documentation/devicetree/bindings/misc/
Dqcom,fastrpc.yaml15 invocations across DSP and APPS boundaries. This enables developers
41 - const: fastrpcglink-apps-dsp
53 - const: fastrpcsmd-apps-dsp
120 qcom,glink-channels = "fastrpcglink-apps-dsp";
/linux-6.8/drivers/mailbox/
Dqcom-apcs-ipc-mailbox.c142 { .compatible = "qcom,ipq6018-apcs-apps-global", .data = &ipq6018_apcs_data },
154 { .compatible = "qcom,qcs404-apcs-apps-global", .data = &msm8916_apcs_data },
159 { .compatible = "qcom,ipq5332-apcs-apps-global", .data = &ipq6018_apcs_data },
160 { .compatible = "qcom,ipq8074-apcs-apps-global", .data = &ipq6018_apcs_data },
/linux-6.8/drivers/scsi/megaraid/
Dmegaraid_ioctl.h70 #define APPTYPE_MIMD 0x00 /* old existing apps */
71 #define APPTYPE_UIOC 0x01 /* new apps using uioc */
116 /* User Apps: */
198 * mcontroller : adapter info structure for old mimd_t apps
/linux-6.8/Documentation/scheduler/
Dsched-nice-design.rst49 people were running number crunching apps at nice +19.)
84 run audio (and other multimedia) apps under RT priorities such as
109 and forcing audio apps to run under the more dangerous SCHED_FIFO
/linux-6.8/Documentation/filesystems/
Drelay.rst70 klog and relay-apps example code
76 The relay-apps example tarball, available on the relay sourceforge
83 The 'klog debugging functions' patch (klog.patch in the relay-apps
94 i.e. without using any of the relay-apps example code or klog, but
104 klog and the relay-apps examples can be found in the relay-apps
445 a separate array. See the 'reserve' example in the relay-apps tarball
/linux-6.8/Documentation/devicetree/bindings/soc/qcom/
Dqcom,smsm.yaml115 # the wireless processor, defined from the 8974 apps processor's
127 apps_smsm: apps@0 {
/linux-6.8/drivers/gpu/drm/nouveau/nvkm/nvfw/
Dhs.c76 hdr->apps[(i * 2) + 0], hdr->apps[(i * 2) + 1]); in nvfw_hs_load_header()
/linux-6.8/Documentation/locking/
Dpi-futex.rst39 I.e. critical RT apps often choose lock structures to protect critical
53 apps have a very fair expectation of being able to use locks, we've got
/linux-6.8/arch/arc/
DKconfig403 bool "Support DSP for userspace apps"
412 bool "Support DSP with AGU for userspace apps"
515 This options allows a Linux userland apps to directly access
/linux-6.8/drivers/gpu/drm/nouveau/nvkm/falcon/
Dfw.c261 fw->imem_base_img = lhdr->apps[0]; in nvkm_falcon_fw_ctor_hs()
262 fw->imem_base = ALIGN(lhdr->apps[0], 0x100); in nvkm_falcon_fw_ctor_hs()
263 fw->imem_size = lhdr->apps[lhdr->num_apps + 0]; in nvkm_falcon_fw_ctor_hs()
/linux-6.8/Documentation/devicetree/bindings/pci/
Dfsl,imx6q-pcie-common.yaml257 - const: apps
265 - const: apps
/linux-6.8/drivers/media/test-drivers/vivid/
DKconfig23 Say Y here if you want to test video apps or debug V4L devices.
/linux-6.8/drivers/gpu/drm/nouveau/include/nvfw/
Dhs.h40 u32 apps[]; member
/linux-6.8/net/vmw_vsock/
Dhyperv_transport.c114 * when we write apps to connect to the host, we can only use VMADDR_CID_ANY
116 * write apps to bind() & listen() in the VM, we can only use VMADDR_CID_ANY
139 * Hyper-V Sockets apps on the host and in Linux VM is:
147 * When we write apps on the host to connect(), the GUID ServiceID is used.
148 * When we write apps in Linux VM to connect(), we only need to specify the
/linux-6.8/include/linux/platform_data/media/
Dsi4713.h36 __u32 reserved[4]; /* drivers and apps must init this to 0 */
/linux-6.8/arch/parisc/include/uapi/asm/
Dstat.h41 * How 64-bit apps are going to be compiled, I have no idea. But at least
/linux-6.8/drivers/gpu/drm/msm/disp/dpu1/
Ddpu_crtc.h25 * voting through apps rsc
27 * voting through apps rsc
/linux-6.8/Documentation/devicetree/bindings/interconnect/
Dqcom,bcm-voter.yaml47 # Example 1: apps bcm_voter on SDM845 SoC should be defined inside &apps_rsc node
/linux-6.8/drivers/media/rc/keymaps/
Drc-mecool-kii-pro.c49 { 0x58, KEY_APPSELECT }, // APPS
/linux-6.8/include/scsi/
Dscsi_status.h68 * with userspace apps that parse the host byte for SG IO, we leave
/linux-6.8/Documentation/fb/
Dcmap_xfbdev.rst24 - X11 apps do something like the following when trying to use grayscale::
/linux-6.8/Documentation/usb/
Dmtouchusb.rst49 touchscreen for embedded apps using QTEmbedded, DirectFB, etc. So I feel the
/linux-6.8/include/uapi/linux/
Dinotify.h63 * the future and not break backward compatibility. Apps will get only the

123456789