gpmc_read_settings_dt(9)

🌸 NAME 🌸

okay so bestie, this is gpmc_read_settings_dt(9) straight outta the Kernel API Manual, and it does exactly what it says on the tin: it reads gpmc settings from device-tree. ✨

---

🦋 SYNOPSIS 🦋

void gpmc_read_settings_dt (struct device_node *np , struct gpmc_settings *p );

---

🎀 ARGUMENTS 🎀

• np — pointer to the device-tree node for a gpmc child device. like, the node bestie, not the whole tree 💅
• p — pointer to the gpmc settings structure. this is where the good stuff gets stored 🫶

---

💖 DESCRIPTION 💖

Reads the GPMC settings for a GPMC child device from device-tree and stores them in the GPMC settings structure passed. no cap, that's the whole vibe: device-tree in, settings struct out. 🌈

The GPMC settings structure is initialised to zero by this function, and so any previously stored settings will be cleared. so if you had old settings in there, they're gone, periodt. 💀

bestie, please remember: this function zeroes the structure first. any previously stored settings get wiped. not me warning you twice, but also yes. 🙈

---

🔥 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_cs_remap(9)
• gpmc_probe_generic_child(9)

---

mwah 💋 — signing off from the ./drivers/memory corner of the kernel, dated October 2026. stay slay, stay zeroed. 👑