omap_vc_config_channel(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… omap_vc_config_channel β€” kernel API manual, but make it make sense

okay bestie, so this page is from the Kernel API Manual and it's all about omap_vc_config_channel(9) β€” say that three times fast, I dare you 🫢


✨ NAME ✨

omap_vc_config_channel β€” configure the VC channel to PMIC mappings, periodt


🌸 SYNOPSIS 🌸

int omap_vc_config_channel (struct voltagedomain *voltdm );

πŸŽ€ ARGUMENTS πŸŽ€

  • voltdm β€” a pointer to the voltagdomain that defines the VC channel you actually want. that's it, that's the whole argument, she's lowkey simple πŸ’…

πŸ¦‹ DESCRIPTION πŸ¦‹

So this function configures the VC channel β†’ PMIC mappings for the following PMIC settings, and yes we're listing them all because details are the moment:

  • i2c slave address (SA)
  • voltage configuration address (RAV)
  • command configuration address (RAC) plus its enable bit (RACEN)
  • command values for ON, ONLP, RET and OFF (CMD)

ngl, here's the catch: this function currently only allows flexible configuration of the non-default channel. like, that's just the rules rn 🫠

Starting with OMAP4, there are more than 2 channels β€” and one of them is defined as the default (on OMAP4, it's MPU, main character energy fr fr πŸ‘‘). Only the non-default channel can be configured.

so to recap: multiple channels, one default, and only the non-default one is getting the glow-up. the default one is booked and busy elsewhere πŸ’€

πŸ”₯ SEE ALSO πŸ”₯

go read those next, bestie, they're all in the friend group πŸ’–


and that's the whole page, hope you slayed your VC channel config ✨ this little gem lives over in ./arch/arm/mach-omap2, dated October 2026, and it came to you courtesy of the Kernel API Manual β€” mwah, kisses, go touch some omap registers πŸŽ€πŸ’œ

πŸ“¦ where this page comes from