From: eduardo.valentin@ti•com (Eduardo Valentin)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCHv3 5/6] arm: omap2plus_defconfig: enable TI bandgap driver
Date: Mon, 24 Jun 2013 17:39:29 -0400 [thread overview]
Message-ID: <51C8BC91.6020707@ti.com> (raw)
In-Reply-To: <51C0C2A8.4020707@ti.com>
Tony,
On 18-06-2013 16:27, Eduardo Valentin wrote:
> Tony,
>
> On 07-06-2013 16:46, Eduardo Valentin wrote:
>> Enable the bandgap driver for TI SoCs thermal support.
>>
>> Cc: Russell King <linux@arm•linux.org.uk>
>> Cc: Tony Lindgren <tony@atomide•com>
>> Cc: Javier Martinez Canillas <javier.martinez@collabora•co.uk>
>> Cc: AnilKumar Ch <anilkumar@ti•com>
>> Cc: Santosh Shilimkar <santosh.shilimkar@ti•com>
>> Cc: Tomi Valkeinen <tomi.valkeinen@ti•com>
>> Cc: linux-arm-kernel at lists.infradead.org
>> Cc: linux-kernel at vger.kernel.org
>> Signed-off-by: Eduardo Valentin <eduardo.valentin@ti•com>
>
> Is it possible for you to queue this one and patch 6 for 3.11?
Gentle reminder.
>
> Cheers,
>
>> ---
>> arch/arm/configs/omap2plus_defconfig | 11 +++++++++++
>> 1 file changed, 11 insertions(+)
>>
>> diff --git a/arch/arm/configs/omap2plus_defconfig b/arch/arm/configs/omap2plus_defconfig
>> index c1ef64b..6e6c494 100644
>> --- a/arch/arm/configs/omap2plus_defconfig
>> +++ b/arch/arm/configs/omap2plus_defconfig
>> @@ -151,6 +151,13 @@ CONFIG_W1=y
>> CONFIG_POWER_SUPPLY=y
>> CONFIG_SENSORS_LM75=m
>> CONFIG_WATCHDOG=y
>> +CONFIG_THERMAL=y
>> +CONFIG_THERMAL_HWMON=y
>> +CONFIG_THERMAL_DEFAULT_GOV_STEP_WISE=y
>> +CONFIG_THERMAL_GOV_FAIR_SHARE=y
>> +CONFIG_THERMAL_GOV_STEP_WISE=y
>> +CONFIG_THERMAL_GOV_USER_SPACE=y
>> +CONFIG_CPU_THERMAL=y
>> CONFIG_OMAP_WATCHDOG=y
>> CONFIG_TWL4030_WATCHDOG=y
>> CONFIG_MFD_TPS65217=y
>> @@ -237,6 +244,10 @@ CONFIG_RTC_DRV_TWL4030=y
>> CONFIG_RTC_DRV_OMAP=y
>> CONFIG_DMADEVICES=y
>> CONFIG_DMA_OMAP=y
>> +CONFIG_TI_SOC_THERMAL=y
>> +CONFIG_TI_THERMAL=y
>> +CONFIG_OMAP4_THERMAL=y
>> +CONFIG_OMAP5_THERMAL=y
>> CONFIG_EXT2_FS=y
>> CONFIG_EXT3_FS=y
>> # CONFIG_EXT3_FS_XATTR is not set
>>
>
>
--
You have got to be excited about what you are doing. (L. Lamport)
Eduardo Valentin
-------------- 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/20130624/66cf164b/attachment.sig>
next prev parent reply other threads:[~2013-06-24 21:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1370637968-23299-1-git-send-email-eduardo.valentin@ti.com>
2013-06-07 20:46 ` [PATCHv3 2/6] arm: introduce config HAS_BANDGAP Eduardo Valentin
2013-06-12 17:07 ` Tony Lindgren
2013-06-18 20:23 ` Eduardo Valentin
2013-06-07 20:46 ` [PATCHv3 3/6] arm: dts: add bandgap entry for OMAP443x devices Eduardo Valentin
2013-06-18 20:14 ` Eduardo Valentin
2013-06-07 20:46 ` [PATCHv3 4/6] arm: dts: add bandgap entry for OMAP4460 devices Eduardo Valentin
2013-06-18 20:16 ` Eduardo Valentin
2013-06-19 1:11 ` Benoit Cousson
2013-06-07 20:46 ` [PATCHv3 5/6] arm: omap2plus_defconfig: enable TI bandgap driver Eduardo Valentin
2013-06-18 20:27 ` Eduardo Valentin
2013-06-24 21:39 ` Eduardo Valentin [this message]
2013-07-04 11:48 ` Tony Lindgren
2013-06-07 20:46 ` [PATCHv3 6/6] arm: omap2plus_defconfig: enable DRA752 thermal support by default 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=51C8BC91.6020707@ti.com \
--to=eduardo.valentin@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox