All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: linux-pm@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Cc: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: [PATCH 0/3] thermal: rcar_thermal: Update how temperature is read
Date: Tue, 10 Mar 2020 18:00:26 +0100	[thread overview]
Message-ID: <20200310170029.1648996-1-niklas.soderlund+renesas@ragnatech.se> (raw)

Hi,

This series simplifies how the temperature is read, actually notifies a 
zone on temperature changes and removes the need for locking in some 
code paths. The change is made possible by a quiet old commit [1] which 
made reading the ctemp value from hardware every time it's needed 
mandatory.

1. a1ade5653804b8eb ("thermal: rcar: check every rcar_thermal_update_temp() return value")

Niklas Söderlund (3):
  thermal: rcar_thermal: Always update thermal zone on interrupt
  thermal: rcar_thermal: Do not store ctemp in rcar_thermal_priv
  thermal: rcar_thermal: Remove lock in rcar_thermal_get_current_temp()

 drivers/thermal/rcar_thermal.c | 47 ++++++++++------------------------
 1 file changed, 13 insertions(+), 34 deletions(-)

-- 
2.25.1


             reply	other threads:[~2020-03-10 17:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10 17:00 Niklas Söderlund [this message]
2020-03-10 17:00 ` [PATCH 1/3] thermal: rcar_thermal: Always update thermal zone on interrupt Niklas Söderlund
2020-03-11 12:38   ` Geert Uytterhoeven
2020-03-10 17:00 ` [PATCH 2/3] thermal: rcar_thermal: Do not store ctemp in rcar_thermal_priv Niklas Söderlund
2020-03-11 12:40   ` Geert Uytterhoeven
2020-03-10 17:00 ` [PATCH 3/3] thermal: rcar_thermal: Remove lock in rcar_thermal_get_current_temp() Niklas Söderlund
2020-03-11 12:43   ` Geert Uytterhoeven

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=20200310170029.1648996-1-niklas.soderlund+renesas@ragnatech.se \
    --to=niklas.soderlund+renesas@ragnatech.se \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-renesas-soc@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 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.