From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 1/6] rockchip: power-domain: make idle handling optional
Date: Mon, 28 Mar 2016 12:09:28 +0200 [thread overview]
Message-ID: <15721662.qSX6841ZWS@diego> (raw)
In-Reply-To: <1457558578-22049-2-git-send-email-zhangqing@rock-chips.com>
Am Donnerstag, 10. M?rz 2016, 05:22:53 schrieb Elaine Zhang:
> Not all new socs need to handle idle states on domain state changes,
> so add the possibility to make them optional.
>
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
applied to my armsoc/drivers branch for 4.7
Thanks
Heiko
next prev parent reply other threads:[~2016-03-28 10:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 21:22 [RESEND PATCH v6 0/6] rockchip: power-domain: fix pm domain for support RK3399 SoC Elaine Zhang
2016-03-09 21:22 ` [PATCH v6 1/6] rockchip: power-domain: make idle handling optional Elaine Zhang
2016-03-28 10:09 ` Heiko Stübner [this message]
2016-03-09 21:22 ` [PATCH v6 2/6] power-domain: allow domains only handling idle requests Elaine Zhang
2016-03-28 10:09 ` Heiko Stübner
2016-03-09 21:22 ` [PATCH v6 3/6] rockchip: power-domain: add support for sub-power domains Elaine Zhang
2016-03-28 11:10 ` Heiko Stübner
2016-03-09 21:22 ` [PATCH v6 4/6] dt/bindings: power: add RK3399 SoCs header for power-domain Elaine Zhang
2016-03-28 11:18 ` Heiko Stübner
2016-03-09 21:24 ` [PATCH v6 5/6] dt/bindings: rockchip: modify document of Rockchip power domains Elaine Zhang
2016-03-12 20:22 ` Heiko Stübner
2016-03-28 11:18 ` Heiko Stübner
2016-03-09 21:24 ` [PATCH v6 6/6] rockchip: power-domain: Modify power domain driver for rk3399 Elaine Zhang
2016-03-28 11:19 ` Heiko Stübner
-- strict thread matches above, loose matches on Subject: below --
2016-03-09 21:00 [PATCH v6 0/6] rockchip: power-domain: fix pm domain for support RK3399 SoC Elaine Zhang
2016-03-09 21:00 ` [PATCH v6 1/6] rockchip: power-domain: make idle handling optional Elaine Zhang
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=15721662.qSX6841ZWS@diego \
--to=heiko@sntech.de \
--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).