arch/arm/mach-omap1/board-sx1.h
Source file repositories/reference/linux-study-clean/arch/arm/mach-omap1/board-sx1.h
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/mach-omap1/board-sx1.h- Extension
.h- Size
- 1121 bytes
- Lines
- 46
- 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
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef __ASM_ARCH_SX1_I2C_CHIPS_H
#define __ASM_ARCH_SX1_I2C_CHIPS_H
#define SOFIA_MAX_LIGHT_VAL 0x2B
#define SOFIA_I2C_ADDR 0x32
/* Sofia reg 3 bits masks */
#define SOFIA_POWER1_REG 0x03
#define SOFIA_USB_POWER 0x01
#define SOFIA_MMC_POWER 0x04
#define SOFIA_BLUETOOTH_POWER 0x08
#define SOFIA_MMILIGHT_POWER 0x20
#define SOFIA_POWER2_REG 0x04
#define SOFIA_BACKLIGHT_REG 0x06
#define SOFIA_KEYLIGHT_REG 0x07
#define SOFIA_DIMMING_REG 0x09
/* Function Prototypes for SX1 devices control on I2C bus */
int sx1_setbacklight(u8 backlight);
int sx1_getbacklight(u8 *backlight);
int sx1_setkeylight(u8 keylight);
int sx1_getkeylight(u8 *keylight);
int sx1_setmmipower(u8 onoff);
int sx1_setusbpower(u8 onoff);
int sx1_i2c_read_byte(u8 devaddr, u8 regoffset, u8 *value);
int sx1_i2c_write_byte(u8 devaddr, u8 regoffset, u8 value);
/* MMC prototypes */
extern void sx1_mmc_init(void);
extern void sx1_mmc_slot_cover_handler(void *arg, int state);
#endif /* __ASM_ARCH_SX1_I2C_CHIPS_H */
Annotation
- 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.