arch/arm/mach-s3c/setup-fb-24bpp-s3c64xx.c

File Facts

System

Linux kernel

Corpus path

arch/arm/mach-s3c/setup-fb-24bpp-s3c64xx.c

Extension

.c

Size

550 bytes

Lines

23

Domain

Architecture Layer

Bucket

arch/arm

Inferred role

Architecture Layer: implementation source

Status

source implementation candidate

Why This File Exists

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

• CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

Dependency Surface

• linux/kernel.h
• linux/types.h
• linux/gpio.h
• fb.h
• gpio-cfg.h
• gpio-samsung.h

Detected Declarations

• function s3c64xx_fb_gpio_setup_24bpp

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0
//
// Copyright 2008 Openmoko, Inc.
// Copyright 2008 Simtec Electronics
//	Ben Dooks <ben@simtec.co.uk>
//	http://armlinux.simtec.co.uk/
//
// Base S3C64XX setup information for 24bpp LCD framebuffer

#include <linux/kernel.h>
#include <linux/types.h>
#include <linux/gpio.h>

#include "fb.h"
#include "gpio-cfg.h"
#include "gpio-samsung.h"

void s3c64xx_fb_gpio_setup_24bpp(void)
{
	s3c_gpio_cfgrange_nopull(S3C64XX_GPI(0), 16, S3C_GPIO_SFN(2));
	s3c_gpio_cfgrange_nopull(S3C64XX_GPJ(0), 12, S3C_GPIO_SFN(2));
}

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/types.h`, `linux/gpio.h`, `fb.h`, `gpio-cfg.h`, `gpio-samsung.h`.
• Detected declarations: `function s3c64xx_fb_gpio_setup_24bpp`.
• Atlas domain: Architecture Layer / arch/arm.
• 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.