[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <vxqi23hxw7bmtfs5wk3u7szganpv5aa74b26xrvpmbehkltodw@dpum7zrxdz44>
Date: Fri, 6 Dec 2024 14:28:11 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: Tudor Ambarus <tudor.ambarus@...aro.org>, robh@...nel.org,
krzk+dt@...nel.org, conor+dt@...nel.org, alim.akhtar@...sung.com,
linux-kernel@...r.kernel.org, linux-samsung-soc@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, andre.draszik@...aro.org, kernel-team@...roid.com,
willmcvicker@...gle.com, peter.griffin@...aro.org, javierm@...hat.com,
tzimmermann@...e.de, vincent.guittot@...aro.org, ulf.hansson@...aro.org,
arnd@...db.de
Subject: Re: [PATCH v3 2/3] firmware: add exynos ACPM protocol driver
On Fri, Dec 06, 2024 at 12:39:56AM +0100, Daniel Lezcano wrote:
> > +# SPDX-License-Identifier: GPL-2.0-only
> > +
> > +config EXYNOS_ACPM_PROTOCOL
> > + tristate "Exynos Alive Clock and Power Manager (ACPM) Message Protocol"
>
> Given the importance of this driver where a lot of PM services rely on, does
> it really make sense to allow it as a module ?
>
> Some PM services may be needed very early in the boot process
>
If it works as module e.g. on Android, it is beneficial. I think the
platform was booting fine without it, at least to some shell, so I can
imagine this can be loaded a bit later.
Best regards,
Krzysztof
Powered by blists - more mailing lists