From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org,
Marek Vasut <marek.vasut+renesas@gmail.com>,
Alexey Firago <alexey_firago@mentor.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] clk: vc5: Add suspend/resume support
Date: Wed, 05 Dec 2018 07:21:39 +0200 [thread overview]
Message-ID: <2439179.Yi0TbQOvfy@avalon> (raw)
In-Reply-To: <4f85447d-07b8-9f4c-ecb2-25d6834e6c5d@gmail.com>
Hi Marek,
On Wednesday, 5 December 2018 01:48:01 EET Marek Vasut wrote:
> On 12/04/2018 09:52 PM, Stephen Boyd wrote:
> > Quoting Marek Vasut (2018-12-04 10:27:21)
> >
> >> diff --git a/drivers/clk/clk-versaclock5.c
> >> b/drivers/clk/clk-versaclock5.c
> >> index decffb3826ec..ac90fb36af1a 100644
> >> --- a/drivers/clk/clk-versaclock5.c
> >> +++ b/drivers/clk/clk-versaclock5.c
> >> @@ -906,6 +906,39 @@ static int vc5_remove(struct i2c_client *client)
> >>
> >> return 0;
> >>
> >> }
> >>
> >> +#ifdef CONFIG_PM_SLEEP
> >> +static int vc5_suspend(struct device *dev)
> >
> > Please mark as __maybe_unused and drop the #ifdef CONFIG_PM_SLEEP
> >
> >> +{
> >> + struct vc5_driver_data *vc5 = dev_get_drvdata(dev);
> >> + int ret;
> >> +
> >> + ret = regcache_sync(vc5->regmap);
> >> + if (ret != 0) {
> >> + dev_err(dev, "Failed to save register map: %d\n", ret);
> >> + return ret;
> >
> > Do we need to block suspend if we can't save the register map away? Or
> > can we just throw up our hands and not restore on resume?
>
> Some hardware will fail on resume, so I'd say -- yes ?
But why do you need to sync on suspend in the first place ? What could cause
the map to be dirty at this stage, and require syncing before suspend, that
couldn't work with the sync be delayed to resume time ?
> The rest is fixed.
>
> >> + }
> >> + regcache_cache_only(vc5->regmap, true);
> >> + regcache_mark_dirty(vc5->regmap);
> >> +
> >> + return 0;
> >> +}
> >> +
> >> +static int vc5_resume(struct device *dev)
> >> +{
> >> + struct vc5_driver_data *vc5 = dev_get_drvdata(dev);
> >> + int ret;
> >> +
> >> + regcache_cache_only(vc5->regmap, false);
> >> + ret = regcache_sync(vc5->regmap);
> >> + if (ret != 0) {
> >> + dev_err(dev, "Failed to restore register map: %d\n",
> >> ret);
> >> + return ret;
> >> + }
> >
> > Simplify to
> >
> > if (ret)
> >
> > dev_err()
> >
> > retun ret;
> >
> >> +
> >> + return 0;
> >> +}
> >> +#endif
> >> +
> >>
> >> static const struct vc5_chip_info idt_5p49v5923_info = {
> >>
> >> .model = IDT_VC5_5P49V5923,
> >> .clk_fod_cnt = 2,
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2018-12-05 5:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 18:27 [PATCH] clk: vc5: Add suspend/resume support Marek Vasut
2018-12-04 20:52 ` Stephen Boyd
2018-12-04 23:48 ` Marek Vasut
2018-12-05 5:21 ` Laurent Pinchart [this message]
2018-12-05 12:29 ` Marek Vasut
2018-12-05 13:54 ` Laurent Pinchart
2018-12-05 14:21 ` Marek Vasut
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=2439179.Yi0TbQOvfy@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=alexey_firago@mentor.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=marek.vasut@gmail.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=sboyd@kernel.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