All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: adc: axp288: Fix the GPADC pin reading often wrongly returning 0
Date: Sun, 9 Jul 2017 21:17:28 +0100	[thread overview]
Message-ID: <20170709211728.243035a5@kernel.org> (raw)
In-Reply-To: <d9d7599e-fcad-43aa-122e-f537f92435df@redhat.com>

On Sun, 9 Jul 2017 20:24:49 +0200
Hans de Goede <hdegoede@redhat.com> wrote:

> Hi,
> 
> On 09-07-17 20:22, Jonathan Cameron wrote:
> > On Sat,  8 Jul 2017 15:11:57 +0200
> > Hans de Goede <hdegoede@redhat.com> wrote:
> > 
> >> I noticed in its DSDT that one of my tablets actually is using the GPADC
> >> pin for temperature monitoring.
> >>
> >> The whole axp288_adc_set_ts() function is a bit weird, in the past it was
> >> removed because it seems to make no sense, then this was reverted because
> >> of regressions.
> >>
> >> So I decided to test the special GPADC pin handling on this tablet.
> >> Conclusion: not only is axp288_adc_set_ts() necessary, we need to sleep a
> >> bit after making the AXP288_ADC_TS_PIN_CTRL changes before sampling the
> >> GPADC, otherwise it will often (about 80% of the time) read 0 instead of
> >> its actual value.
> >>
> >> It seems that there is only 1 bias current source and to be able to use it
> >> for the GPIO0 pin in GPADC mode it must be temporarily turned off for the
> >> TS pin, but the datasheet does not mention this.
> >>
> >> This commit adds a sleep after disabling the TS pin bias current,
> >> fixing the GPADC more often then not wrongly returning 0.
> >>
> >> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> > Hans,
> > 
> > This is sufficiently weird that I want your opinion on what
> > to do with this.   Are we looking at a necessary fix for a hardware
> > platform that we should push out asap and mark for stable?
> > 
> > Or is this a bit of an odd corner case where a slower path makes
> > more sense?
> 
> Since we have had this bug for ages and no-one has noticed I think
> taking this a bit slower is fine. Would be nice to get it into 4.13,
> but no need for a Cc stable IMHO.
> 
> Thanks & Regards,
> 
> Hans
Thanks,

Applied to the fixes-togreg branch of iio.git.

It may still get picked up for stable, but I'm not going to explicitly
push it for such.

Jonathan
> 
> 
> > 
> > I'm happy either way.
> > 
> > Jonathan
> >> ---
> >>   drivers/iio/adc/axp288_adc.c | 12 +++++++++++-
> >>   1 file changed, 11 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/iio/adc/axp288_adc.c b/drivers/iio/adc/axp288_adc.c
> >> index 7fd24949c0c1..462a99c13e7a 100644
> >> --- a/drivers/iio/adc/axp288_adc.c
> >> +++ b/drivers/iio/adc/axp288_adc.c
> >> @@ -126,11 +126,21 @@ static int axp288_adc_read_channel(int *val, unsigned long address,
> >>   static int axp288_adc_set_ts(struct regmap *regmap, unsigned int mode,
> >>   				unsigned long address)
> >>   {
> >> +	int ret;
> >> +
> >>   	/* channels other than GPADC do not need to switch TS pin */
> >>   	if (address != AXP288_GP_ADC_H)
> >>   		return 0;
> >>   
> >> -	return regmap_write(regmap, AXP288_ADC_TS_PIN_CTRL, mode);
> >> +	ret = regmap_write(regmap, AXP288_ADC_TS_PIN_CTRL, mode);
> >> +	if (ret)
> >> +		return ret;
> >> +
> >> +	/* When switching to the GPADC pin give things some time to settle */
> >> +	if (mode == AXP288_ADC_TS_PIN_GPADC)
> >> +		usleep_range(6000, 10000);
> >> +
> >> +	return 0;
> >>   }
> >>   
> >>   static int axp288_adc_read_raw(struct iio_dev *indio_dev,
> > 


      reply	other threads:[~2017-07-09 20:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-08 13:11 [PATCH] iio: adc: axp288: Fix the GPADC pin reading often wrongly returning 0 Hans de Goede
2017-07-09 18:22 ` Jonathan Cameron
2017-07-09 18:24   ` Hans de Goede
2017-07-09 20:17     ` Jonathan Cameron [this message]

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=20170709211728.243035a5@kernel.org \
    --to=jic23@kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.