linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dmitry.torokhov@gmail.com (Dmitry Torokhov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] touchscreen: sun4i-ts: A10 (sun4i) has a different temperature curve
Date: Sun, 8 Mar 2015 14:11:17 -0700	[thread overview]
Message-ID: <20150308211117.GA23193@dtor-ws> (raw)
In-Reply-To: <1425848022-18001-1-git-send-email-hdegoede@redhat.com>

Hi Hans,

On Sun, Mar 08, 2015 at 09:53:39PM +0100, Hans de Goede wrote:
> Hi Dmitry, Maxime, et al.
> 
> Here is a patch-set for the sun4i-ts driver temperature sensor support,
> it consists of 2 fixes:
> 
> 1) Use a better temperature curve for A10 SoCs to avoid reporting a way to
> high temperature.
> 
> 2) Start with reporting an "estimated" temperature of 40 degrees rather then
> returning -EAGAIN until we get the first temperature ready interrupt to avoid
> the kernel tempzone core logging errors because of our -EAGAIN return.

No, I think we better teach thermal core not to complain about
-EAGAINs.

> 
> Dmitry can you please queue up the 2 sun4i-ts patches for 4.1, and Maxime,
> can you please queue up the matching dts change ?
> 
> Thanks & Regards,
> 
> Hans

-- 
Dmitry

  parent reply	other threads:[~2015-03-08 21:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-08 20:53 [PATCH 0/3] touchscreen: sun4i-ts: A10 (sun4i) has a different temperature curve Hans de Goede
2015-03-08 20:53 ` [PATCH 1/3] " Hans de Goede
2015-03-08 21:13   ` Dmitry Torokhov
2015-03-09  8:15     ` Hans de Goede
2015-03-08 20:53 ` [PATCH 2/3] touchscreen: sun4i-ts: Do not report -EAGAIN from tempzone callback Hans de Goede
2015-03-08 20:53 ` [PATCH 3/3] ARM: dts: sunxi: Adjust touchscreen compatible for sun5i and later Hans de Goede
2015-03-08 21:43   ` Maxime Ripard
2015-03-08 21:11 ` Dmitry Torokhov [this message]
2015-03-09  8:17   ` [PATCH 0/3] touchscreen: sun4i-ts: A10 (sun4i) has a different temperature curve Hans de Goede

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=20150308211117.GA23193@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).