From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Valentin, Eduardo" <eduardo.valentin@ti.com>
Cc: devel@driverdev.osuosl.org, b-cousson@ti.com, j-keerthy@ti.com,
linux-kernel@vger.kernel.org, kbaidarov@dev.rtsoft.ru,
grant.likely@secretlab.ca
Subject: Re: [PATCHv3 1/4] staging: OMAP4+: thermal: introduce bandgap temperature sensor
Date: Thu, 12 Jul 2012 08:34:52 -0700 [thread overview]
Message-ID: <20120712153452.GC17365@kroah.com> (raw)
In-Reply-To: <CAGF5oy8585Lb6ibsgzo+3aDJEc-vcRwiu4hxtNS=GFUEy7LDqQ@mail.gmail.com>
On Thu, Jul 12, 2012 at 05:45:52AM +0300, Valentin, Eduardo wrote:
> Hello,
>
> On Thu, Jul 12, 2012 at 3:32 AM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > On Wed, Jul 11, 2012 at 11:41:06PM +0300, Eduardo Valentin wrote:
> >> In the System Control Module, OMAP supplies a voltage reference
> >> and a temperature sensor feature that are gathered in the band
> >> gap voltage and temperature sensor (VBGAPTS) module. The band
> >> gap provides current and voltage reference for its internal
> >> circuits and other analog IP blocks. The analog-to-digital
> >> converter (ADC) produces an output value that is proportional
> >> to the silicon temperature.
> >>
> >> This patch provides a platform driver which expose this feature.
> >> It is moduled as a MFD child of the System Control Module core
> >> MFD driver.
> >>
> >> This driver provides only APIs to access the device properties,
> >> like temperature, thresholds and update rate.
> >>
> >> Signed-off-by: Eduardo Valentin <eduardo.valentin@ti.com>
> >> Signed-off-by: J Keerthy <j-keerthy@ti.com>
> >
> > This patch gives me the following build error:
> >
> > rivers/staging/omap-thermal/omap-bandgap.c: In function ‘omap_bandgap_build’:
> > drivers/staging/omap-thermal/omap-bandgap.c:805:2: error: implicit declaration of function ‘of_match_device’ [-Werror=implicit-function-declaration]
> > drivers/staging/omap-thermal/omap-bandgap.c:805:8: warning: assignment makes pointer from integer without a cast [enabled by default]
>
> OK. Those I didn't see while testing on my side. I didn't use
> -Werror=implicit-function-declaration though.
You shouldn't need to do that, just build this driver on your desktop
and you will see the error (hint, do you really want to build this on
x86-64 platforms?)
thanks,
greg k-h
next prev parent reply other threads:[~2012-07-12 15:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 20:41 [PATCHv3 0/4] staging: adding OMAP bandgap driver Eduardo Valentin
2012-07-11 20:41 ` [PATCHv3 1/4] staging: OMAP4+: thermal: introduce bandgap temperature sensor Eduardo Valentin
2012-07-12 0:32 ` Greg Kroah-Hartman
2012-07-12 2:45 ` Valentin, Eduardo
2012-07-12 14:25 ` Valentin, Eduardo
2012-07-12 15:34 ` Greg Kroah-Hartman [this message]
2012-07-12 15:36 ` Valentin, Eduardo
2012-07-11 20:41 ` [PATCHv3 2/4] staging: omap-thermal: common code to expose driver to thermal framework Eduardo Valentin
2012-07-11 20:41 ` [PATCHv3 3/4] staging: omap-thermal: add OMAP4 data structures Eduardo Valentin
2012-07-11 20:41 ` [PATCHv3 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=20120712153452.GC17365@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=b-cousson@ti.com \
--cc=devel@driverdev.osuosl.org \
--cc=eduardo.valentin@ti.com \
--cc=grant.likely@secretlab.ca \
--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