From: Heiko Stuebner <heiko@sntech.de>
To: Elaine Zhang <zhangqing@rock-chips.com>,
Kevin Hilman <khilman@baylibre.com>
Cc: wxt@rock-chips.com, linux-arm-kernel@lists.infradead.org,
huangtao@rock-chips.com, zyw@rock-chips.com, xxx@rock-chips.com,
jay.xu@rock-chips.com, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/6] rockchip: power-domain: add support for sub-power domains
Date: Fri, 19 Feb 2016 01:20:03 +0100 [thread overview]
Message-ID: <1828664.WUMlfLyMuz@phil> (raw)
In-Reply-To: <1455764838-12928-4-git-send-email-zhangqing@rock-chips.com>
Hi Elaine,
Am Donnerstag, 18. Februar 2016, 11:07:15 schrieb Elaine Zhang:
> This patch adds support for making one power domain a sub-domain of
> other domain. This is useful for modeling power dependences,
> which needs to have more than one power domain enabled to be operational.
>
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
> ---
> drivers/soc/rockchip/pm_domains.c | 54
> +++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+)
>
> diff --git a/drivers/soc/rockchip/pm_domains.c
> b/drivers/soc/rockchip/pm_domains.c index 350527b..8cdf1b2 100644
> --- a/drivers/soc/rockchip/pm_domains.c
> +++ b/drivers/soc/rockchip/pm_domains.c
> @@ -372,6 +372,54 @@ static void rockchip_configure_pd_cnt(struct
> rockchip_pmu *pmu, regmap_write(pmu->regmap, domain_reg_offset + 4,
> count);
> }
>
> +static int rockchip_pm_add_subdomain(struct rockchip_pmu *pmu,
> + struct device_node *parent)
> +{
> + struct device_node *np;
> + int error;
> +
> + for_each_child_of_node(parent, np) {
> + struct generic_pm_domain *child_domain, *parent_domain;
> + u32 idx = ~0;
> +
> + if (of_property_read_u32(parent, "reg", &idx)) {
> + dev_err(pmu->dev,
> + "%s: failed to retrieve domain id (reg)\n",
> + parent->name);
> + of_node_put(parent);
> + return -EINVAL;
> + }
> + parent_domain = pmu->genpd_data.domains[idx];
> +
> + error = rockchip_pm_add_one_domain(pmu, np);
> + if (error) {
> + dev_err(pmu->dev, "failed to handle node %s: %d\n",
> + np->name, error);
> + of_node_put(np);
> + return -ENODEV;
> + }
> +
> + if (of_property_read_u32(np, "reg", &idx)) {
> + dev_err(pmu->dev,
> + "%s: failed to retrieve domain id (reg)\n",
> + np->name);
> + of_node_put(np);
> + return -EINVAL;
> + }
> + child_domain = pmu->genpd_data.domains[idx];
> +
> + if (pm_genpd_add_subdomain(parent_domain, child_domain))
> + pr_warn("%s failed to add subdomain: %s\n",
> + parent_domain->name, child_domain->name);
should probably be dev_err here
> + else
> + pr_warn("%s add subdomain: %s\n",
> + parent_domain->name, child_domain->name);
you don't need pr_warn / dev_warn on sucess
> +
> + rockchip_pm_add_subdomain(pmu, np);
> + }
> + return 0;
> +}
> +
In general the code looks like you're going to group the domains
hirarchically, like
power: power-controller {
compatible = "rockchip,rk3399-power-controller";
pd_cci {
reg = <RK3399_PD_CCI>;
clocks = ...;
pd_cci0 {
reg = <RK3399_PD_CCI0>;
clocks = ...;
};
};
};
This isn't documented in the dt-binding and also isn't really improving
reading these declarations. Instead as I said before, I think I'd like more
get inspiration from how Exynos is doing that already (arch/arm/mach-
exynos/pm_domains.c at "Assign the child power domains to their parents")
simply declaring an additional power-domains property like:
power: power-controller {
compatible = "rockchip,rk3399-power-controller";
pd_cci {
reg = <RK3399_PD_CCI>;
clocks = ...;
};
pd_cci0 {
reg = <RK3399_PD_CCI0>;
clocks = ...;
power-domains = <&power RK3399_PD_CCI>;
};
};
> static int rockchip_pm_domain_probe(struct platform_device *pdev)
> {
> struct device *dev = &pdev->dev;
> @@ -437,6 +485,12 @@ static int rockchip_pm_domain_probe(struct
> platform_device *pdev) node->name, error);
> goto err_out;
> }
blank line here
> + error = rockchip_pm_add_subdomain(pmu, node);
> + if (error < 0) {
> + dev_err(dev, "failed to handle subdomain node %s: %d\n",
> + node->name, error);
> + goto err_out;
> + }
> }
>
> if (error) {
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/6] rockchip: power-domain: add support for sub-power domains
Date: Fri, 19 Feb 2016 01:20:03 +0100 [thread overview]
Message-ID: <1828664.WUMlfLyMuz@phil> (raw)
In-Reply-To: <1455764838-12928-4-git-send-email-zhangqing@rock-chips.com>
Hi Elaine,
Am Donnerstag, 18. Februar 2016, 11:07:15 schrieb Elaine Zhang:
> This patch adds support for making one power domain a sub-domain of
> other domain. This is useful for modeling power dependences,
> which needs to have more than one power domain enabled to be operational.
>
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
> ---
> drivers/soc/rockchip/pm_domains.c | 54
> +++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+)
>
> diff --git a/drivers/soc/rockchip/pm_domains.c
> b/drivers/soc/rockchip/pm_domains.c index 350527b..8cdf1b2 100644
> --- a/drivers/soc/rockchip/pm_domains.c
> +++ b/drivers/soc/rockchip/pm_domains.c
> @@ -372,6 +372,54 @@ static void rockchip_configure_pd_cnt(struct
> rockchip_pmu *pmu, regmap_write(pmu->regmap, domain_reg_offset + 4,
> count);
> }
>
> +static int rockchip_pm_add_subdomain(struct rockchip_pmu *pmu,
> + struct device_node *parent)
> +{
> + struct device_node *np;
> + int error;
> +
> + for_each_child_of_node(parent, np) {
> + struct generic_pm_domain *child_domain, *parent_domain;
> + u32 idx = ~0;
> +
> + if (of_property_read_u32(parent, "reg", &idx)) {
> + dev_err(pmu->dev,
> + "%s: failed to retrieve domain id (reg)\n",
> + parent->name);
> + of_node_put(parent);
> + return -EINVAL;
> + }
> + parent_domain = pmu->genpd_data.domains[idx];
> +
> + error = rockchip_pm_add_one_domain(pmu, np);
> + if (error) {
> + dev_err(pmu->dev, "failed to handle node %s: %d\n",
> + np->name, error);
> + of_node_put(np);
> + return -ENODEV;
> + }
> +
> + if (of_property_read_u32(np, "reg", &idx)) {
> + dev_err(pmu->dev,
> + "%s: failed to retrieve domain id (reg)\n",
> + np->name);
> + of_node_put(np);
> + return -EINVAL;
> + }
> + child_domain = pmu->genpd_data.domains[idx];
> +
> + if (pm_genpd_add_subdomain(parent_domain, child_domain))
> + pr_warn("%s failed to add subdomain: %s\n",
> + parent_domain->name, child_domain->name);
should probably be dev_err here
> + else
> + pr_warn("%s add subdomain: %s\n",
> + parent_domain->name, child_domain->name);
you don't need pr_warn / dev_warn on sucess
> +
> + rockchip_pm_add_subdomain(pmu, np);
> + }
> + return 0;
> +}
> +
In general the code looks like you're going to group the domains
hirarchically, like
power: power-controller {
compatible = "rockchip,rk3399-power-controller";
pd_cci {
reg = <RK3399_PD_CCI>;
clocks = ...;
pd_cci0 {
reg = <RK3399_PD_CCI0>;
clocks = ...;
};
};
};
This isn't documented in the dt-binding and also isn't really improving
reading these declarations. Instead as I said before, I think I'd like more
get inspiration from how Exynos is doing that already (arch/arm/mach-
exynos/pm_domains.c at "Assign the child power domains to their parents")
simply declaring an additional power-domains property like:
power: power-controller {
compatible = "rockchip,rk3399-power-controller";
pd_cci {
reg = <RK3399_PD_CCI>;
clocks = ...;
};
pd_cci0 {
reg = <RK3399_PD_CCI0>;
clocks = ...;
power-domains = <&power RK3399_PD_CCI>;
};
};
> static int rockchip_pm_domain_probe(struct platform_device *pdev)
> {
> struct device *dev = &pdev->dev;
> @@ -437,6 +485,12 @@ static int rockchip_pm_domain_probe(struct
> platform_device *pdev) node->name, error);
> goto err_out;
> }
blank line here
> + error = rockchip_pm_add_subdomain(pmu, node);
> + if (error < 0) {
> + dev_err(dev, "failed to handle subdomain node %s: %d\n",
> + node->name, error);
> + goto err_out;
> + }
> }
>
> if (error) {
next prev parent reply other threads:[~2016-02-19 0:20 UTC|newest]
Thread overview: 21+ 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 ` Elaine Zhang
2016-02-18 3:07 ` Elaine Zhang
2016-02-18 3:07 ` [PATCH v2 1/6] rockchip: power-domain: make idle handling optional Elaine Zhang
2016-02-18 3:07 ` Elaine Zhang
[not found] ` <1455764838-12928-2-git-send-email-zhangqing-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-02-19 0:05 ` Heiko Stuebner
2016-02-19 0:05 ` Heiko Stuebner
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 ` Elaine Zhang
[not found] ` <1455764838-12928-1-git-send-email-zhangqing-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-02-18 3:07 ` [PATCH v2 3/6] rockchip: power-domain: add support for sub-power domains Elaine Zhang
2016-02-18 3:07 ` Elaine Zhang
2016-02-18 3:07 ` Elaine Zhang
2016-02-19 0:20 ` Heiko Stuebner [this message]
2016-02-19 0:20 ` Heiko Stuebner
2016-03-03 0:05 ` Kevin Hilman
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 3:07 ` Elaine Zhang
2016-02-18 23:48 ` [PATCH v2 0/6] rockchip: power-domain: fix pm domain for support RK3399 SoC Heiko Stuebner
2016-02-18 23:48 ` 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=1828664.WUMlfLyMuz@phil \
--to=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=jay.xu@rock-chips.com \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=wxt@rock-chips.com \
--cc=xxx@rock-chips.com \
--cc=zhangqing@rock-chips.com \
--cc=zyw@rock-chips.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.