regcache_sync(9)
π NAME π
regcache_sync β sync the register cache with the hardware. This is the regcache_sync(9) page from the Kernel API Manual, and bestie, we are getting into it. π«Ά
β¨ SYNOPSIS β¨
int regcache_sync (struct regmap *map );
π ARGUMENTS π
mapβ map to configure. π
πΈ DESCRIPTION πΈ
Okay so first thing: any registers that should not be synced should be marked as volatile. That's the move. β¨
In general, drivers can choose not to use the provided syncing functionality if they so require. No pressure β literally optional vibes.
This pushes cached changes made while cache_only (e.g. suspend) down to hardware. Think of it as sending the group-chat drafts to the actual hardware. π
The caller must disable cache_only before calling this function. π¨ Like, do that first, bestie β it's giving prerequisites.
Return a negative value on failure, 0 on success. That's the whole mood. π
π¦ SEE ALSO π¦
- Kernel file
./drivers/base/regmap/regcache.c regcache_read(9)regcache_write(9)regcache_sync_region(9)regcache_drop_region(9)regcache_cache_only(9)regcache_mark_dirty(9)regcache_cache_bypass(9)regcache_reg_cached(9)
Sign-off time: source/version ./drivers/base/regmap, date October 2026, page regcache_sync(9) β periodt. ππ§
π¦ 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