From: jic23@kernel.org (Jonathan Cameron)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] iio: adc: sun4i-gpadc-iio: register in the thermal after registering in pm
Date: Sat, 30 Sep 2017 18:45:38 +0100 [thread overview]
Message-ID: <20170930184538.10ec70f1@archlinux> (raw)
In-Reply-To: <f7b1b9c493c563a2f5b5f5f44596d45d3d719d26.1506430136.git-series.quentin.schulz@free-electrons.com>
On Tue, 26 Sep 2017 14:52:18 +0200
Quentin Schulz <quentin.schulz@free-electrons.com> wrote:
> This driver has a get_temp function used by the thermal framework that
> uses pm functions.
>
> However, the driver isn't registered in pm before it is registered in
> thermal framework, resulting in the pm_resume not being called and thus
> the IP not enabled.
>
> When the IP is disabled, the raw temp value is always 0. With the
> devices currently supported, it isn't a problem since with their
> respective formula, they return a really cold SoC temperature which
> isn't a problem for the thermal framework. But for future SoC that have
> a different formula, it could return a critically hot temperature,
> forcing the thermal framework to shutdown the board.
>
> Signed-off-by: Quentin Schulz <quentin.schulz@free-electrons.com>
Hmm. I wondered about sending this as a fix, but decided in the end
that your argument convinced me we could let this go the slow way.
Applied to the togreg branch of iio.git and pushed out as testing
for the autobuilders to play with.
Thanks,
Jonathan
> ---
> drivers/iio/adc/sun4i-gpadc-iio.c | 34 ++++++++++++++------------------
> 1 file changed, 15 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/iio/adc/sun4i-gpadc-iio.c b/drivers/iio/adc/sun4i-gpadc-iio.c
> index 137f577..392d47f 100644
> --- a/drivers/iio/adc/sun4i-gpadc-iio.c
> +++ b/drivers/iio/adc/sun4i-gpadc-iio.c
> @@ -529,17 +529,10 @@ static int sun4i_gpadc_probe_dt(struct platform_device *pdev,
> return ret;
> }
>
> - if (!IS_ENABLED(CONFIG_THERMAL_OF))
> - return 0;
> + if (IS_ENABLED(CONFIG_THERMAL_OF))
> + info->sensor_device = &pdev->dev;
>
> - info->sensor_device = &pdev->dev;
> - info->tzd = thermal_zone_of_sensor_register(info->sensor_device, 0,
> - info, &sun4i_ts_tz_ops);
> - if (IS_ERR(info->tzd))
> - dev_err(&pdev->dev, "could not register thermal sensor: %ld\n",
> - PTR_ERR(info->tzd));
> -
> - return PTR_ERR_OR_ZERO(info->tzd);
> + return 0;
> }
>
> static int sun4i_gpadc_probe_mfd(struct platform_device *pdev,
> @@ -586,15 +579,6 @@ static int sun4i_gpadc_probe_mfd(struct platform_device *pdev,
> * return the temperature.
> */
> info->sensor_device = pdev->dev.parent;
> - info->tzd = thermal_zone_of_sensor_register(info->sensor_device,
> - 0, info,
> - &sun4i_ts_tz_ops);
> - if (IS_ERR(info->tzd)) {
> - dev_err(&pdev->dev,
> - "could not register thermal sensor: %ld\n",
> - PTR_ERR(info->tzd));
> - return PTR_ERR(info->tzd);
> - }
> } else {
> indio_dev->num_channels =
> ARRAY_SIZE(sun4i_gpadc_channels_no_temp);
> @@ -664,6 +648,18 @@ static int sun4i_gpadc_probe(struct platform_device *pdev)
> pm_runtime_set_suspended(&pdev->dev);
> pm_runtime_enable(&pdev->dev);
>
> + if (IS_ENABLED(CONFIG_THERMAL_OF)) {
> + info->tzd = thermal_zone_of_sensor_register(info->sensor_device,
> + 0, info,
> + &sun4i_ts_tz_ops);
> + if (IS_ERR(info->tzd)) {
> + dev_err(&pdev->dev,
> + "could not register thermal sensor: %ld\n",
> + PTR_ERR(info->tzd));
> + return PTR_ERR(info->tzd);
> + }
> + }
> +
> ret = devm_iio_device_register(&pdev->dev, indio_dev);
> if (ret < 0) {
> dev_err(&pdev->dev, "could not register the device\n");
>
> base-commit: 1f183459b5144384e2669a3f757d36bacab108cf
prev parent reply other threads:[~2017-09-30 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 12:52 [PATCH 1/2] iio: adc: sun4i-gpadc-iio: register in the thermal after registering in pm Quentin Schulz
2017-09-26 12:52 ` [PATCH 2/2] iio: adc: sun4i-gpadc-iio: do not fail probing when no thermal DT node Quentin Schulz
2017-09-26 13:20 ` Maxime Ripard
2017-09-30 17:45 ` Jonathan Cameron [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=20170930184538.10ec70f1@archlinux \
--to=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).