cros_ec_lpc...rite_address(9)
π cros_ec_lpc_mec_emi_write_address(9) π
okay bestie, welcome to the Kernel API Manual β¨ this one's a tiny little page but it's lowkey iconic β it's all about the ChromeOS Embedded Controller LPC memory-mapped situation π¦
πΈ NAME πΈ
cros_ec_lpc_mec_emi_write_address β initialize EMI at a given address, periodt π
β¨ SYNOPSIS β¨
void cros_ec_lpc_mec_emi_write_address (u16 addr , enum
cros_ec_lpc_mec_emi_access_mode access_type );
like, that's the whole signature. no cap, it returns void β nothing comes back, she just does the thing π«Ά
π ARGUMENTS π
addrβ the starting read / write address π this is where the party beginsaccess_typeβ the type of access, and like, typically it's 32-bit auto-increment π« (that's the vibe, that's the default energy)
π₯ SEE ALSO π₯
- Kernel file
./drivers/platform/chrome/cros_ec_lpc_mec.cβ go read the source, iykyk π cros_ec_lpc_mec_lock(9)cros_ec_lpc_mec_unlock(9)cros_ec_lpc_mec_in_range(9)cros_ec_lpc_io_bytes_mec(9)
the whole friend group fr fr π
ngl this page is short but she ate β memorize the args and you're golden π
and that's a wrap, bestie!! π this lil beauty lives over in ./drivers/platform/chrome, it's dated October 2026, and it's sitting pretty in the Kernel API Manual β mwah πβ¨π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms