mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Daniel Lezcano <daniel.lezcano@kernel.org>,
	Zhang Rui <rui.zhang@intel.com>,
	Lukasz Luba <lukasz.luba@arm.com>,
	linux-pm@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] thermal: samsung: Enable TMU by default
Date: Tue, 26 May 2026 18:17:59 +0200	[thread overview]
Message-ID: <b20c560f-4bc3-4686-9c91-36d93f1535b2@oss.qualcomm.com> (raw)
In-Reply-To: <20260526135312.8697-2-krzysztof.kozlowski@oss.qualcomm.com>

On 5/26/26 15:53, Krzysztof Kozlowski wrote:
> The SoC Thermal Management Unit (TMU) is essential for proper operation
> of the SoCs.  Kernel should not ask users choice of drivers when that
> choice is obvious and known to the developers that answer should be
> 'yes' or 'module'.
> 
> Impact of making it default:
> 
> 1. arm64 defconfig: No changes, already present in defconfig.
> 
> 2. arm32: No changes, the driver is already selected by MACH_EXYNOS.
> 
> 3. COMPILE_TEST builds: enable by default for arm32 or arm64 builds,
>     whenever ARCH_EXYNOS is selected.  This has impact on build time and
>     feels logical, because if one selects ARCH_EXYNOS then probably by
>     default wants to build test it entirely.  Kernels with COMPILE_TEST
>     are not supposed to be used for booting.
> 
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> ---

Applied, thanks

      reply	other threads:[~2026-05-26 16:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26 13:53 Krzysztof Kozlowski
2026-05-26 16:17 ` Daniel Lezcano [this message]

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=b20c560f-4bc3-4686-9c91-36d93f1535b2@oss.qualcomm.com \
    --to=daniel.lezcano@oss.qualcomm.com \
    --cc=bzolnier@gmail.com \
    --cc=daniel.lezcano@kernel.org \
    --cc=krzk@kernel.org \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@intel.com \
    /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

all inboxes | Powered by JetHome®