drivers/media/platform/samsung/s5p-mfc/s5p_mfc_intr.c
Source file repositories/reference/linux-study-clean/drivers/media/platform/samsung/s5p-mfc/s5p_mfc_intr.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/platform/samsung/s5p-mfc/s5p_mfc_intr.c- Extension
.c- Size
- 2332 bytes
- Lines
- 89
- Domain
- Driver Families
- Bucket
- drivers/media
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/delay.hlinux/errno.hlinux/io.hlinux/sched.hlinux/wait.hs5p_mfc_common.hs5p_mfc_debug.hs5p_mfc_intr.h
Detected Declarations
function MFCfunction s5p_mfc_clean_dev_int_flagsfunction s5p_mfc_wait_for_done_ctxfunction s5p_mfc_clean_ctx_int_flags
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-only
/*
* drivers/media/platform/samsung/mfc5/s5p_mfc_intr.c
*
* C file for Samsung MFC (Multi Function Codec - FIMV) driver
* This file contains functions used to wait for command completion.
*
* Kamil Debski, Copyright (C) 2011 Samsung Electronics Co., Ltd.
* http://www.samsung.com/
*/
#include <linux/delay.h>
#include <linux/errno.h>
#include <linux/io.h>
#include <linux/sched.h>
#include <linux/wait.h>
#include "s5p_mfc_common.h"
#include "s5p_mfc_debug.h"
#include "s5p_mfc_intr.h"
int s5p_mfc_wait_for_done_dev(struct s5p_mfc_dev *dev, int command)
{
int ret;
ret = wait_event_interruptible_timeout(dev->queue,
(dev->int_cond && (dev->int_type == command
|| dev->int_type == S5P_MFC_R2H_CMD_ERR_RET)),
msecs_to_jiffies(MFC_INT_TIMEOUT));
if (ret == 0) {
mfc_err("Interrupt (dev->int_type:%d, command:%d) timed out\n",
dev->int_type, command);
return 1;
} else if (ret == -ERESTARTSYS) {
mfc_err("Interrupted by a signal\n");
return 1;
}
mfc_debug(1, "Finished waiting (dev->int_type:%d, command: %d)\n",
dev->int_type, command);
if (dev->int_type == S5P_MFC_R2H_CMD_ERR_RET)
return 1;
return 0;
}
void s5p_mfc_clean_dev_int_flags(struct s5p_mfc_dev *dev)
{
dev->int_cond = 0;
dev->int_type = 0;
dev->int_err = 0;
}
int s5p_mfc_wait_for_done_ctx(struct s5p_mfc_ctx *ctx,
int command, int interrupt)
{
int ret;
if (interrupt) {
ret = wait_event_interruptible_timeout(ctx->queue,
(ctx->int_cond && (ctx->int_type == command
|| ctx->int_type == S5P_MFC_R2H_CMD_ERR_RET)),
msecs_to_jiffies(MFC_INT_TIMEOUT));
} else {
ret = wait_event_timeout(ctx->queue,
(ctx->int_cond && (ctx->int_type == command
|| ctx->int_type == S5P_MFC_R2H_CMD_ERR_RET)),
msecs_to_jiffies(MFC_INT_TIMEOUT));
}
if (ret == 0) {
mfc_err("Interrupt (ctx->int_type:%d, command:%d) timed out\n",
ctx->int_type, command);
return 1;
} else if (ret == -ERESTARTSYS) {
mfc_err("Interrupted by a signal\n");
return 1;
}
mfc_debug(1, "Finished waiting (ctx->int_type:%d, command: %d)\n",
ctx->int_type, command);
if (ctx->int_type == S5P_MFC_R2H_CMD_ERR_RET)
return 1;
return 0;
}
void s5p_mfc_clean_ctx_int_flags(struct s5p_mfc_ctx *ctx)
{
ctx->int_cond = 0;
ctx->int_type = 0;
ctx->int_err = 0;
}
Annotation
- Immediate include surface: `linux/delay.h`, `linux/errno.h`, `linux/io.h`, `linux/sched.h`, `linux/wait.h`, `s5p_mfc_common.h`, `s5p_mfc_debug.h`, `s5p_mfc_intr.h`.
- Detected declarations: `function MFC`, `function s5p_mfc_clean_dev_int_flags`, `function s5p_mfc_wait_for_done_ctx`, `function s5p_mfc_clean_ctx_int_flags`.
- Atlas domain: Driver Families / drivers/media.
- Implementation status: source implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.