From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Cc: Wolfram Sang <wsa@kernel.org>,
linux-pm@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 0/3] drivers/thermal/rcar_gen3_thermal: Fix device initialization
Date: Fri, 10 Feb 2023 11:27:14 +0100 [thread overview]
Message-ID: <20230210102649.GD175687@linaro.org> (raw)
In-Reply-To: <20230208190333.3159879-1-niklas.soderlund+renesas@ragnatech.se>
On Wed, Feb 08, 2023 at 08:03:30PM +0100, Niklas Söderlund wrote:
> Hello,
>
> This small series fixes a window where incorrect values can be read from
> the driver before it is fully initialized. The root cause is that the
> thermal zone is register too early.
>
> Patch 1/3 is new in v2 and removes a unneeded call to set_trips() when
> resuming from suspend, This call was in v1 changed as part of addressing
> the initialization issue, it's nicer to get rid of it before that is
> needed.
>
> Patch 2/3 prepares for the change while also fixing a theoretical issue
> where one thermal node described in DT would describe interrupts and
> another would not. Resulting in interrupt support being disabled for
> both of them. I'm not aware of any case where this configuration would
> be used, either the SoC supports interrupts, or it don't.
>
> While patch 3/3 fixes the real issue by fully initializing the device
> before registering the zone.
>
> Niklas Söderlund (3):
> drivers/thermal/rcar_gen3_thermal: Do not call set_trips() when
> resuming
> drivers/thermal/rcar_gen3_thermal: Create device local ops struct
> drivers/thermal/rcar_gen3_thermal: Fix device initialization
>
> drivers/thermal/rcar_gen3_thermal.c | 36 ++++++++++++++---------------
> 1 file changed, 18 insertions(+), 18 deletions(-)
Applied, thhanks
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
prev parent reply other threads:[~2023-02-10 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 19:03 [PATCH v2 0/3] drivers/thermal/rcar_gen3_thermal: Fix device initialization Niklas Söderlund
2023-02-08 19:03 ` [PATCH v2 1/3] drivers/thermal/rcar_gen3_thermal: Do not call set_trips() when resuming Niklas Söderlund
2023-02-08 19:03 ` [PATCH v2 2/3] drivers/thermal/rcar_gen3_thermal: Create device local ops struct Niklas Söderlund
2023-02-08 19:03 ` [PATCH v2 3/3] drivers/thermal/rcar_gen3_thermal: Fix device initialization Niklas Söderlund
2023-02-10 10:27 ` Daniel Lezcano [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=20230210102649.GD175687@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=wsa@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 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).