drivers/staging/media/atomisp/pci/hive_isp_css_common/host/gpio_private.h

File Facts

System

Linux kernel

Corpus path

drivers/staging/media/atomisp/pci/hive_isp_css_common/host/gpio_private.h

Extension

.h

Size

852 bytes

Lines

34

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.

Dependency Surface

• assert_support.h
• device_access.h

Detected Declarations

• function Copyright
• function gpio_reg_load

Annotated Snippet

#ifndef __GPIO_PRIVATE_H_INCLUDED__
#define __GPIO_PRIVATE_H_INCLUDED__

#include "assert_support.h"
#include "device_access.h"

static inline void gpio_reg_store(
    const gpio_ID_t	ID,
    const unsigned int		reg,
    const hrt_data			value)
{
	OP___assert(ID < N_GPIO_ID);
	OP___assert(GPIO_BASE[ID] != (hrt_address) - 1);
	ia_css_device_store_uint32(GPIO_BASE[ID] + reg * sizeof(hrt_data), value);
	return;
}

static inline hrt_data gpio_reg_load(
    const gpio_ID_t	ID,
    const unsigned int		reg)
{
	OP___assert(ID < N_GPIO_ID);
	OP___assert(GPIO_BASE[ID] != (hrt_address) - 1);
	return ia_css_device_load_uint32(GPIO_BASE[ID] + reg * sizeof(hrt_data));
}

#endif /* __GPIO_PRIVATE_H_INCLUDED__ */

Annotation

• Immediate include surface: `assert_support.h`, `device_access.h`.
• Detected declarations: `function Copyright`, `function gpio_reg_load`.
• 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.