drivers/media/platform/qcom/camss/camss-vfe-vbif.c
Source file repositories/reference/linux-study-clean/drivers/media/platform/qcom/camss/camss-vfe-vbif.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/platform/qcom/camss/camss-vfe-vbif.c- Extension
.c- Size
- 650 bytes
- Lines
- 32
- 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/io.hcamss.hcamss-vfe.hcamss-vfe-vbif.h
Detected Declarations
function Copyrightfunction vfe_vbif_apply_settings
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-only
/*
* camss-vfe-vbif.c
*
* Qualcomm MSM Camera Subsystem - VFE VBIF Module
*
* Copyright (c) 2025, The Linux Foundation. All rights reserved.
*
*/
#include <linux/io.h>
#include "camss.h"
#include "camss-vfe.h"
#include "camss-vfe-vbif.h"
#define VBIF_FIXED_SORT_EN 0x30
#define VBIF_FIXED_SORT_SEL0 0x34
void vfe_vbif_write_reg(struct vfe_device *vfe, u32 reg, u32 val)
{
writel_relaxed(val, vfe->vbif_base + reg);
}
int vfe_vbif_apply_settings(struct vfe_device *vfe)
{
vfe_vbif_write_reg(vfe, VBIF_FIXED_SORT_EN, 0xfff);
vfe_vbif_write_reg(vfe, VBIF_FIXED_SORT_SEL0, 0x555000);
return 0;
}
Annotation
- Immediate include surface: `linux/io.h`, `camss.h`, `camss-vfe.h`, `camss-vfe-vbif.h`.
- Detected declarations: `function Copyright`, `function vfe_vbif_apply_settings`.
- 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.