get_gpmc_timing_reg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– get_gpmc_timing_reg(9) πŸ’–

okay so welcome to the Kernel API Manual, bestie β€” this page is literally all about get_gpmc_timing_reg(9), and it's giving β€œread a timing parameter and print DTS settings for it” energy. slay ✨


🌸 NAME 🌸

get_gpmc_timing_reg β€” read a timing parameter and print DTS settings for it. iconic behavior, no cap.

πŸŽ€ SYNOPSIS πŸŽ€

int get_gpmc_timing_reg (int cs , int reg , int st_bit , int end_bit ,
int max , const char *name , const enum gpmc_clk_domain cd , int shift ,
bool raw , bool noval );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • cs β€” Chip Select Region. fr fr, that's the region.
  • reg β€” GPMC_CS_CONFIGn register offset. The offset, bestie.
  • st_bit β€” Start Bit.
  • end_bit β€” End Bit. Must be >= st_bit, okay?
  • max β€” Maximum parameter value (before optional shift). If 0, maximum is as high as st_bit and end_bit allow. vibe check passed.
  • name β€” DTS node name, w/o "gpmc,".
  • cd β€” Clock Domain of timing parameter.
  • shift β€” Parameter value left shifts shift, which is then printed instead of value.
  • raw β€” Raw Format Option. raw format: gpmc,name = <value>; tick format: gpmc,name = <value> /zwj;* x ns -- y ns; x ticks *zwj;/. Where x ns -- y ns result in the same tick value. When max is exceeded, "invalid" is printed inside comment. not me explaining raw format but here we are πŸ’…
  • noval β€” Parameter values equal to 0 are not printed.

πŸ”₯ RETURN πŸ”₯

Specified timing parameter (after optional shift). That's the return value, bestie. periodt 🌈

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/memory/omap-gpmc.c and these iconic references:


okay that's the whole page! source/version: ./drivers/memory; date: October 2026; page: get_gpmc_timing_reg(9). bye bestie, go read those timing regs πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from