[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160407165355.GA9188@linaro.org>
Date: Thu, 7 Apr 2016 17:53:55 +0100
From: Daniel Lezcano <daniel.lezcano@...aro.org>
To: rcochran@...utronix.de
Cc: "Brown, Len" <len.brown@...el.com>,
"Gortmaker, Paul (Wind River)" <paul.gortmaker@...driver.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Len Brown <lenb@...nel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>
Subject: Re: [PATCH] drivers/idle: make intel_idle.c driver more explicitly
non-modular
On Tue, Apr 05, 2016 at 09:33:12AM +0200, rcochran@...utronix.de wrote:
> On Tue, Apr 05, 2016 at 05:53:47AM +0000, Brown, Len wrote:
> > > On Tue, Apr 05, 2016 at 04:20:47AM +0000, Brown, Len wrote:
> > > > No, I do not believe that cpuidle should bother
> > > > supporting changing idle drivers at run-time.
> > >
> > > Huh? But you just said, "it would be good to be able to unload it
> > > when it doesn't probe."
> >
> > being able to switch the registered driver at run-time
> > does not require the driver to be modular.
>
> Uh, right, but you don't think that the cpuidle core should allow
> changing drivers. If it doesn't allowing changing drivers, then there
> would be just one choice, compiled in, and thus none of the drivers
> should be modular.
Actually, the modular support has been removed from almost all the cpuidle
drivers and the cpuidle framework is no longer assuming driver could
be unloaded.
The cpuidle drivers are very arch/platform specific and the acpi vs
something is an exception and could be handled differently than
converting to modular again.
I don't see the point on removing a cpuidle driver at runtime to
something else.
Removing the modular dead code in the driver makes sense as this
what have been done in the others drivers.
-- Daniel
Powered by blists - more mailing lists