diff options
| author | Mark Brown <broonie@kernel.org> | 2026-09-25 18:44:47 +0100 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2026-09-25 18:44:47 +0100 |
| commit | 9048d2416b0923e88c07db585fd47034c6b95dad (patch) | |
| tree | 0e67e482ea6dad8d47bbe40f8ca06e343fb08301 /include/linux/mfd | |
| parent | b9205f0837ca91a0bbe6aa9002207656840c1406 (diff) | |
| parent | 59951bd9c6b63d4d98539db96becef729ad60b4a (diff) | |
regulator: Allow mtk-regulator-coupler to be built as a module
Justin Yeh <justin.yeh@mediatek.com> says:
MTK_REGULATOR_COUPLER can currently only be built into the kernel: it is
a bool, and its prompt is hidden unless COMPILE_TEST is set, so on real
MediaTek configurations the symbol has no prompt and is forced to its
"default ARCH_MEDIATEK" value.
Kernels that ship nearly everything as a module (Android GKI style
kernels, but distro kernels have the same shape) cannot use it that way.
Two things are in the way:
- the four helpers the coupler calls are declared in
include/linux/regulator/coupler.h for coupler implementations to
use, but none of them is exported (patch 1);
- the Kconfig symbol is a bool without a usable prompt (patch 2).
Link: https://patch.msgid.link/20260903062056.1024263-1-justin.yeh@mediatek.com
Diffstat (limited to 'include/linux/mfd')
0 files changed, 0 insertions, 0 deletions