[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160329163649.GE14322@vireshk-i7>
Date: Tue, 29 Mar 2016 22:06:49 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: linaro-kernel@...ts.linaro.org, k.kozlowski@...sung.com,
kgene.kim@...sung.com, heiko@...ech.de, xf@...k-chips.com,
linux-pm@...r.kernel.org, Rafael Wysocki <rjw@...ysocki.net>,
linux-kernel@...r.kernel.org, mmcclint@...eaurora.org
Subject: Re: [PATCH V1 Resend 2/3] cpufreq: dt: Add generic platform-device
creation support
On 29-03-16, 17:14, Arnd Bergmann wrote:
> On Tuesday 29 March 2016 12:09:48 Viresh Kumar wrote:
> > +config CPUFREQ_DT_PLATDEV
> > + bool
> > + depends on CPUFREQ_DT
>
> The 'depends on' line is redundant as you always 'select' the code
> from CPUFREQ_DT. Since they are always set together, you can also
> just drop the new symbol, or put the new code into the same file.
I would like to keep a separate file for this, it looks awkward to update the
driver for any new user platform.
I added a separate symbol to take care of the Modular case of cpufreq-dt. i.e. I
didn't wanted to add module_exit() code in the new file. Currently, it gets
included in the kernel even if cpufreq-dt is selected as a Module, so we just
create the platform-device just once and never touch it again.
--
viresh
Powered by blists - more mailing lists