From: Punit Agrawal <punit.agrawal@arm.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-pm@vger.kernel.org, lm-sensors@lm-sensors.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Jean Delvare <jdelvare@suse.de>,
Eduardo Valentin <edubezval@gmail.com>
Subject: Re: [PATCH 7/9] hwmon: Support registration of thermal zones for SCP temperature sensors
Date: Fri, 24 Jul 2015 15:12:59 +0100 [thread overview]
Message-ID: <9hhoaj1bq50.fsf@e105922-lin.cambridge.arm.com> (raw)
In-Reply-To: <55AFBDC1.3000604@roeck-us.net> (Guenter Roeck's message of "Wed, 22 Jul 2015 08:58:57 -0700")
Hi Guenter,
Guenter Roeck <linux@roeck-us.net> writes:
> On 07/22/2015 07:02 AM, Punit Agrawal wrote:
>> Add support to create thermal zones based on the temperature sensors
>> provided by the SCP. The thermal zones can be defined using the
>> thermal DT bindings and should refer to the SCP sensor id to select
>> the sensor.
>>
>> Signed-off-by: Punit Agrawal <punit.agrawal@arm.com>
>> Cc: Jean Delvare <jdelvare@suse.de>
>> Cc: Guenter Roeck <linux@roeck-us.net>
>> Cc: Eduardo Valentin <edubezval@gmail.com>
>> ---
>> drivers/hwmon/scpi-hwmon.c | 53 ++++++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 53 insertions(+)
>>
>> diff --git a/drivers/hwmon/scpi-hwmon.c b/drivers/hwmon/scpi-hwmon.c
>> index dd0a6f1..1e52ced 100644
>> --- a/drivers/hwmon/scpi-hwmon.c
>> +++ b/drivers/hwmon/scpi-hwmon.c
[...]
>> @@ -54,6 +61,20 @@ static int scpi_read_sensor(struct sensor_dev *sensor, u32 *value)
>> return 0;
>> }
>>
>> +static int scpi_read_temp(void *dev, long *temp)
>> +{
>> + struct sensor_dev *sensor = dev;
>> + u32 value;
>> + int ret;
>> +
>> + ret = scpi_read_sensor(sensor, &value);
>> + if (ret)
>> + return ret;
>> +
>> + *temp = value;
>> + return 0;
>> +}
>> +
>> /* hwmon callback functions */
>> static ssize_t
>> scpi_hwmon_show_sensor(struct device *dev,
>> @@ -90,6 +111,10 @@ struct attribute *scpi_attrs[24] = { 0 };
>> struct attribute_group scpi_group;
>> const struct attribute_group *scpi_groups[2] = { 0 };
>>
>> +struct thermal_zone_of_device_ops scpi_sensor_ops = {
>
> static struct ...
>
Updated.
>> + .get_temp = scpi_read_temp,
>> +};
>> +
>> static int scpi_hwmon_probe(struct platform_device *pdev)
>> {
>> u16 sensors, i;
>> @@ -108,9 +133,12 @@ static int scpi_hwmon_probe(struct platform_device *pdev)
>> if (!scpi_sensors.device)
>> return -ENOMEM;
>>
>> + INIT_LIST_HEAD(&scpi_sensors.thermal_zones);
>> +
>> dev_info(&pdev->dev, "Found %d sensors\n", sensors);
>> for (i = 0; i < sensors; i++) {
>> struct sensor_dev *dev = &scpi_sensors.device[i];
>> + struct scpi_thermal_zone *zone;
>>
>> ret = scpi_ops->sensor_get_info(i, &dev->info);
>> if (ret) {
>> @@ -130,6 +158,20 @@ static int scpi_hwmon_probe(struct platform_device *pdev)
>> snprintf(dev->label, 20,
>> "temp%d_label", scpi_sensors.num_temp);
>> scpi_sensors.num_temp++;
>> +
>> + zone = devm_kmalloc(&pdev->dev, sizeof(*zone),
>> + GFP_KERNEL);
>
> Please consider using devm_kzalloc().
>
Done
>> + if (!zone)
>> + return -ENOMEM;
>> +
>> + zone->tzd = thermal_zone_of_sensor_register(&pdev->dev,
>> + i, dev, &scpi_sensor_ops);
>> + if (!IS_ERR(zone->tzd))
>> + list_add(&zone->list,
>> + &scpi_sensors.thermal_zones);
>> + else
>> + devm_kfree(&pdev->dev, zone);
>> +
>
> I would prefer
>
> if (IS_ERR_OR_NULL(zone->tzd)) {
> devm_kfree(&pdev->dev, zone);
> break;
> }
> list_add(&zone->list, &scpi_sensors.thermal_zones);
>
> The code has a problem, though: You don't clean up thermal zones if
> there is an error later on in the probe function. Either you need to
> implement a cleanup function to be called from an error handler (and
> from the remove function), or you need to wait with registering
> thermal zones to the very end of the probe function.
>
I've re-factored to register the sensors at the end of the probe.
> Note that thermal_zone_of_sensor_register can return NULL if thermal
> zones are not configured, so you have to use IS_ERR_OR_NULL
> when checking for errors.
>
You're right. I missed the NULL return when THERMAL_OF is configured
off. This doesn't match the documentation at the top of the function in
drivers/thermal/of-thermal.c
* Return: On success returns a valid struct thermal_zone_device,
* otherwise, it returns a corresponding ERR_PTR(). Caller must
* check the return value with help of IS_ERR() helper.
Usage of thermal_zone_of_sensor_register in other drivers matches the above
doc. I'll include a patch fixing the NULL return with the next version.
>> break;
>> case VOLTAGE:
>> snprintf(dev->input, 20,
>> @@ -187,7 +229,18 @@ static int scpi_hwmon_probe(struct platform_device *pdev)
>>
>> static int scpi_hwmon_remove(struct platform_device *pdev)
>> {
>> + struct list_head *pos;
>> +
>> scpi_ops = NULL;
>> +
>> + list_for_each(pos, &scpi_sensors.thermal_zones) {
>> + struct scpi_thermal_zone *zone;
>> +
>> + zone = list_entry(pos, struct scpi_thermal_zone, list);
>> + thermal_zone_of_sensor_unregister(scpi_sensors.hwdev,
>
> Not sure how this can work. The registration was with &pdev->dev,
> not with hwdev. What happens if you actually unload this driver ?
>
Thanks for catching this! I'll fix this in the next version.
I had tested unloading the driver and didn't notice any adverse
ill-effects. Although thermal_zone_of_sensor_unregister expects a
pointer to a device, other then checking for non-NULLness, it doesn't do
anything with it.
Perhaps, this argument should be dropped from the function. If the
thermal maintainers agree I can cook up a patch. Eduardo?
Thanks,
Punit
>> + zone->tzd);
>> + }
>> +
>> return 0;
>> }
>>
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-07-24 14:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 14:02 [PATCH 0/9] Platform support for thermal management on Junoe Punit Agrawal
2015-07-22 14:02 ` [PATCH 1/9] devicetree: bindings: Add optional dynamic-power-coefficient property Punit Agrawal
2015-07-22 14:02 ` [PATCH 2/9] cpufreq-dt: Supply power coefficient when registering cooling devices Punit Agrawal
2015-07-22 14:02 ` [PATCH 3/9] cpufreq: arm_big_little: Add support to register a cpufreq cooling device Punit Agrawal
2015-07-22 14:02 ` [PATCH 4/9] Documentation: add DT bindings for ARM SCPI sensors Punit Agrawal
2015-07-22 14:02 ` [PATCH 5/9] firmware: arm_scpi: Extend to support sensors Punit Agrawal
2015-07-22 14:02 ` [PATCH 6/9] hwmon: Support sensors exported via ARM SCP interface Punit Agrawal
2015-07-22 15:33 ` Guenter Roeck
2015-07-24 14:08 ` Punit Agrawal
2015-07-22 14:02 ` [PATCH 7/9] hwmon: Support registration of thermal zones for SCP temperature sensors Punit Agrawal
2015-07-22 15:58 ` Guenter Roeck
2015-07-24 14:12 ` Punit Agrawal [this message]
2015-07-22 14:02 ` [PATCH 8/9] arm64: dts: Add sensor node to Juno dt Punit Agrawal
2015-07-22 14:02 ` [PATCH 9/9] arm64: dts: Create SoC thermal zone for Juno Punit Agrawal
2015-07-23 9:29 ` [PATCH 0/9] Platform support for thermal management on Junoe Viresh Kumar
2015-07-24 14:16 ` Punit Agrawal
2015-07-25 1:27 ` Viresh Kumar
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=9hhoaj1bq50.fsf@e105922-lin.cambridge.arm.com \
--to=punit.agrawal@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lm-sensors@lm-sensors.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
all inboxes | Powered by JetHome®