From: Eduardo Valentin <eduardo.valentin@ti.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: Russell King <linux@arm.linux.org.uk>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
tony@atomide.com, linux-kernel@vger.kernel.org,
Eduardo Valentin <eduardo.valentin@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [RESEND][PATCH 1/3] arm: dts: introduce config HAS_BANDGAP
Date: Mon, 6 May 2013 20:23:13 -0400 [thread overview]
Message-ID: <51884971.9050508@ti.com> (raw)
In-Reply-To: <20130506223653.GA12089@obsidianresearch.com>
[-- Attachment #1.1: Type: text/plain, Size: 1186 bytes --]
On 06-05-2013 18:36, Jason Gunthorpe wrote:
> On Tue, May 07, 2013 at 12:34:13AM +0300, Aaro Koskinen wrote:
>> On Mon, May 06, 2013 at 05:00:56PM -0400, Eduardo Valentin wrote:
>>> Introduce HAS_BANDGAP config entry. This config is a
>>> boolean value so that arch code can flag is they
>>> feature a bandgap device.
>>
>> Maybe it could be mentioned that omap-thermal already depend on this?
>> At least for a random reviewer it was not immediately clear why this is
>> added, especially since there were no users for it in subsequent patches.
>
> I looked (very briefly), and it seemed like omap-thermal is self
> contained and doesn't need arch support?
>
It is. At least I tried to make it, at least to the extenstion I could get.
> 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?
Thats the idea behind this config option. It follows the same design as
CONFIG_ARCH_HAS_CPUFREQ, for instance.
> Jason
>
>
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 295 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: eduardo.valentin@ti.com (Eduardo Valentin)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND][PATCH 1/3] arm: dts: introduce config HAS_BANDGAP
Date: Mon, 6 May 2013 20:23:13 -0400 [thread overview]
Message-ID: <51884971.9050508@ti.com> (raw)
In-Reply-To: <20130506223653.GA12089@obsidianresearch.com>
On 06-05-2013 18:36, Jason Gunthorpe wrote:
> On Tue, May 07, 2013 at 12:34:13AM +0300, Aaro Koskinen wrote:
>> On Mon, May 06, 2013 at 05:00:56PM -0400, Eduardo Valentin wrote:
>>> Introduce HAS_BANDGAP config entry. This config is a
>>> boolean value so that arch code can flag is they
>>> feature a bandgap device.
>>
>> Maybe it could be mentioned that omap-thermal already depend on this?
>> At least for a random reviewer it was not immediately clear why this is
>> added, especially since there were no users for it in subsequent patches.
>
> I looked (very briefly), and it seemed like omap-thermal is self
> contained and doesn't need arch support?
>
It is. At least I tried to make it, at least to the extenstion I could get.
> 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?
Thats the idea behind this config option. It follows the same design as
CONFIG_ARCH_HAS_CPUFREQ, for instance.
> Jason
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 295 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130506/3a925826/attachment-0001.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Eduardo Valentin <eduardo.valentin@ti.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
Eduardo Valentin <eduardo.valentin@ti.com>, <tony@atomide.com>,
<linux-omap@vger.kernel.org>,
Russell King <linux@arm.linux.org.uk>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RESEND][PATCH 1/3] arm: dts: introduce config HAS_BANDGAP
Date: Mon, 6 May 2013 20:23:13 -0400 [thread overview]
Message-ID: <51884971.9050508@ti.com> (raw)
In-Reply-To: <20130506223653.GA12089@obsidianresearch.com>
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
On 06-05-2013 18:36, Jason Gunthorpe wrote:
> On Tue, May 07, 2013 at 12:34:13AM +0300, Aaro Koskinen wrote:
>> On Mon, May 06, 2013 at 05:00:56PM -0400, Eduardo Valentin wrote:
>>> Introduce HAS_BANDGAP config entry. This config is a
>>> boolean value so that arch code can flag is they
>>> feature a bandgap device.
>>
>> Maybe it could be mentioned that omap-thermal already depend on this?
>> At least for a random reviewer it was not immediately clear why this is
>> added, especially since there were no users for it in subsequent patches.
>
> I looked (very briefly), and it seemed like omap-thermal is self
> contained and doesn't need arch support?
>
It is. At least I tried to make it, at least to the extenstion I could get.
> 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?
Thats the idea behind this config option. It follows the same design as
CONFIG_ARCH_HAS_CPUFREQ, for instance.
> Jason
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 295 bytes --]
next prev parent reply other threads:[~2013-05-07 0:23 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 21:00 [RESEND][PATCH 0/3] arm: enable TI SoC thermal driver Eduardo Valentin
2013-05-06 21:00 ` [RESEND][PATCH 1/3] arm: dts: introduce config HAS_BANDGAP Eduardo Valentin
2013-05-06 21:00 ` Eduardo Valentin
2013-05-06 21:00 ` Eduardo Valentin
2013-05-06 21:31 ` Stephen Warren
2013-05-06 21:31 ` Stephen Warren
2013-05-07 0:20 ` Eduardo Valentin
2013-05-07 0:20 ` Eduardo Valentin
2013-05-07 0:20 ` Eduardo Valentin
2013-05-06 21:34 ` Aaro Koskinen
2013-05-06 21:34 ` Aaro Koskinen
2013-05-06 22:36 ` Jason Gunthorpe
2013-05-06 22:36 ` Jason Gunthorpe
2013-05-07 0:23 ` Eduardo Valentin [this message]
2013-05-07 0:23 ` Eduardo Valentin
2013-05-07 0:23 ` Eduardo Valentin
2013-05-07 0:36 ` Jason Gunthorpe
2013-05-07 0:36 ` Jason Gunthorpe
2013-05-07 0:36 ` Jason Gunthorpe
2013-05-07 13:15 ` Eduardo Valentin
2013-05-07 13:15 ` Eduardo Valentin
2013-05-07 13:15 ` Eduardo Valentin
2013-05-07 18:27 ` Jason Gunthorpe
2013-05-07 18:27 ` Jason Gunthorpe
2013-05-07 19:06 ` Aaro Koskinen
2013-05-07 19:06 ` Aaro Koskinen
2013-05-08 6:04 ` Tomi Valkeinen
2013-05-08 6:04 ` Tomi Valkeinen
2013-05-08 6:04 ` Tomi Valkeinen
2013-05-06 22:40 ` Eduardo Valentin
2013-05-06 22:40 ` Eduardo Valentin
2013-05-06 22:40 ` Eduardo Valentin
2013-05-06 21:00 ` [RESEND][PATCH 2/3] arm: dts: add bandgap entry for OMAP443x devices Eduardo Valentin
2013-05-06 21:00 ` Eduardo Valentin
2013-05-06 21:00 ` Eduardo Valentin
2013-05-06 21:00 ` [RESEND][PATCH 3/3] arm: add bandgap entry for OMAP4460 devices Eduardo Valentin
2013-05-06 21:00 ` Eduardo Valentin
2013-05-06 21:00 ` Eduardo Valentin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51884971.9050508@ti.com \
--to=eduardo.valentin@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.