linux-kernel - Re: [PATCH] arm64: defconfig: make TPS6594 support build-in

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c55c87ea-01a1-4200-8fed-e629d7d068ec@kernel.org>
Date: Fri, 21 Nov 2025 09:10:04 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Michael Walle <mwalle@...nel.org>, Arnd Bergmann <arnd@...db.de>
Cc: soc@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: defconfig: make TPS6594 support build-in

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@...nel.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