Skip to contentSkip to conversation

ram: Move Kconfig options into their own menu entry

PATCH In review Yao Zi 3 participants 4 messages Jun 2, 2025 – Jun 12, 2025

lore
Share & tools
lore

Yao Zi

author
#0 lore raw

PATCH 1/1 ram: Move Kconfig options into their own menu entry

RAM drivers using Device Model currently lack of their own Kconfig menu entry, which makes Kconfig put all options of the class in the top-level menu of device drivers. These options are also incorrectly grouped with pinctrl options in the generated .config, which is hard to read. Let's create a menu entry for these drivers.

Fixes 6c51df6859f ("dm: Add support for RAM drivers")
---
 drivers/ram/Kconfig | 4 ++++
 1 file changed, 4 insertions(+)
drivers/ram/Kconfig +4 -0
index 39d03e8d3d3..edb8e254d5b 100644
@@ -1,3 +1,5 @@
+menu "RAM drivers using Driver Model"
+
 config RAM
 	bool "Enable RAM drivers using Driver Model"
 	depends on DM
@@ -136,3 +138,5 @@ source "drivers/ram/stm32mp1/Kconfig"
 source "drivers/ram/starfive/Kconfig"
 source "drivers/ram/sunxi/Kconfig"
 source "drivers/ram/thead/Kconfig"
+
+endmenu
Signature · 1 line
2.49.0
Reviewed-by on v1 1/1
#1 lore raw

Hi Yao Zi,

Quoted 8 lines · Yao Zi

RAM drivers using Device Model currently lack of their own Kconfig menu entry, which makes Kconfig put all options of the class in the top-level menu of device drivers. These options are also incorrectly grouped with pinctrl options in the generated .config, which is hard to read. Let's create a menu entry for these drivers.

Fixes 6c51df6859f ("dm: Add support for RAM drivers")

drivers/ram/Kconfig line 2

Quoted 11 lines
---
  drivers/ram/Kconfig | 4 ++++
  1 file changed, 4 insertions(+)
drivers/ram/Kconfig +2 -0
index 39d03e8d3d3..edb8e254d5b 100644
@@ -1,3 +1,5 @@
+menu "RAM drivers using Driver Model"
+

Considering SPL_RAM, TPL_RAM and VPL_RAM all depend on RAM, you could also go the same route as AXI and have:

menuconfig RAM

drivers/ram/Kconfig line 5

Quoted 2 lines
drivers/ram/Kconfig +0 -0
  	bool "Enable RAM drivers using Driver Model"
  	depends on DM

[...]

if RAM

drivers/ram/Kconfig source "drivers/ram/stm32mp1/Kconfig" · line 140

Quoted 4 lines
drivers/ram/Kconfig +0 -0
@@ -136,3 +138,5 @@ source "drivers/ram/stm32mp1/Kconfig"
  source "drivers/ram/starfive/Kconfig"
  source "drivers/ram/sunxi/Kconfig"
  source "drivers/ram/thead/Kconfig"

endif

Up to you :)

Cheers,
Quentin

Reviewed-by on v1 1/1
#2 lore raw
In reply to Yao Zi
Quoted 8 lines · Yao Zi

RAM drivers using Device Model currently lack of their own Kconfig menu entry, which makes Kconfig put all options of the class in the top-level menu of device drivers. These options are also incorrectly grouped with pinctrl options in the generated .config, which is hard to read. Let's create a menu entry for these drivers.

Fixes 6c51df6859f ("dm: Add support for RAM drivers")
Signature · 1 line
Tom
#3 lore raw
In reply to Yao Zi
Quoted 8 lines · Yao Zi

RAM drivers using Device Model currently lack of their own Kconfig menu entry, which makes Kconfig put all options of the class in the top-level menu of device drivers. These options are also incorrectly grouped with pinctrl options in the generated .config, which is hard to read. Let's create a menu entry for these drivers.

[...]

Applied to u-boot/next, thanks!

[1/1] ram: Move Kconfig options into their own menu entry

      commit: 548d997229b7929bd7f0782415952d5a85eb7e64
Signature · 1 line
Tom