From: "Zhang, Rui" <rui.zhang@intel.com>
To: "rafael@kernel.org" <rafael@kernel.org>,
"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Thomas, Sujith" <sujith.thomas@intel.com>,
"amitk@kernel.org" <amitk@kernel.org>
Subject: Re: [PATCH RFC] thermal/drivers/intel_menlow: Remove add_one_attribute
Date: Tue, 21 Feb 2023 12:58:59 +0000 [thread overview]
Message-ID: <6b63db0832fadffa56ff85a1c4ca2b98d165df50.camel@intel.com> (raw)
In-Reply-To: <b66fca52-d1f9-2761-4117-819c5820308d@linaro.org>
Hi, Daniel,
On Tue, 2023-02-21 at 12:30 +0100, Daniel Lezcano wrote:
> Hi Rui,
>
>
> On 21/02/2023 07:22, Zhang, Rui wrote:
> > On Mon, 2023-02-20 at 17:24 +0100, Daniel Lezcano wrote:
> > > The driver hooks the thermal framework sysfs to add some driver
> > > specific information. A debatable approach as that may belong the
> > > device sysfs directory, not the thermal zone directory.
> > >
> > > As the driver is accessing the thermal internals, we should
> > > provide
> > > at
> > > least an API to the thermal framework to add an attribute to the
> > > existing sysfs thermal zone entry.
> > >
> > > Before doing that and given the age of the driver (2008) may be
> > > it is
> > > worth to double check if these attributes are really needed. So
> > > my
> > > first proposal is to remove them if that does not hurt.
> > >
> > > Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> >
> > I don't have any device that uses this driver.
> > Let's see what Sujith says.
>
> Thanks for your answer.
>
> I take the opportunity to ask you for the ACPI thermal additional
> sysfs
> entries.
>
> The ACPI thermal driver adds a link:
>
> /sys/class/thermal/thermal_zone0/device
>
> which points to:
>
> ../../../LNXSYSTM:00/LNXSYBUS:01/LNXTHERM:00
>
>
> And in this directory there is:
>
> /sys/devices/LNXSYSTM:00/LNXSYBUS:01/LNXTHERM:00/thermal_zone
>
> pointing to /sys/class/thermal/thermal_zone0
>
>
> I was wondering if we have to keep it also? It is a cyclic
> description
> and we can have the several thermal zones having a device link
> pointing
> to the same location.
I don't think so. So far, ACPI Thermal object and the generic thermal
zone device are 1:1 match.
> So I'm not sure this is correct.
>
> I can understand adding a link in the thermal zone pointing to the
> device could make sense, and that could be generalized to all the
> thermal zone creation, but the back pointer link seems strange.
>
> Would it make sense to remove this second link ?
That was required by some userpsace tool running on menlow, similar to
this one. But TBH, I don't recall the userspace details.
thanks,
rui
next prev parent reply other threads:[~2023-02-21 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 16:24 Daniel Lezcano
2023-02-21 6:22 ` Zhang, Rui
2023-02-21 11:30 ` Daniel Lezcano
2023-02-21 12:58 ` Zhang, Rui [this message]
2023-02-21 13:31 ` Daniel Lezcano
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=6b63db0832fadffa56ff85a1c4ca2b98d165df50.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sujith.thomas@intel.com \
/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
all inboxes | Powered by JetHome®