gpmc_cs_remap(9)

💖 gpmc_cs_remap — remaps a chip-select physical base address 💖

okay so bestie, we’re in the Kernel API Manual and this page is literally called gpmc_cs_remap(9). It’s giving “move this chip-select to a new physical base address” energy, and I’m obsessed. 🎀

🦋 NAME 🦋

gpmc_cs_remap — remaps a chip-select physical base address.

✨ SYNOPSIS ✨

int gpmc_cs_remap (int cs , u32 base );

💅 ARGUMENTS 💅

• cs — the chip-select to remap, aka the one getting its glow-up.
• base — the physical base address to re-map that chip-select to, no cap.

🧚 DESCRIPTION 🧚

okay so this function re-maps a chip-select to a new physical base address that you pass in as base. That’s the whole vibe. It returns 0 on success, and on failure it returns the appropriate negative error code — so watch for that, bestie. 😭

🌈 SEE ALSO 🌈

• Kernel file: ./drivers/memory/omap-gpmc.c
• gpmc_get_clk_period(9)
• get_gpmc_timing_reg(9)
• set_gpmc_timing_reg(9)
• gpmc_calc_waitmonitoring_divider(9)
• gpmc_calc_divider(9)
• gpmc_cs_set_timings(9)
• gpmc_configure(9)
• gpmc_omap_get_nand_ops(9)
• gpmc_cs_program_settings(9)
• gpmc_read_settings_dt(9)
• gpmc_probe_generic_child(9)

okay that’s the whole page, bestie 💖 huge slay from ./drivers/memory, dated October 2026, and yes it’s still the gpmc_cs_remap(9) manual page 🫶✨