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: [PATCH 0/4] staging: adding OMAP bandgap driver
Date: Wed, 4 Jul 2012 01:37:06 +0300 [thread overview]
Message-ID: <1341355030-20800-1-git-send-email-eduardo.valentin@ti.com> (raw)
Hello Greg,
This is a set of patches which contains a temperature sensor driver
for OMAP platform and a minimal support for the generic thermal framework
(CONFIG_THERMAL).
It was originally written for TI's android development
tree, where it has its own thermal framework.
I have ripped it off from that tree and add basic support on the driver
to use the generic thermal framework (CONFIG_THERMAL). Apart from
that, the driver have already gone through some rewrites and redesigns.
This device resides inside the system control module of OMAP and the
original driver had a MFD design. Now with the rewrites, it got
only DT probing support and with that it has its own io area,
and it works pretty much independent.
FYI, the generic thermal framework is also under its own
improvements cycles, and the support I've written on this driver
I am sending, depends partially on it. It relies on the generic
CPU cooling device (CONFIG_CPU_COOLING). But the driver won't
compile that part of the code, unless the config entry is present.
So, the way it is now, it is compilable, but the output module
will not have thermal framework exposure (/sys/class/thermal).
The driver is under work, but it can already probe on OMAPs 4430,
4460 (potentially on 4470, but this is untested) and 5430.
So, I decided to send it to staging for maturation, instead
of maturating it out of the tree.
Let me know if it makes sense to keep it under staging.
Otherwise I can go through its maturation out of tree and
send it for merge under drivers/thermal/ (Len B.)
These patches are based on linux-next/master. And you can also
fetch them here:
git@gitorious.org:thermal-framework/thermal-framework.git thermal_work/omap/bandgap_staging
All best,
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-03 22:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 22:37 Eduardo Valentin [this message]
2012-07-03 22:37 ` [PATCH 1/4] staging: OMAP4+: thermal: introduce bandgap temperature sensor Eduardo Valentin
2012-07-06 23:27 ` Greg Kroah-Hartman
2012-07-07 6:48 ` Valentin, Eduardo
2012-07-03 22:37 ` [PATCH 2/4] staging: omap-thermal: common code to expose driver to thermal framework Eduardo Valentin
2012-07-03 22:37 ` [PATCH 3/4] staging: omap-thermal: add OMAP4 data structures Eduardo Valentin
2012-07-03 22:37 ` [PATCH 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=1341355030-20800-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
all inboxes | Powered by JetHome®