linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Valentin <eduardo.valentin@ti.com>
To: tony@atomide.com, grant.likely@linaro.org
Cc: linux-pm@vger.kernel.org, linux-omap@vger.kernel.org,
	linux@arm.linux.org.uk,
	Eduardo Valentin <eduardo.valentin@ti.com>
Subject: [PATCHv3 0/6] arm: enable TI SoC thermal driver
Date: Fri, 7 Jun 2013 16:46:02 -0400	[thread overview]
Message-ID: <1370637968-23299-1-git-send-email-eduardo.valentin@ti.com> (raw)

Hello,

Idea is to add the missing bits under arch/arm/*omap* required
to enable by default the ti-soc-thermal driver. I am planing to
move it out of staging tree. This has been scheduled to 3.11.

It would be interesting to get
feedback from other ppl. By enabling it by default we could reach
more ppl for testing it across the supported chips.

The difference from v2 is that now the driver is changed to use
GPIO bindings for Tshut as suggested by Benoit and I added
a simple description what is bandgap.

The difference from v1 is just that patch 01 doe snot include the
dts prefix, as it is not supposed to be DTS related.


Eduardo Valentin (6):
  thermal: ti-soc-thermal: use standard GPIO DT bindings
  arm: introduce config HAS_BANDGAP
  arm: dts: add bandgap entry for OMAP443x devices
  arm: dts: add bandgap entry for OMAP4460 devices
  arm: omap2plus_defconfig: enable TI bandgap driver
  arm: omap2plus_defconfig: enable DRA752 thermal support by default

 arch/arm/Kconfig                                  |  3 +++
 arch/arm/boot/dts/omap443x.dtsi                   |  4 ++++
 arch/arm/boot/dts/omap4460.dtsi                   |  9 +++++++++
 arch/arm/configs/omap2plus_defconfig              | 12 ++++++++++++
 arch/arm/mach-omap2/Kconfig                       |  1 +
 drivers/staging/ti-soc-thermal/ti-bandgap.c       |  8 ++------
 drivers/staging/ti-soc-thermal/ti_soc_thermal.txt |  9 +++++----
 7 files changed, 36 insertions(+), 10 deletions(-)

-- 
1.8.2.1.342.gfa7285d


             reply	other threads:[~2013-06-07 20:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-07 20:46 Eduardo Valentin [this message]
2013-06-07 20:46 ` [PATCHv3 1/6] thermal: ti-soc-thermal: use standard GPIO DT bindings Eduardo Valentin
2013-06-19  2:28   ` [PATCHv4 " Eduardo Valentin
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
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=1370637968-23299-1-git-send-email-eduardo.valentin@ti.com \
    --to=eduardo.valentin@ti.com \
    --cc=grant.likely@linaro.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).