From: Jon Hunter <jonathanh@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
Alexandre Courbot <gnurou@gmail.com>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 1/3] soc/tegra: pmc: Initialise power partitions early
Date: Thu, 30 Jun 2016 11:20:29 +0100 [thread overview]
Message-ID: <5774F26D.5050008@nvidia.com> (raw)
In-Reply-To: <20160630101732.GG1776@ulmo.ba.sec>
On 30/06/16 11:17, Thierry Reding wrote:
> * PGP Signed by an unknown key
>
> On Tue, Jun 28, 2016 at 12:20:42PM +0100, Jon Hunter wrote:
>> If CONFIG_PM_GENERIC_DOMAINS is not enabled, then power partitions
>> associated with a device will not be enabled automatically by the PM
>> core when the device is in use. To avoid situations where a device in
>> a power partition is to be used but the partition is not enabled,
>> initialise the power partitions for Tegra early in the boot process and
>> if CONFIG_PM_GENERIC_DOMAINS is not enabled, then power on all
>> partitions defined in the device-tree blob.
>>
>> Note that if CONFIG_PM_GENERIC_DOMAINS is not enabled, after the
>> partitions are turned on, the clocks and resets used as part of the
>> sequence for turning on the partition are released again as they are no
>> longer needed by the PMC driver. Another benefit of this is that this
>> avoids any issues of sharing resets between the PMC driver and other
>> device drivers that may wish to independently control a particular
>> reset.
>>
>> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
>> ---
>> drivers/soc/tegra/pmc.c | 33 ++++++++++++++++++++++-----------
>> 1 file changed, 22 insertions(+), 11 deletions(-)
>>
>> diff --git a/drivers/soc/tegra/pmc.c b/drivers/soc/tegra/pmc.c
>> index 1f702538f8ec..64678ff2173e 100644
>> --- a/drivers/soc/tegra/pmc.c
>> +++ b/drivers/soc/tegra/pmc.c
>> @@ -788,7 +788,7 @@ error:
>> static void tegra_powergate_add(struct tegra_pmc *pmc, struct device_node *np)
>> {
>> struct tegra_powergate *pg;
>> - bool off;
>> + bool off, err = true;
>> int id;
>>
>> pg = kzalloc(sizeof(*pg), GFP_KERNEL);
>> @@ -819,6 +819,9 @@ static void tegra_powergate_add(struct tegra_pmc *pmc, struct device_node *np)
>> if (tegra_powergate_of_get_resets(pg, np, off))
>> goto remove_clks;
>>
>> + if (!IS_ENABLED(CONFIG_PM_GENERIC_DOMAINS))
>> + goto power_on_cleanup;
>> +
>> pm_genpd_init(&pg->genpd, NULL, off);
>>
>> if (of_genpd_add_provider_simple(np, &pg->genpd))
>> @@ -828,6 +831,11 @@ static void tegra_powergate_add(struct tegra_pmc *pmc, struct device_node *np)
>>
>> return;
>>
>> +power_on_cleanup:
>> + if (off)
>> + WARN_ON(tegra_powergate_power_up(pg, true));
>> + err = false;
>> +
>> remove_resets:
>> while (pg->num_resets--)
>> reset_control_put(pg->resets[pg->num_resets]);
>> @@ -845,14 +853,23 @@ free_mem:
>> kfree(pg);
>>
>> error:
>> - dev_err(pmc->dev, "failed to create power domain for %s\n", np->name);
>> + if (err)
>> + dev_err(pmc->dev, "failed to configure partition %s\n",
>> + np->name);
>
> This is beginning to look very spaghetti-like. Do we really need the
> error message here? Could we instead add more explicit error messages
> before the gotos above?
Yes I can't say I loved it either. Ok, yes will add more specific error
messages above gotos instead.
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2016-06-30 10:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 11:20 [RFC PATCH 0/3] soc/tegra: Turn on XUSB partitions Jon Hunter
2016-06-28 11:20 ` [RFC PATCH 1/3] soc/tegra: pmc: Initialise power partitions early Jon Hunter
2016-06-30 10:17 ` Thierry Reding
2016-06-30 10:20 ` Jon Hunter [this message]
2016-06-28 11:20 ` [RFC PATCH 2/3] soc/tegra: pmc: Enable XUSB partitions on boot Jon Hunter
2016-06-28 11:20 ` [RFC PATCH 3/3] arm64: tegra210: Add XUSB powergates Jon Hunter
2016-06-29 15:30 ` Jon Hunter
2016-06-29 15:56 ` Thierry Reding
2016-06-29 16:07 ` Jon Hunter
2016-06-30 10:20 ` Thierry Reding
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=5774F26D.5050008@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=gnurou@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).