From: zhangqing@rock-chips.com (Elaine Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/6] rockchip: power-domain: fix pm domain for support RK3399 SoC
Date: Thu, 18 Feb 2016 11:07:12 +0800 [thread overview]
Message-ID: <1455764838-12928-1-git-send-email-zhangqing@rock-chips.com> (raw)
fix some idle handling
support sub-power domain
add rk3399-power.h
modify power domain for RK3399 SoC
modify document for RK3399 Soc
Elaine Zhang (6):
rockchip: power-domain: make idle handling optional
rockchip: power-domain: allow domains only handling idle requests
rockchip: power-domain: add support for sub-power domains
dt/bindings: power: add RK3399 SoCs header for power-domain
rockchip: power-domain: Modify power domain driver for rk3399
dt/bindings: rockchip: modify document of Rockchip power domains
.../bindings/soc/rockchip/power_domain.txt | 21 ++++
drivers/soc/rockchip/pm_domains.c | 131 ++++++++++++++++++++-
include/dt-bindings/power/rk3399-power.h | 53 +++++++++
3 files changed, 200 insertions(+), 5 deletions(-)
create mode 100644 include/dt-bindings/power/rk3399-power.h
--
1.9.1
next reply other threads:[~2016-02-18 3:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 3:07 Elaine Zhang [this message]
2016-02-18 3:07 ` [PATCH v2 1/6] rockchip: power-domain: make idle handling optional Elaine Zhang
2016-02-19 0:05 ` Heiko Stuebner
2016-02-18 3:07 ` [PATCH v2 2/6] rockchip: power-domain: allow domains only handling idle requests Elaine Zhang
2016-02-18 3:07 ` [PATCH v2 3/6] rockchip: power-domain: add support for sub-power domains Elaine Zhang
2016-02-19 0:20 ` Heiko Stuebner
2016-03-03 0:05 ` Kevin Hilman
2016-02-18 3:07 ` [PATCH v2 4/6] dt/bindings: power: add RK3399 SoCs header for power-domain Elaine Zhang
2016-02-18 23:48 ` [PATCH v2 0/6] rockchip: power-domain: fix pm domain for support RK3399 SoC Heiko Stuebner
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=1455764838-12928-1-git-send-email-zhangqing@rock-chips.com \
--to=zhangqing@rock-chips.com \
--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).