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

Signed-off-by: Michael Walle <mwalle@kernel.org>
---
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/a07364c1-5a4c-474f-be21-96f38bfe9130@ti.com/

 arch/arm64/configs/defconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index f8bcae89c260..e29a41c54b8f 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -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
-- 
2.47.3

On 20/11/2025 08:55, Michael Walle wrote:
> The Kontron SMARC-sAM67 module needs the TPS6594 regulator driver to
> boot from SD card, i.e. for its root filesystem.
> 
> Signed-off-by: Michael Walle <mwalle@kernel.org>
> ---
> 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

On Thu Nov 20, 2025 at 2:51 PM CET, Krzysztof Kozlowski wrote:
> On 20/11/2025 08:55, Michael Walle wrote:
>> The Kontron SMARC-sAM67 module needs the TPS6594 regulator driver to
>> boot from SD card, i.e. for its root filesystem.
>> 
>> Signed-off-by: Michael Walle <mwalle@kernel.org>
>> ---
>> 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...

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

On 21/11/2025 08:42, Michael Walle wrote:
> 
> 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

On 21/11/2025 08:42, Michael Walle wrote:
> On Thu Nov 20, 2025 at 2:51 PM CET, Krzysztof Kozlowski wrote:
>> On 20/11/2025 08:55, Michael Walle wrote:
>>> The Kontron SMARC-sAM67 module needs the TPS6594 regulator driver to
>>> boot from SD card, i.e. for its root filesystem.
>>>
>>> Signed-off-by: Michael Walle <mwalle@kernel.org>
>>> ---
>>> 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...
> 
> 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

On Fri Nov 21, 2025 at 9:10 AM CET, Krzysztof Kozlowski wrote:
> On 21/11/2025 08:42, Michael Walle wrote:
>> On Thu Nov 20, 2025 at 2:51 PM CET, Krzysztof Kozlowski wrote:
>>> On 20/11/2025 08:55, Michael Walle wrote:
>>>> The Kontron SMARC-sAM67 module needs the TPS6594 regulator driver to
>>>> boot from SD card, i.e. for its root filesystem.
>>>>
>>>> Signed-off-by: Michael Walle <mwalle@kernel.org>
>>>> ---
>>>> 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...
>> 
>> 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

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