From: Tony Lindgren <tony@atomide.com>
To: Keerthy <j-keerthy@ti.com>
Cc: t-kristo@ti.com, sboyd@kernel.org, linux-clk@vger.kernel.org,
d-gerlach@ti.com, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] clk: clk: Add functions to save/restore clock context en-masse
Date: Mon, 9 Jul 2018 22:56:05 -0700 [thread overview]
Message-ID: <20180710055605.GF99251@atomide.com> (raw)
In-Reply-To: <1529568907-19930-1-git-send-email-j-keerthy@ti.com>
* Keerthy <j-keerthy@ti.com> [180621 01:18]:
> Deep enough power saving mode can result into losing context of the clock
> registers also, and they need to be restored once coming back from the power
> saving mode. Hence add functions to save/restore clock context.
Patches 1 to 3 look good to me:
Acked-by: Tony Lindgren <tony@atomide.com>
Stephen, if no more comments, can you please set up an immutable
branch for me as otherwise the last patch might cause merge
conflicts?
Regards,
Tony
next prev parent reply other threads:[~2018-07-10 5:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 8:15 [PATCH v3 0/4] clk: clk: Add functions to save/restore clock context en-masse Keerthy
2018-06-21 8:15 ` Keerthy
2018-06-21 8:15 ` [PATCH v3 1/4] " Keerthy
2018-06-21 8:15 ` Keerthy
2018-06-21 8:15 ` [PATCH v3 2/4] clk: clk: Add clk_gate_restore_context function Keerthy
2018-06-21 8:15 ` Keerthy
2018-06-21 8:15 ` [PATCH v3 3/4] clk: ti: Add functions to save/restore clk context Keerthy
2018-06-21 8:15 ` Keerthy
2018-06-21 8:15 ` [PATCH v3 4/4] soc: ti: pm33xx: Save/restore clk context based on enable_off_mode setting Keerthy
2018-06-21 8:15 ` Keerthy
2018-07-10 5:56 ` Tony Lindgren [this message]
2018-08-13 15:25 ` [PATCH v3 0/4] clk: clk: Add functions to save/restore clock context en-masse Tero Kristo
2018-08-13 15:25 ` Tero Kristo
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=20180710055605.GF99251@atomide.com \
--to=tony@atomide.com \
--cc=d-gerlach@ti.com \
--cc=j-keerthy@ti.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=t-kristo@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.