From: "Michael Walle" <mwalle@kernel.org>
To: "Krzysztof Kozlowski" <krzk@kernel.org>, "Arnd Bergmann" <arnd@arndb.de>
Cc: <soc@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: defconfig: make TPS6594 support build-in
Date: Fri, 21 Nov 2025 08:42:20 +0100 [thread overview]
Message-ID: <DEE7CKFYFS69.2R2RADO7WNTFS@kernel.org> (raw)
In-Reply-To: <0d6e055a-d71b-443f-83c8-6365a88ad9b6@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]
next prev parent reply other threads:[~2025-11-21 7:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 7:55 [PATCH] arm64: defconfig: make TPS6594 support build-in Michael Walle
2025-11-20 13:51 ` Krzysztof Kozlowski
2025-11-21 7:42 ` Michael Walle [this message]
2025-11-21 8:10 ` Krzysztof Kozlowski
2025-11-21 9:02 ` Michael Walle
2025-11-21 8:11 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DEE7CKFYFS69.2R2RADO7WNTFS@kernel.org \
--to=mwalle@kernel.org \
--cc=arnd@arndb.de \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox