arch/arm/mach-pxa/gumstix.c
Source file repositories/reference/linux-study-clean/arch/arm/mach-pxa/gumstix.c
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/mach-pxa/gumstix.c- Extension
.c- Size
- 5226 bytes
- Lines
- 239
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/module.hlinux/kernel.hlinux/init.hlinux/platform_device.hlinux/interrupt.hlinux/delay.hlinux/mtd/mtd.hlinux/mtd/partitions.hlinux/gpio/machine.hlinux/gpio/property.hlinux/gpio.hlinux/err.hlinux/clk.hasm/setup.hasm/page.hasm/mach-types.hasm/irq.hlinux/sizes.hasm/mach/arch.hasm/mach/map.hasm/mach/irq.hasm/mach/flash.hpxa25x.hlinux/platform_data/mmc-pxamci.hudc.hgumstix.hdevices.hgeneric.h
Detected Declarations
function gumstix_mmc_initfunction gumstix_mmc_initfunction gumstix_udc_initfunction gumstix_udc_initfunction gumstix_setup_bt_clockfunction gumstix_bluetooth_initfunction gumstix_bluetooth_initfunction __attribute__function __attribute__function carrier_board_initfunction gumstix_init
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-only
/*
* linux/arch/arm/mach-pxa/gumstix.c
*
* Support for the Gumstix motherboards.
*
* Original Author: Craig Hughes
* Created: Feb 14, 2008
* Copyright: Craig Hughes
*
* Implemented based on lubbock.c by Nicolas Pitre and code from Craig
* Hughes
*/
#include <linux/module.h>
#include <linux/kernel.h>
#include <linux/init.h>
#include <linux/platform_device.h>
#include <linux/interrupt.h>
#include <linux/delay.h>
#include <linux/mtd/mtd.h>
#include <linux/mtd/partitions.h>
#include <linux/gpio/machine.h>
#include <linux/gpio/property.h>
#include <linux/gpio.h>
#include <linux/err.h>
#include <linux/clk.h>
#include <asm/setup.h>
#include <asm/page.h>
#include <asm/mach-types.h>
#include <asm/irq.h>
#include <linux/sizes.h>
#include <asm/mach/arch.h>
#include <asm/mach/map.h>
#include <asm/mach/irq.h>
#include <asm/mach/flash.h>
#include "pxa25x.h"
#include <linux/platform_data/mmc-pxamci.h>
#include "udc.h"
#include "gumstix.h"
#include "devices.h"
#include "generic.h"
static struct resource flash_resource = {
.start = 0x00000000,
.end = SZ_64M - 1,
.flags = IORESOURCE_MEM,
};
static struct mtd_partition gumstix_partitions[] = {
{
.name = "Bootloader",
.size = 0x00040000,
.offset = 0,
.mask_flags = MTD_WRITEABLE /* force read-only */
} , {
.name = "rootfs",
.size = MTDPART_SIZ_FULL,
.offset = MTDPART_OFS_APPEND
}
};
static struct flash_platform_data gumstix_flash_data = {
.map_name = "cfi_probe",
.parts = gumstix_partitions,
.nr_parts = ARRAY_SIZE(gumstix_partitions),
.width = 2,
};
static struct platform_device gumstix_flash_device = {
.name = "pxa2xx-flash",
.id = 0,
.dev = {
.platform_data = &gumstix_flash_data,
},
.resource = &flash_resource,
.num_resources = 1,
};
static struct platform_device *devices[] __initdata = {
&gumstix_flash_device,
};
#ifdef CONFIG_MMC_PXA
static struct pxamci_platform_data gumstix_mci_platform_data = {
.ocr_mask = MMC_VDD_32_33|MMC_VDD_33_34,
Annotation
- Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/init.h`, `linux/platform_device.h`, `linux/interrupt.h`, `linux/delay.h`, `linux/mtd/mtd.h`, `linux/mtd/partitions.h`.
- Detected declarations: `function gumstix_mmc_init`, `function gumstix_mmc_init`, `function gumstix_udc_init`, `function gumstix_udc_init`, `function gumstix_setup_bt_clock`, `function gumstix_bluetooth_init`, `function gumstix_bluetooth_init`, `function __attribute__`, `function __attribute__`, `function carrier_board_init`.
- 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.