[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <80dc4e2e0c7e0fc6f224e704b8594c0f12d0afe9.camel@siemens.com>
Date: Thu, 22 Feb 2024 07:55:34 +0000
From: "Sverdlin, Alexander" <alexander.sverdlin@...mens.com>
To: "andrew@...n.ch" <andrew@...n.ch>
CC: "linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>, "sre@...nel.org"
<sre@...nel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RFC] power: reset: restart-poweroff: convert to module
Hi Andrew!
On Wed, 2024-02-21 at 23:37 +0100, Andrew Lunn wrote:
> > The necessity of having a fake platform device for a generic, platform
> > independent functionality is not obvious.
> > Some platforms requre device tree modification for this, some would require
> > ACPI tables modification, while functionality may be useful even to
> > end-users without required expertise. Convert the platform driver to
> > a simple module.
> >
> > Signed-off-by: Alexander Sverdlin <alexander.sverdlin@...mens.com>
> > ---
> > This RFC is merely to understand if this approach would be accepted.
> > Converting to "tristate" could follow or preceed this patch.
>
> So that is you use case here? Why do you want to be able to just load
> this driver, without using DT to indicate it is needed by the
> hardware?
Yes, the code is platform-independent now and can be re-used for deployments
which meant to be "always on". One could actually even use it with
off-the-shelf x86 hardware. But instantiating a platform device there would
be a hack. Why not just control this code in the kernel config?
--
Alexander Sverdlin
Siemens AG
www.siemens.com
Powered by blists - more mailing lists