linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Valentin <edubezval@gmail.com>
To: Pankaj Jangra <jangra.pankaj9@gmail.com>
Cc: Anson Huang <b20788@freescale.com>,
	linux-pm@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	rui.zhang@intel.com
Subject: Re: [PATCH] Thermal: imx: add clk disable/enable for suspend/resume
Date: Sat, 3 Jan 2015 21:00:53 -0400	[thread overview]
Message-ID: <20150104010051.GA26438@developer> (raw)
In-Reply-To: <CADTbHxpExF7Qzz9-HCVWWbU24ymBV1wLt4ON_6avY_oLkknFaQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2137 bytes --]

Hello,

On Mon, Jan 05, 2015 at 10:34:11PM +0530, Pankaj Jangra wrote:
> Hi Anson,
> 
> On Mon, Jan 5, 2015 at 7:59 PM, Anson Huang <b20788@freescale.com> wrote:
> 
> > Thermal sensor's clk is from pll3_usb_otg, per hardware
> > design requirement, need to make sure pll3_usb_otg is disabled
> > before STOP mode is entered, otherwise, all PFDs under it may
> > enter incorrect state, this patch disables pll3_usb_otg before
> > suspend and enables it after resume.
> >
> > Signed-off-by: Anson Huang <b20788@freescale.com>
> >
> > +++ b/drivers/thermal/imx_thermal.c
> > @@ -600,6 +600,8 @@ static int imx_thermal_suspend(struct device *dev)
> >         regmap_write(map, TEMPSENSE0 + REG_CLR, TEMPSENSE0_MEASURE_TEMP);
> >         regmap_write(map, TEMPSENSE0 + REG_SET, TEMPSENSE0_POWER_DOWN);
> >         data->mode = THERMAL_DEVICE_DISABLED;
> > +       if (!IS_ERR(data->thermal_clk))
> >
> I think you do not need to check for the error condition here. Because
> during the probe of driver, this condition is already checked and if the
> clock get is failed,
> it will fail the driver probing itself.
> 

Agreed here, no need for this extra check.

> +               clk_disable_unprepare(data->thermal_clk);
> 
> 
> >         return 0;
> >  }
> > @@ -609,6 +611,8 @@ static int imx_thermal_resume(struct device *dev)
> >         struct imx_thermal_data *data = dev_get_drvdata(dev);
> >         struct regmap *map = data->tempmon;
> >
> > +       if (!IS_ERR(data->thermal_clk))
> >
> Same as above.
> 
> > +               clk_prepare_enable(data->thermal_clk);
> >         /* Enabled thermal sensor after resume */
> >         regmap_write(map, TEMPSENSE0 + REG_CLR, TEMPSENSE0_POWER_DOWN);
> >         regmap_write(map, TEMPSENSE0 + REG_SET, TEMPSENSE0_MEASURE_TEMP);
> > --
> >
> 
> Else changes looks good to me.
> 
> -- Pankaj Jangra
> 
> > 1.9.1
> >
> > --
> > 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
> >

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

      parent reply	other threads:[~2015-01-05 19:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 14:29 [PATCH] Thermal: imx: add clk disable/enable for suspend/resume Anson Huang
     [not found] ` <CADTbHxpExF7Qzz9-HCVWWbU24ymBV1wLt4ON_6avY_oLkknFaQ@mail.gmail.com>
2015-01-04  1:00   ` Eduardo Valentin [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=20150104010051.GA26438@developer \
    --to=edubezval@gmail.com \
    --cc=b20788@freescale.com \
    --cc=jangra.pankaj9@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rui.zhang@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;
as well as URLs for NNTP newsgroup(s).