public inbox for linux-hwmon@vger.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Guenter Roeck <linux@roeck-us.net>, Jean Delvare <jdelvare@suse.com>
Cc: <linux-hwmon@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/3] hwmon: (tmp102) Improve handling of initial read delay
Date: Tue, 12 Jul 2016 15:53:17 -0500	[thread overview]
Message-ID: <578558BD.1000608@ti.com> (raw)
In-Reply-To: <1467258119-14071-1-git-send-email-linux@roeck-us.net>

On 06/29/2016 10:41 PM, Guenter Roeck wrote:
> If the chip was in shutdown mode when the driver was loaded, the first
> conversion is ready no more than 35 milli-seconds after the chip was
> taken out of shutdown. The driver delay was so far set to 333 ms (HZ / 3),
> which is much higher than the maximum time needed by the chip.
> Reduce the time to 35 milli-seconds.
>
> Introduce a 'valid' flag to ensure that sensor data is actually read
> even if requested less than 333 ms after the driver was loaded.
>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> ---
> v3: Don't go to sleep if sensor readings are not available;
>      instead, return -EAGAIN (matching previous behavior)
>      tmp102_update_device() is now a void function.
> v2: No change
>
> Note: This series depends on the following two patches in -next.


a little too late perhaps.. Apologies, was on vacation.. tested and 
for the series:

Acked-by: Nishanth Menon <nm@ti.com>


-- 
Regards,
Nishanth Menon

  parent reply	other threads:[~2016-07-12 20:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30  3:41 [PATCH v3 1/3] hwmon: (tmp102) Improve handling of initial read delay Guenter Roeck
2016-06-30  3:41 ` [PATCH v3 2/3] hwmon: (tmp102) Rework chip configuration Guenter Roeck
2016-06-30  3:41 ` [PATCH v3 3/3] hwmon: (tmp102) Convert to use regmap, and drop local cache Guenter Roeck
2016-07-12 20:53 ` Nishanth Menon [this message]
2016-07-12 21:24   ` [PATCH v3 1/3] hwmon: (tmp102) Improve handling of initial read delay Guenter Roeck

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=578558BD.1000608@ti.com \
    --to=nm@ti.com \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox