Skip to contentSkip to conversation

arm64: defconfig: make TPS6594 support build-in

PATCH In review Michael Walle 2 participants 6 messages Nov 20, 2025 – Nov 21, 2025

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 arm64: defconfig: make TPS6594 support build-in

The Kontron SMARC-sAM67 module needs the TPS6594 regulator driver to boot from SD card, i.e. for its root filesystem.

---
Arnd, the PR from TI [1] (which contains the device trees for this board) is already out, so I'm sending this to the soc ML directly. Let me know if this can still be applied, if not, I'll have to wait for the next window.

[1] https://lore.kernel.org/linux-arm-kernel/[email protected]/

 arch/arm64/configs/defconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/configs/defconfig +1 -1
index f8bcae89c260..e29a41c54b8f 100644
@@ -824,7 +824,7 @@ CONFIG_RZ_MTU3=y
 CONFIG_MFD_TI_AM335X_TSCADC=m
 CONFIG_MFD_TI_LP873X=m
 CONFIG_MFD_TPS65219=y
-CONFIG_MFD_TPS6594_I2C=m
+CONFIG_MFD_TPS6594_I2C=y
 CONFIG_MFD_ROHM_BD718XX=y
 CONFIG_MFD_STM32_LPTIMER=m
 CONFIG_MFD_STM32_TIMERS=m
Signature · 1 line
2.47.3
#1 lore raw
Quoted 10 lines · Michael Walle

The Kontron SMARC-sAM67 module needs the TPS6594 regulator driver to boot from SD card, i.e. for its root filesystem.

---
Arnd, the PR from TI [1] (which contains the device trees for this board) is already out, so I'm sending this to the soc ML directly. Let me know if this can still be applied, if not, I'll have to wait for the next window.

Why it cannot go via TI tree? It should...

Best regards,
Krzysztof

#2 lore raw
Quoted 12 lines · Krzysztof Kozlowski
Quoted 10 lines · Michael Walle

The Kontron SMARC-sAM67 module needs the TPS6594 regulator driver to boot from SD card, i.e. for its root filesystem.

---
Arnd, the PR from TI [1] (which contains the device trees for this board) is already out, so I'm sending this to the soc ML directly. Let me know if this can still be applied, if not, I'll have to wait for the next window.

Quoted 1 line

Why it cannot go via TI tree? It should...

As explained above it can of course, but I've missed the time window as the PR from the TI tree to the soc tree was already sent out.

For why I'm sending this to the soc ML, Arnd once told me to send defconfig changes to the soc ML (commit 066f5f4c7967 for example).

-michael

#3 lore raw
Quoted 13 lines · Michael Walle
Quoted 12 lines · Krzysztof Kozlowski
Quoted 10 lines · Michael Walle

The Kontron SMARC-sAM67 module needs the TPS6594 regulator driver to boot from SD card, i.e. for its root filesystem.

---
Arnd, the PR from TI [1] (which contains the device trees for this board) is already out, so I'm sending this to the soc ML directly. Let me know if this can still be applied, if not, I'll have to wait for the next window.

Quoted 4 lines
Quoted 1 line

Why it cannot go via TI tree? It should...

As explained above it can of course, but I've missed the time window as the PR from the TI tree to the soc tree was already sent out.

This alone would justify for anyone to send directly to soc@ when they miss their upstream maintainer timeframes, so sorry, but that's the way. Time window in TI can still take it. If they cannot, then for sure soc@ cannot, because soc@ takes from TI.

Best regards,
Krzysztof

#4 lore raw
Quoted 14 lines · Krzysztof Kozlowski
Quoted 13 lines · Michael Walle
Quoted 12 lines · Krzysztof Kozlowski
Quoted 10 lines · Michael Walle

The Kontron SMARC-sAM67 module needs the TPS6594 regulator driver to boot from SD card, i.e. for its root filesystem.

---
Arnd, the PR from TI [1] (which contains the device trees for this board) is already out, so I'm sending this to the soc ML directly. Let me know if this can still be applied, if not, I'll have to wait for the next window.

Quoted 7 lines
Quoted 4 lines
Quoted 1 line

Why it cannot go via TI tree? It should...

As explained above it can of course, but I've missed the time window as the PR from the TI tree to the soc tree was already sent out.

This alone would justify for anyone to send directly to soc@ when they miss their upstream maintainer timeframes, so sorry, but that's the way.

Fair point. Sorry for the noise.

-michael

Quoted 5 lines

Time window in TI can still take it. If they cannot, then for sure soc@ cannot, because soc@ takes from TI.

Best regards,
Krzysztof

#5 lore raw
In reply to Michael Walle
Quoted 3 lines · Michael Walle

For why I'm sending this to the soc ML, Arnd once told me to send defconfig changes to the soc ML (commit 066f5f4c7967 for example).

That's a non-platform specific patch, so a completely different rule. Which SoC tree would take it? None. So your only chances was via soc@. Which SoC tree should take TI-related patch? TI.

Best regards,
Krzysztof