drivers/staging/media/atomisp/pci/sh_css_host_data.c
Source file repositories/reference/linux-study-clean/drivers/staging/media/atomisp/pci/sh_css_host_data.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/media/atomisp/pci/sh_css_host_data.c- Extension
.c- Size
- 658 bytes
- Lines
- 35
- Domain
- Driver Families
- Bucket
- drivers/staging
- 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.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/slab.hia_css_host_data.hsh_css_internal.h
Detected Declarations
function Copyrightfunction ia_css_host_data_free
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/*
* Support for Intel Camera Imaging ISP subsystem.
* Copyright (c) 2015, Intel Corporation.
*/
#include <linux/slab.h>
#include <ia_css_host_data.h>
#include <sh_css_internal.h>
struct ia_css_host_data *ia_css_host_data_allocate(size_t size)
{
struct ia_css_host_data *me;
me = kmalloc_obj(struct ia_css_host_data);
if (!me)
return NULL;
me->size = (uint32_t)size;
me->address = kvmalloc(size, GFP_KERNEL);
if (!me->address) {
kfree(me);
return NULL;
}
return me;
}
void ia_css_host_data_free(struct ia_css_host_data *me)
{
if (me) {
kvfree(me->address);
me->address = NULL;
kfree(me);
}
}
Annotation
- Immediate include surface: `linux/slab.h`, `ia_css_host_data.h`, `sh_css_internal.h`.
- Detected declarations: `function Copyright`, `function ia_css_host_data_free`.
- Atlas domain: Driver Families / drivers/staging.
- 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.