From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/6] rockchip: power-domain: make idle handling optional
Date: Fri, 19 Feb 2016 01:05:38 +0100 [thread overview]
Message-ID: <291170080.OevJ1dsWVH@phil> (raw)
In-Reply-To: <1455764838-12928-2-git-send-email-zhangqing@rock-chips.com>
Am Donnerstag, 18. Februar 2016, 11:07:13 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>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
What's up with the Signed-off-bys? I remember creating the draft of this
change, so either my authorship of the patch should be retained or the
Signed-off-by with my name removed :-)
git send-email will keep patch authorship nicely.
> ---
> drivers/soc/rockchip/pm_domains.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/soc/rockchip/pm_domains.c
> b/drivers/soc/rockchip/pm_domains.c index 6cdffb1..3dcc611 100644
> --- a/drivers/soc/rockchip/pm_domains.c
> +++ b/drivers/soc/rockchip/pm_domains.c
> @@ -63,14 +63,16 @@ struct rockchip_pmu {
> };
>
> #define to_rockchip_pd(gpd) container_of(gpd, struct rockchip_pm_domain,
> genpd) +#define NULL_BIT -32
> +#define OVERFLOW_MASK 32
I don't really understand why you need this NULL_BIT / OVERFLOW_MASK.
Defining the unset things to -1 should work nicely as well and is already
regularly used elsewhere - so people will already know this scheme. That way
you also don't need to introduce two new constants someone will have to look
up later.
>
> #define DOMAIN(pwr, status, req, idle, ack) \
> { \
> .pwr_mask = BIT(pwr), \
> .status_mask = BIT(status), \
> - .req_mask = BIT(req), \
> - .idle_mask = BIT(idle), \
> - .ack_mask = BIT(ack), \
> + .req_mask = (req >= 0) ? BIT(req) : OVERFLOW_MASK, \
> + .idle_mask = (idle >= 0) ? BIT(idle) : OVERFLOW_MASK, \
> + .ack_mask = (ack >= 0) ? BIT(ack) : OVERFLOW_MASK, \
> }
>
> #define DOMAIN_RK3288(pwr, status, req) \
> @@ -96,6 +98,9 @@ static int rockchip_pmu_set_idle_request(struct
> rockchip_pm_domain *pd, struct rockchip_pmu *pmu = pd->pmu;
> unsigned int val;
>
> + if (pd_info->req_mask >= OVERFLOW_MASK)
> + return 0;
> +
> regmap_update_bits(pmu->regmap, pmu->info->req_offset,
> pd_info->req_mask, idle ? -1U : 0);
next prev parent reply other threads:[~2016-02-19 0:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 3:07 [PATCH v2 0/6] rockchip: power-domain: fix pm domain for support RK3399 SoC Elaine Zhang
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 [this message]
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=291170080.OevJ1dsWVH@phil \
--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).