From: Roger Quadros <rogerq@ti.com>
To: <kishon@ti.com>, <tony@atomide.com>
Cc: <nm@ti.com>, <nsekhar@ti.com>, <balbi@ti.com>,
<grygorii.strashko@ti.com>, <linux-kernel@vger.kernel.org>,
<linux-omap@vger.kernel.org>, Roger Quadros <rogerq@ti.com>
Subject: [PATCH v2 0/3] phy: ti-pipe3: dra7: sata: allow suspend to RAM (core-retention)
Date: Tue, 2 Jun 2015 12:10:39 +0300 [thread overview]
Message-ID: <1433236242-26172-1-git-send-email-rogerq@ti.com> (raw)
Hi,
We fix 2 things here to ensure that PHY clocks are disabled during
system suspend.
1) Stop relying on pm_runtime ops to disable our clocks as they don't
fit in well with the PHY framework usage scenario. This ensures that all clocks are
disabled when phy_exit() is called.
2) Implement workaround for SATA errata i783 (SATA Lockup After SATA DPLL Unlock/Relock)
so that we can now turn off sata_refclk to support suspend-to-ram without preventing
core-retention.
Changelog:
v2:
- Fixed pcie disable_clocks. Addressed review comments.
cheers,
-roger
Roger Quadros (3):
phy: ti-pipe3: fix suspend
phy: ti-pipe3: i783 workaround for SATA lockup after dpll
unlock/relock
ARM: dts: dra7: Add syscon-pllreset syscon to SATA PHY
Documentation/devicetree/bindings/phy/ti-phy.txt | 16 ++
arch/arm/boot/dts/dra7.dtsi | 1 +
drivers/phy/phy-ti-pipe3.c | 217 +++++++++--------------
3 files changed, 105 insertions(+), 129 deletions(-)
--
2.1.4
next reply other threads:[~2015-06-02 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 9:10 Roger Quadros [this message]
2015-06-02 9:10 ` [PATCH v2 1/3] phy: ti-pipe3: fix suspend Roger Quadros
2015-06-02 9:10 ` [PATCH v2 2/3] phy: ti-pipe3: i783 workaround for SATA lockup after dpll unlock/relock Roger Quadros
2015-06-02 9:10 ` [PATCH v2 3/3] ARM: dts: dra7: Add syscon-pllreset syscon to SATA PHY Roger Quadros
2015-07-15 11:21 ` Kishon Vijay Abraham I
2015-07-15 12:07 ` Tony Lindgren
2015-07-15 13:47 ` Roger Quadros
2015-07-15 14:59 ` 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=1433236242-26172-1-git-send-email-rogerq@ti.com \
--to=rogerq@ti.com \
--cc=balbi@ti.com \
--cc=grygorii.strashko@ti.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®