exynos5_dmc_...pass_voltage(9)
π NAME π
exynos5_dmc_align_bypass_voltage β okay so this one sets the voltage for the DMC β¨ (yes, that's the whole name, and yes we're saying it with our whole chest)
Quick vibe check first: this page lives in the Kernel API Manual (that's the manual name bestie, noting it here instead of doing the boring header-line thing π), and the function itself goes by exynos5_dmc_align_bypass_voltage. The page title got a lil truncated to exynos5_dmc_...pass_voltage(9) which is honestly giving "my name got cut off in the group chat" π but we move.
β¨ SYNOPSIS β¨
int exynos5_dmc_align_bypass_voltage (struct exynos5_dmc *dmc , unsigned
long target_volt );
Like, it returns an int, it takes a struct exynos5_dmc * and an unsigned long, and that's the whole menu π
π«Ά ARGUMENTS π«Ά
dmcβ the device we're setting this voltage for, aka the one getting the glow-up πtarget_voltβ the new voltage that's been chosen to be the final one, periodt. This is the destination, no layovers βοΈ
π¦ DESCRIPTION π¦
Okay so picture this: the function tries to align the voltage to the safe level for the 'bypass' mode πΈ. It checks whether a higher voltage is actually needed, and then it changes the value accordingly. Lowkey the responsible friend of the group, ngl.
β οΈ Bestie, listen: the target voltage must not be less than currently needed, because for the current frequency the device might become unstable π That's not a vibe. That's the opposite of a vibe. Do not do that. π
It's giving "let me make sure you're safe before you go out" energy and honestly? Iconic.
π SEE ALSO π
The whole squad, in the order they showed up π«Ά:
Kernel file ./drivers/memory/samsung/exynos5422-dmc.cstruct dmc_opp_table(9)struct exynos5_dmc(9)find_target_freq_idx(9)exynos5_switch_timing_regs(9)exynos5_init_freq_table(9)exynos5_set_bypass_dram_timings(9)exynos5_dram_change_timings(9)exynos5_dmc_align_target_voltage(9)exynos5_dmc_align_bypass_dram_timings(9)exynos5_dmc_switch_to_bypass_configuration(9)exynos5_dmc_change_freq_and_volt(9)exynos5_dmc_get_volt_freq(9)exynos5_dmc_target(9)exynos5_counters_get(9)exynos5_dmc_start_perf_events(9)exynos5_dmc_perf_events_calc(9)exynos5_dmc_perf_events_check(9)exynos5_dmc_enable_perf_events(9)exynos5_dmc_disable_perf_events(9)exynos5_dmc_get_status(9)exynos5_dmc_get_cur_freq(9)exynos5_dmc_align_init_freq(9)create_timings_aligned(9)of_get_dram_timings(9)exynos5_dmc_init_clks(9)exynos5_performance_counters_init(9)exynos5_dmc_set_pause_on_switching(9)exynos5_dmc_probe(9)exynos5_dmc_remove(9)
and that's the whole page bestie, go forth and align those voltages responsibly π
Cute lil sign-off: this one's sourced from ./drivers/memory/samsung, dated October 2026, under the exynos5_dmc_...pass_voltage(9) header, living its best life in the Kernel API Manual πβ¨ iykyk
π¦ 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