From: Florian Fainelli <f.fainelli@gmail.com>
To: Sudeep Holla <sudeep.holla@arm.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
linux-hwmon@vger.kernel.org
Cc: Guenter Roeck <linux@roeck-us.net>
Subject: Couple of questions on SCMI sensor protocol and Linux implementation
Date: Tue, 2 Apr 2019 20:22:58 -0700 [thread overview]
Message-ID: <1902f151-7ddd-6b4b-4135-a2affe20c009@gmail.com> (raw)
Hi Sudeep,
There are a couple of things on which I would appreciate your feedback
regarding the Linux SCMI sensor protocol:
1) The Linux SCMI implementation has all the nuts and bolts to allow
configuring trip points, but the hwmon subsystem through the use of
hwmon_thermal_add_sensor() API does not actually make use of that
capability. Would it be a big stretch to use the hwmon_ops::write
function to get to support that feature? The other thing that puzzles me
is that there does not appear to be provision in the SCMI sensor
protocol to describe thermal zones, so I assume that people still have
to provide supplemental data through Device Tree for
devm_thermal_zone_of_sensor_register() to pick up the thermal zones
definitions?
2) Support for regulators through SCMI
I work with a device where the regulators can only be controlled via a
dedicated piece of HW which is accessible through SCMI from the Linux
side. Do you think there is value in coming up with a scmi-regulator.c
driver that makes use of the sensor protocol for discovering and
reporting regulators or would that be something that belongs more to the
power domain protocol?
Thanks for reading me! Cheers
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-04-03 3:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 3:22 Florian Fainelli [this message]
2019-04-12 13:57 ` Couple of questions on SCMI sensor protocol and Linux implementation Sudeep Holla
2019-04-12 15:38 ` Guenter Roeck
2019-04-12 22:40 ` Florian Fainelli
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=1902f151-7ddd-6b4b-4135-a2affe20c009@gmail.com \
--to=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sudeep.holla@arm.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;
as well as URLs for NNTP newsgroup(s).