From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linux-pm@vger.kernel.org, thierry.reding@gmail.com,
Amit Kucheria <amitk@kernel.org>, Zhang Rui <rui.zhang@intel.com>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
"Lee, Chun-Yi" <joeyli.kernel@gmail.com>,
ye xingchen <ye.xingchen@zte.com.cn>,
open list <linux-kernel@vger.kernel.org>,
rafael@kernel.org
Subject: Re: [PATCH 5/8] thermal/drivers/int3400: Use thermal zone device wrappers
Date: Wed, 05 Jul 2023 04:35:59 -0700 [thread overview]
Message-ID: <f3679761bbf31ff93d45985f67a85f28b0027eac.camel@linux.intel.com> (raw)
In-Reply-To: <77c90891-3712-4b3b-a22c-d9ccba36f58e@linaro.org>
Hi Daniel,
On Wed, 2023-07-05 at 12:41 +0200, Daniel Lezcano wrote:
>
> Hi Srinivas,
>
> thanks for your answer. What about the patch 6?
I was not CCed. But checked from LKML,
The change looks good.
Thanks,
Srinivas
>
>
> On 03/07/2023 18:15, srinivas pandruvada wrote:
> > Hi Daniel,
> >
> > On Mon, 2023-07-03 at 12:49 +0200, Daniel Lezcano wrote:
> > >
> > > Hi Srinivas,
> > >
> > > do you agree with the changes in patches 5 and 6 ?
> > >
> > > Thanks
> > >
> > > -- Daniel
> > >
> > >
> > > On 25/05/2023 16:01, Daniel Lezcano wrote:
> > > > The driver is accessing the thermal zone device structure but
> > > > the
> > > > accessors are already existing and we want to consolidate the
> > > > thermal
> > > > core code by preventing accesses to the internals from the
> > > > drivers.
> > > >
> > > > Let's use these accessors.
> > > >
> > > > On the other side, the code is getting directly the temperature
> > > > from
> > > > tz->temperature, but the temperature is a faked on, so we can
> > > > replace
> > > > this access by the fake temp and remove the thermal zone device
> > > > structure access.
> > > >
> > May be something simple description like this will be enough.
> >
> > "
> > Use thermal core API to access thermal zone "type" field instead of
> > directly using the structure field.
> > While here, remove access to temperature field, as this driver is
> > reporting fake temperature, which can be replaced with
> > INT3400_FAKE_TEMP. Also replace hardcoded 20C with
> > INT3400_FAKE_TEMP.
> > "
> >
> > The change itself looks fine.
>
>
next prev parent reply other threads:[~2023-07-05 11:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 14:01 [PATCH 0/8] Finish thermal zone structure encapsulation Daniel Lezcano
2023-05-25 14:01 ` [PATCH 1/8] net/mlx5: Update the driver with the recent thermal changes Daniel Lezcano
2023-05-26 9:20 ` Simon Horman
2023-05-31 22:10 ` Saeed Mahameed
2023-06-07 13:17 ` Daniel Lezcano
2023-05-25 14:01 ` [PATCH 2/8] thermal/core: Hardening the self-encapsulation Daniel Lezcano
2023-05-25 14:01 ` [PATCH 3/8] thermal/core: Reorder the headers inclusion Daniel Lezcano
2023-05-25 14:01 ` [PATCH 4/8] thermal/core: Update the generic trip points Daniel Lezcano
2023-06-20 11:28 ` Rafael J. Wysocki
2023-06-20 18:35 ` Daniel Lezcano
2023-06-23 17:59 ` Rafael J. Wysocki
2023-06-25 20:29 ` Rafael J. Wysocki
2023-05-25 14:01 ` [PATCH 5/8] thermal/drivers/int3400: Use thermal zone device wrappers Daniel Lezcano
2023-07-03 10:49 ` Daniel Lezcano
2023-07-03 16:15 ` srinivas pandruvada
2023-07-05 10:41 ` Daniel Lezcano
2023-07-05 11:35 ` srinivas pandruvada [this message]
2023-07-05 11:49 ` Daniel Lezcano
2023-05-25 14:01 ` [PATCH 6/8] thermal/drivers/int340x: Do not check the thermal zone state Daniel Lezcano
2023-05-25 14:01 ` [PATCH 7/8] thermal/drivers/int340x: Use thermal zone device trip update Daniel Lezcano
2023-05-25 14:01 ` [PATCH 8/8] thermal/core: Move the thermal zone structure to the private core header Daniel Lezcano
2023-06-13 14:12 ` [PATCH 0/8] Finish thermal zone structure encapsulation Daniel Lezcano
2023-06-20 10:54 ` Rafael J. Wysocki
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=f3679761bbf31ff93d45985f67a85f28b0027eac.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=amitk@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=daniel.lezcano@linaro.org \
--cc=jernej.skrabec@gmail.com \
--cc=joeyli.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=thierry.reding@gmail.com \
--cc=ye.xingchen@zte.com.cn \
/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).