gpmc_probe_generic_child(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… gpmc_probe_generic_child β€” the Kernel API Manual, bestie ✨

okay so this is a section 9 kernel API page, from the Kernel API Manual, and it's literally about the GPMC driver. yes we're in the kernel, yes it's giving embedded-core realness, and yes i'm gonna walk you through it 🫢


✨ NAME ✨

gpmc_probe_generic_child β€” configures the gpmc for a child device πŸ’«


🌸 SYNOPSIS 🌸

int gpmc_probe_generic_child (struct platform_device *pdev , struct
       device_node *child );

that's the whole signature, no cap. two pointers in, an int out πŸŽ€


πŸ¦‹ ARGUMENTS πŸ¦‹

  • pdev β€” pointer to gpmc platform device. like, the parent energy πŸ‘‘
  • child β€” pointer to device-tree node for child device. the main character in question 🌟

πŸ’– DESCRIPTION πŸ’–

so what does it actually do? it allocates and configures a GPMC chip-select for a child device. that's it, that's the whole vibe ✨

and then it reports back:

  • returns 0 on success β€” slay, we ate πŸ’…
  • returns the appropriate negative error code on failure β€” not slay, but at least it tells you why 😭
ngl, if you get a negative number back, that's not a vibe β€” that's an error code, and you should go read it properly πŸ™ˆ

πŸ”₯ SEE ALSO πŸ”₯

the kernel file itself lives at ./drivers/memory/omap-gpmc.c β€” go drink from the source bestie πŸ“

and the whole friend group:

literally the entire group chat, all tagged, all iconic πŸ‘‘


and that's the page!! 🧚 source: ./drivers/memory, dated October 2026 β€” so mark your calendar, screenshot it, frame it, this manpage said see you then πŸ’œπŸŽ€βœ¨

πŸ“¦ where this page comes from