Searched refs:apps (Results 1 – 25 of 70) sorted by relevance
123
/Linux-v6.6/drivers/net/ethernet/netronome/nfp/ |
D | nfp_app.c | 18 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-v6.6/drivers/gpu/drm/nouveau/nvkm/nvfw/ |
D | hs.c | 76 hdr->apps[(i * 2) + 0], hdr->apps[(i * 2) + 1]); in nvfw_hs_load_header()
|
/Linux-v6.6/drivers/gpu/drm/nouveau/nvkm/falcon/ |
D | fw.c | 261 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-v6.6/drivers/gpu/drm/nouveau/include/nvfw/ |
D | hs.h | 40 u32 apps[]; member
|
/Linux-v6.6/Documentation/scheduler/ |
D | sched-nice-design.rst | 49 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-v6.6/drivers/media/test-drivers/vivid/ |
D | Kconfig | 24 Say Y here if you want to test video apps or debug V4L devices.
|
/Linux-v6.6/Documentation/arch/ia64/ |
D | efirtc.rst | 31 Because we wanted to minimize the impact on existing user-level apps using 133 As of today, none of the existing user-level apps supports this feature.
|
/Linux-v6.6/Documentation/filesystems/ |
D | relay.rst | 70 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-v6.6/Documentation/fb/ |
D | cmap_xfbdev.rst | 24 - X11 apps do something like the following when trying to use grayscale::
|
D | deferred_io.rst | 40 apps to pretend to have a normal framebuffer but reswizzle for the device
|
/Linux-v6.6/arch/arm64/boot/dts/qcom/ |
D | msm8916-samsung-j5-common.dtsi | 21 tz-apps@85500000 {
|
D | msm8916-samsung-gt5-common.dtsi | 23 tz-apps@85500000 {
|
D | ipq5332.dtsi | 334 compatible = "qcom,ipq5332-apcs-apps-global", 335 "qcom,ipq6018-apcs-apps-global";
|
D | msm8916-samsung-a2015-common.dtsi | 22 tz-apps@85500000 {
|
D | msm8939-samsung-a7.dts | 28 tz-apps@85500000 {
|
D | ipq9574.dtsi | 651 compatible = "qcom,ipq9574-apcs-apps-global", 652 "qcom,ipq6018-apcs-apps-global";
|
D | msm8916-samsung-serranove.dts | 42 tz-apps@85500000 {
|
D | ipq8074.dtsi | 719 compatible = "qcom,ipq8074-apcs-apps-global", 720 "qcom,ipq6018-apcs-apps-global";
|
/Linux-v6.6/Documentation/locking/ |
D | pi-futex.rst | 39 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-v6.6/Documentation/usb/ |
D | mtouchusb.rst | 49 touchscreen for embedded apps using QTEmbedded, DirectFB, etc. So I feel the
|
/Linux-v6.6/Documentation/arch/openrisc/ |
D | openrisc_port.rst | 111 running many standard linux apps.
|
/Linux-v6.6/arch/arc/ |
D | Kconfig | 408 bool "Support DSP for userspace apps" 417 bool "Support DSP with AGU for userspace apps" 520 This options allows a Linux userland apps to directly access
|
/Linux-v6.6/arch/arm/boot/dts/nxp/imx/ |
D | imx7d.dtsi | 155 reset-names = "pciephy", "apps", "turnoff";
|
/Linux-v6.6/drivers/staging/media/atomisp/ |
D | TODO | 75 * Fix not all v4l2 apps working, e.g. cheese does not work
|
/Linux-v6.6/Documentation/admin-guide/media/ |
D | si4713.rst | 185 The tool can be found in v4l-dvb repository under v4l2-apps/util directory.
|
123