[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5188FE54.6050200@ti.com>
Date: Tue, 7 May 2013 09:15:00 -0400
From: Eduardo Valentin <eduardo.valentin@...com>
To: Jason Gunthorpe <jgunthorpe@...idianresearch.com>
CC: Eduardo Valentin <eduardo.valentin@...com>,
Aaro Koskinen <aaro.koskinen@....fi>, <tony@...mide.com>,
<linux-omap@...r.kernel.org>,
Russell King <linux@....linux.org.uk>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [RESEND][PATCH 1/3] arm: dts: introduce config HAS_BANDGAP
Hello Jason,
On 06-05-2013 20:36, Jason Gunthorpe wrote:
> On Mon, May 06, 2013 at 08:23:13PM -0400, Eduardo Valentin wrote:
>
>>> I get the impression it is desired to minimize driver kconfig
>>> dependencies to the minimum required to compile to increase build
>>> testing coverage, so maybe it would be appropriate to drop this
>>> entirely?
>
>> Well, it is also desired to compile things to the correct target
>> right?
>
> There is some of that too..
>
> But broadly the direction seems that drivers should have minimal
> dependencies so, eg, the thermal maintainer compiling for x86 should
> be able to compile test/static analyze your driver..
>
Well, I do not see much of this attempt actually. Do you have some link
/ evidene that shows someone who actually cares about compiling drivers
for targets that they are not used for? On this specific driver, I
actually have had exactly the opposite advice [1]. I am not convinced
people actually want to do that.
>> Thats the idea behind this config option. It follows the same design as
>> CONFIG_ARCH_HAS_CPUFREQ, for instance.
>
> That is entirely contained inside arch/arm and doesn't involve
> drivers.
It actually goes outside arch/arm.
>
> Jason
>
>
[1] - https://patchwork.kernel.org/patch/1185431/
Download attachment "signature.asc" of type "application/pgp-signature" (296 bytes)
Powered by blists - more mailing lists