arch/m68k/kernel/pcibios.c

File Facts

System

Linux kernel

Corpus path

arch/m68k/kernel/pcibios.c

Extension

.c

Size

2153 bytes

Lines

82

Domain

Architecture Layer

Bucket

arch/m68k

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/kernel.h
• linux/types.h
• linux/mm.h
• linux/init.h
• linux/pci.h

Detected Declarations

• function pcibios_align_resource
• function pcibios_enable_device
• function Bridges
• function pcibios_fixup_bus
• function list_for_each_entry

Annotated Snippet

if (newcmd != cmd) {
			pr_info("PCI: enabling bridge %s (0x%04x -> 0x%04x)\n",
				pci_name(dev), cmd, newcmd);
			pci_write_config_word(dev, PCI_COMMAND, newcmd);
		}
	}
	return 0;
}

void pcibios_fixup_bus(struct pci_bus *bus)
{
	struct pci_dev *dev;

	list_for_each_entry(dev, &bus->devices, bus_list) {
		pci_write_config_byte(dev, PCI_CACHE_LINE_SIZE, 8);
		pci_write_config_byte(dev, PCI_LATENCY_TIMER, 32);
	}
}

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/types.h`, `linux/mm.h`, `linux/init.h`, `linux/pci.h`.
• Detected declarations: `function pcibios_align_resource`, `function pcibios_enable_device`, `function Bridges`, `function pcibios_fixup_bus`, `function list_for_each_entry`.
• Atlas domain: Architecture Layer / arch/m68k.
• 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.