| /linux-5.19.10/drivers/dma/ |
| D | timb_dma.c | 77 bool ongoing; member
182 if (td_chan->ongoing) { in __td_start_dma()
213 td_chan->ongoing = true; in __td_start_dma()
244 td_chan->ongoing = false; in __td_finish()
265 if (td_chan->ongoing) { in __td_ier_mask()
282 BUG_ON(td_chan->ongoing); in __td_start_next()
|
| /linux-5.19.10/kernel/ |
| D | tracepoint.c | 41 bool ongoing; member
54 snapshot->ongoing = true; in tp_rcu_get_state()
61 if (!snapshot->ongoing) in tp_rcu_cond_sync()
66 snapshot->ongoing = false; in tp_rcu_cond_sync()
|
| /linux-5.19.10/sound/soc/mxs/ |
| D | mxs-saif.h | 109 unsigned int ongoing; member
|
| D | mxs-saif.c | 95 if (master_saif->ongoing && rate != master_saif->cur_rate) { in mxs_saif_set_clk()
586 master_saif->ongoing = 1; in mxs_saif_trigger()
622 master_saif->ongoing = 0; in mxs_saif_trigger()
|
| /linux-5.19.10/Documentation/driver-api/mmc/ |
| D | mmc-async-req.rst | 48 truly non-blocking. If there is an ongoing async request it waits
50 doesn't wait for the new request to complete. If there is no ongoing
|
| /linux-5.19.10/drivers/net/wireless/broadcom/brcm80211/brcmfmac/ |
| D | fweh.c | 280 void brcmf_fweh_p2pdev_setup(struct brcmf_if *ifp, bool ongoing) in brcmf_fweh_p2pdev_setup() argument
282 ifp->drvr->fweh.p2pdev_setup_ongoing = ongoing; in brcmf_fweh_p2pdev_setup()
|
| D | fweh.h | 323 void brcmf_fweh_p2pdev_setup(struct brcmf_if *ifp, bool ongoing);
|
| /linux-5.19.10/Documentation/ABI/testing/ |
| D | sysfs-bus-fsi | 29 ongoing operation in case of an expired 'Master Time Out'
|
| D | sysfs-driver-hid-wiimote | 36 that the detection is still ongoing, "unknown" means, that the
|
| /linux-5.19.10/include/linux/mtd/ |
| D | onenand.h | 145 unsigned int ongoing; member
|
| /linux-5.19.10/Documentation/fb/ |
| D | pvr2fb.rst | 38 ongoing
|
| /linux-5.19.10/drivers/mtd/nand/onenand/ |
| D | onenand_omap2.c | 211 !this->ongoing) { in omap2_onenand_wait()
301 if (this->ongoing) in omap2_onenand_wait()
|
| /linux-5.19.10/arch/m68k/ |
| D | Kconfig | 101 It is an ongoing process to be certain the hardware in a machine
|
| /linux-5.19.10/Documentation/openrisc/ |
| D | openrisc_port.rst | 8 For information about OpenRISC processors and ongoing development:
|
| /linux-5.19.10/drivers/gpio/ |
| D | TODO | 1 This is a place for planning the ongoing long-term work in the GPIO
47 following ongoing work as well) we can delete the old global
|
| /linux-5.19.10/Documentation/RCU/ |
| D | NMI-RCU.rst | 98 not to return until all ongoing NMI handlers exit. It is therefore safe
|
| /linux-5.19.10/Documentation/devicetree/bindings/dma/ti/ |
| D | k3-udma.yaml | 22 segmentation or reassembly operations to be ongoing. The DMA controller
|
| /linux-5.19.10/Documentation/admin-guide/media/ |
| D | si470x.rst | 82 For processing RDS information, there is a project ongoing at:
|
| /linux-5.19.10/arch/parisc/ |
| D | Kconfig | 346 It is an ongoing process to be certain the hardware in a machine
|
| /linux-5.19.10/Documentation/arm/samsung-s3c24xx/ |
| D | overview.rst | 23 and extra interrupts is still ongoing.
|
| /linux-5.19.10/Documentation/driver-api/surface_aggregator/clients/ |
| D | dtx.rst | 577 latch when sent during an ongoing detachment process. It will be silently
599 Acknowledges and confirms a latch request. If sent during an ongoing
|
| /linux-5.19.10/Documentation/staging/ |
| D | tee.rst | 41 - TEE_IOC_CANCEL may cancel an ongoing TEE_IOC_OPEN_SESSION or TEE_IOC_INVOKE.
|
| /linux-5.19.10/arch/ia64/ |
| D | Kconfig | 375 It is an ongoing process to be certain the hardware in a machine
|
| /linux-5.19.10/Documentation/process/ |
| D | 3.Early-stage.rst | 35 via the rlimit mechanism for the short term, and ongoing latency reduction
|
| D | embargoed-hardware-issues.rst | 226 up to date in order to follow the ongoing upstream kernel development,
|