From: Eduardo Valentin <eduardo.valentin@ti.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: <devel@driverdev.osuosl.org>, <linux-kernel@vger.kernel.org>,
<j-keerthy@ti.com>, <grant.likely@secretlab.ca>,
<b-cousson@ti.com>, <kbaidarov@dev.rtsoft.ru>,
Eduardo Valentin <eduardo.valentin@ti.com>
Subject: [PATCHv2 0/4] staging: adding OMAP bandgap driver
Date: Sat, 7 Jul 2012 10:57:48 +0300 [thread overview]
Message-ID: <1341647872-15267-1-git-send-email-eduardo.valentin@ti.com> (raw)
Greg,
Here is the reworked series with the omap bangap driver and minimalist
thermal framework support. Diff from v1 is simple that now it won't
break compilation. Only change is between patch 1 and patch 2, I have
added the missing and needed Makefile and Kconfig entries in patch 1,
for omap-bandgap.c.
Cheers,
Eduardo Valentin (4):
staging: OMAP4+: thermal: introduce bandgap temperature sensor
staging: omap-thermal: common code to expose driver to thermal
framework
staging: omap-thermal: add OMAP4 data structures
staging: omap-thermal: add OMAP5 data structures
drivers/staging/Kconfig | 2 +
drivers/staging/Makefile | 1 +
drivers/staging/omap-thermal/Kconfig | 45 +
drivers/staging/omap-thermal/Makefile | 5 +
drivers/staging/omap-thermal/TODO | 27 +
drivers/staging/omap-thermal/omap-bandgap.c | 1186 ++++++++++++++++++++
drivers/staging/omap-thermal/omap-bandgap.h | 441 ++++++++
drivers/staging/omap-thermal/omap-thermal-common.c | 397 +++++++
drivers/staging/omap-thermal/omap-thermal.h | 108 ++
drivers/staging/omap-thermal/omap4-thermal.c | 259 +++++
drivers/staging/omap-thermal/omap5-thermal.c | 297 +++++
drivers/staging/omap-thermal/omap_bandgap.txt | 30 +
12 files changed, 2798 insertions(+), 0 deletions(-)
create mode 100644 drivers/staging/omap-thermal/Kconfig
create mode 100644 drivers/staging/omap-thermal/Makefile
create mode 100644 drivers/staging/omap-thermal/TODO
create mode 100644 drivers/staging/omap-thermal/omap-bandgap.c
create mode 100644 drivers/staging/omap-thermal/omap-bandgap.h
create mode 100644 drivers/staging/omap-thermal/omap-thermal-common.c
create mode 100644 drivers/staging/omap-thermal/omap-thermal.h
create mode 100644 drivers/staging/omap-thermal/omap4-thermal.c
create mode 100644 drivers/staging/omap-thermal/omap5-thermal.c
create mode 100644 drivers/staging/omap-thermal/omap_bandgap.txt
--
1.7.7.1.488.ge8e1c
next reply other threads:[~2012-07-07 7:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-07 7:57 Eduardo Valentin [this message]
2012-07-07 7:57 ` [PATCHv2 1/4] staging: OMAP4+: thermal: introduce bandgap temperature sensor Eduardo Valentin
2012-07-09 19:31 ` Greg Kroah-Hartman
2012-07-09 20:33 ` Valentin, Eduardo
2012-07-11 10:07 ` Valentin, Eduardo
2012-07-11 12:52 ` Greg Kroah-Hartman
2012-07-11 20:07 ` Valentin, Eduardo
2012-07-11 20:45 ` Valentin, Eduardo
2012-07-07 7:57 ` [PATCHv2 2/4] staging: omap-thermal: common code to expose driver to thermal framework Eduardo Valentin
2012-07-07 7:57 ` [PATCHv2 3/4] staging: omap-thermal: add OMAP4 data structures Eduardo Valentin
2012-07-07 7:57 ` [PATCHv2 4/4] staging: omap-thermal: add OMAP5 " 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=1341647872-15267-1-git-send-email-eduardo.valentin@ti.com \
--to=eduardo.valentin@ti.com \
--cc=b-cousson@ti.com \
--cc=devel@driverdev.osuosl.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=j-keerthy@ti.com \
--cc=kbaidarov@dev.rtsoft.ru \
--cc=linux-kernel@vger.kernel.org \
/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