Bug 1218133

Summary:	enable regulator modules (REGULATOR_MT6323, REGULATOR_MT6380, MFD_MT6397)
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Bob Goddard <opensuse>
Component:	Kernel	Assignee:	openSUSE Kernel Bugs <kernel-bugs>
Status:	NEW ---	QA Contact:	E-mail List <qa-bugs>
Severity:	Enhancement
Priority:	P5 - None	CC:	andrea.porta, ivan.ivanov, opensuse, stanimir.varbanov, tiwai
Version:	Current	Flags:	ivan.ivanov: needinfo? (opensuse)
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Bob Goddard 2023-12-16 22:40:21 UTC

There are quite a number of regulator modules not being built.

Some of these at least depend on the multifunction device drivers.

I am looking to get tumbleweed up and running on the BananaPi-R3, and perhaps the new BananaPi-R4 in the future.

This needs REGULATOR_MT6323 enabled, at least as a module, and it depend on MFD_MT6397.

There seems to be an awful lot of regulators not being build, mainly because the multi function devices have not been selected.

As many of these can be built as modules, can these all be enables? As in all the PMICs?

Comment 1 Bob Goddard 2023-12-18 13:35:10 UTC

And also REGULATOR_MT6380.

I think it would be better to enable them all if they can be build as modules.

Comment 2 Takashi Iwai 2024-01-02 16:51:28 UTC

It'd be appreciated if you can list up the all missing entries to be set, e.g. give a diff of kconfig.

Comment 3 Bob Goddard 2024-01-05 13:31:54 UTC

I'm not completely correct in what may be required.

Seems like the following need to be built into the kernel and not as modules. I'm still dissecting. Trying to find the correct order the modules get loaded without generating a kernel oops is proving difficult. Could be anothee couple of weeks before I get what needs to be build & what the load order is of any modules.

CONFIG_AQUANTIA_PHY
CONFIG_ARM_MEDIATEK_CPUFREQ
CONFIG_BRIDGE
CONFIG_COMMON_CLK_MT7981_ETHSYS
CONFIG_CPU_FREQ_GOV_USERSPACE
CONFIG_I2C_MT65XX
CONFIG_ICPLUS_PHY
CONFIG_LLC
CONFIG_MEDIATEK_GE_PHY
CONFIG_MEDIATEK_WATCHDOG
CONFIG_MTK_HSDMA
CONFIG_MTK_MMSYS
CONFIG_MTK_PMIC_WRAP
CONFIG_NET_DSA
CONFIG_NET_DSA_MT7530
CONFIG_NET_DSA_MT7530_MDIO
CONFIG_NET_DSA_MT7530_MMIO
CONFIG_NET_DSA_TAG_MTK
CONFIG_NET_MEDIATEK_SOC
CONFIG_PCIE_MEDIATEK_GEN3
CONFIG_PCS_MTK_LYNXI
CONFIG_PHYLINK
CONFIG_PHY_MTK_TPHY
CONFIG_REALTEK_PHY
CONFIG_REGULATOR_FIXED_VOLTAGE
CONFIG_REGULATOR_MT6380
CONFIG_RFKILL
CONFIG_STP

Comment 4 Takashi Iwai 2024-01-08 15:26:36 UTC

We really want to avoid built-in unless they have to be, especially if those are device-specific drivers, not the core stuff.

e.g. why the network drivers have to be built-in at all...?

Comment 5 Ivan Ivanov 2024-05-15 12:03:18 UTC

Bob Goddard, could you check last question from Takashy?