linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Valentin <edubezval@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: pali.rohar@gmail.com, sre@debian.org, sre@ring0.de,
	kernel list <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-omap@vger.kernel.org, tony@atomide.com, khilman@kernel.org,
	aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com,
	rui.zhang@intel.com, linux-pm@vger.kernel.org
Subject: Re: [PATCH] ti-soc-thermal: implement eocz bit to make driver useful on omap3
Date: Mon, 5 Jan 2015 17:35:59 -0400	[thread overview]
Message-ID: <20150105213557.GD31536@developer> (raw)
In-Reply-To: <20150103162241.GA26680@amd>

[-- Attachment #1: Type: text/plain, Size: 1987 bytes --]

On Sat, Jan 03, 2015 at 05:22:42PM +0100, Pavel Machek wrote:
> Hi!
> 
> > > When periodic mode is not enabled, it is neccessary to force reads.
> > > 
> > > Signed-off-by: Pavel Machek <pavel@ucw.cz>
> > > 
> 
> > > --- a/drivers/thermal/ti-soc-thermal/ti-bandgap.c
> > > +++ b/drivers/thermal/ti-soc-thermal/ti-bandgap.c
> > > @@ -43,6 +43,8 @@
> > >  
> > >  #include "ti-bandgap.h"
> > >  
> > > +static int ti_bandgap_force_single_read(struct ti_bandgap *bgp, int id);
> > > +
> > >  /***   Helper functions to access registers and their bitfields   ***/
> > >  
> > >  /**
> > > @@ -852,14 +831,20 @@ int ti_bandgap_read_temperature(struct ti_bandgap *bgp, int id,
> > >  	if (ret)
> > >  		return ret;
> > >  
> > > +	if (!TI_BANDGAP_HAS(bgp, MODE_CONFIG)) {
> > > +		ret = ti_bandgap_force_single_read(bgp, id);
> > 
> > not sure MODE_CONFIG is sufficient condition for single read on all OMAP
> > versions.
> 
> Ok, what do you suggest? AFAICT, without MODE_CONFIG, continuous ADC
> mode is not available, so we have to force it periodically, so this
> should be correct.

I will have a better look and let you know. for now, adding a single
read should not hurt ( but I will double check)

> 
> > > +		if (ret)
> > > +			return ret;
> > > +	}
> > > +
> > >  	spin_lock(&bgp->lock);
> > >  	temp = ti_bandgap_read_temp(bgp, id);
> > >  	spin_unlock(&bgp->lock);
> > >  
> > > -	ret |= ti_bandgap_adc_to_mcelsius(bgp, temp, &temp);
> > > +	ret = ti_bandgap_adc_to_mcelsius(bgp, temp, &temp);
> > 
> > this one should be part of your clean up patch
> 
> Ok, can you apply the cleanup patch and I'll prepare one on the top of
> it?

I mean, you should resend the cleanup patch including the above '|=' removal, as you are already doing in the cleanup patch.

> 
> 									Pavel
> -- 
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-01-05 21:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-03 11:46 [PATCH] ti-soc-thermal: implement eocz bit to make driver useful on omap3 Pavel Machek
2015-01-03 12:26 ` Eduardo Valentin
2015-01-03 16:22   ` Pavel Machek
2015-01-05 21:35     ` Eduardo Valentin [this message]
2015-01-18 20:18       ` Pavel Machek
2015-01-21  5:21         ` Eduardo Valentin
2015-01-18 20:20 ` [PATCHv2] " Pavel Machek
2015-01-18 20:24 ` [PATCHv2] ti-soc-thermal: request temperature periodically if hw can't do that itself Pavel Machek
2015-03-24 16:30   ` Eduardo Valentin
2015-03-24 22:27     ` Pavel Machek
2015-03-24 22:20   ` [PATCHv3] " Pavel Machek
2015-03-31  8:42   ` [PATCH] ti-soc-thermal: implement omap3 support Pavel Machek
2015-03-31 15:02     ` Grazvydas Ignotas
2015-04-02 14:49       ` Pavel Machek
2015-04-02 14:49     ` [PATCHv2] " Pavel Machek
2015-04-07 18:57       ` Eduardo Valentin
2015-04-07 19:09       ` 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=20150105213557.GD31536@developer \
    --to=edubezval@gmail.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=ivo.g.dimitrov.75@gmail.com \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=rui.zhang@intel.com \
    --cc=sre@debian.org \
    --cc=sre@ring0.de \
    --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).