From: Caesar Wang <wxt@rock-chips.com>
To: "Russell King - ARM Linux" <linux@arm.linux.org.uk>,
"Heiko Stuebner" <heiko@sntech.de>,
杨凯 <kever.yang@rock-chips.com>
Cc: dianders@chromium.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/3] ARM: rockchip: fix the CPU soft reset
Date: Tue, 09 Jun 2015 08:43:56 +0800 [thread overview]
Message-ID: <557636CC.6010809@rock-chips.com> (raw)
In-Reply-To: <20150608094334.GX7557@n2100.arm.linux.org.uk>
在 2015年06月08日 17:43, Russell King - ARM Linux 写道:
> On Mon, Jun 08, 2015 at 03:11:34PM +0800, Caesar Wang wrote:
>> diff --git a/arch/arm/mach-rockchip/platsmp.c b/arch/arm/mach-rockchip/platsmp.c
>> index 5b4ca3c..bd40852 100644
>> --- a/arch/arm/mach-rockchip/platsmp.c
>> +++ b/arch/arm/mach-rockchip/platsmp.c
>> @@ -72,6 +72,7 @@ static struct reset_control *rockchip_get_core_reset(int cpu)
>> static int pmu_set_power_domain(int pd, bool on)
>> {
>> u32 val = (on) ? 0 : BIT(pd);
>> + struct reset_control *rstc = rockchip_get_core_reset(pd);
>> int ret;
>>
>> /*
>> @@ -80,20 +81,15 @@ static int pmu_set_power_domain(int pd, bool on)
>> * processor is powered down.
>> */
>> if (read_cpuid_part() != ARM_CPU_PART_CORTEX_A9) {
>> - struct reset_control *rstc = rockchip_get_core_reset(pd);
>> -
>> + /* We only require the reset on the RK3288 at the moment */
>> if (IS_ERR(rstc)) {
>> pr_err("%s: could not get reset control for core %d\n",
>> __func__, pd);
>> return PTR_ERR(rstc);
>> }
>>
>> - if (on)
>> - reset_control_deassert(rstc);
>> - else
>> + if (!on)
>> reset_control_assert(rstc);
>> -
>> - reset_control_put(rstc);
>> }
> Do we need the CPU part number check for the assertion/deassertion of
> the reset control? Surely the DT provides this where appropriate and
> omits it where it's inappropriate?
>
> If so, I'd separate out the decision whether to error out from the
> decision whether to assert the reset control, like this:
>
> if (IS_ERR(rstc) && read_cpuid_part() != ARM_CPU_PART_CORTEX_A9) {
> pr_err("%s: could not get reset control for core %d\n",
> __func__, pd);
> return PTR_ERR(rstc);
> }
>
> if (!IS_ERR(rstc) && !on)
> reset_control_assert(rstc);
>
> or maybe:
>
> if (IS_ERR(rstc) && PTR_ERR(rstc) != -ENOENT) {
> pr_err("%s: could not get reset control for core %d: %d\n",
> __func__, pd, PTR_ERR(rstc));
> return PTR_ERR(rstc);
> }
>
> if (!IS_ERR(rstc) && !on)
> reset_control_assert(rstc);
>
> which lets you detect whether of_reset_control_get() failed because the
> reset control was not present (and thus not required) vs failed for some
> other reason - and this means that the issue of whether the reset
> control is used is entirely up to the supplied DT file.
Sound resonable for me.
I hope get the Heiko and Kever option.
After all the code is uploaded by Heiko and Kever.
>>
>> ret = regmap_update_bits(pmu, PMU_PWRDN_CON, BIT(pd), val);
>> @@ -112,6 +108,12 @@ static int pmu_set_power_domain(int pd, bool on)
>> }
>> }
>>
>> + if (read_cpuid_part() != ARM_CPU_PART_CORTEX_A9 && on)
>> + reset_control_deassert(rstc);
>> +
>> + if (!IS_ERR(rstc))
>> + reset_control_put(rstc);
>> +
> and here:
> if (!IS_ERR(rstc)) {
> if (on)
> reset_control_deassert(rstc);
> reset_control_put(rstc);
> }
Ditto.
--
Thanks,
- Caesar
WARNING: multiple messages have this Message-ID (diff)
From: wxt@rock-chips.com (Caesar Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/3] ARM: rockchip: fix the CPU soft reset
Date: Tue, 09 Jun 2015 08:43:56 +0800 [thread overview]
Message-ID: <557636CC.6010809@rock-chips.com> (raw)
In-Reply-To: <20150608094334.GX7557@n2100.arm.linux.org.uk>
? 2015?06?08? 17:43, Russell King - ARM Linux ??:
> On Mon, Jun 08, 2015 at 03:11:34PM +0800, Caesar Wang wrote:
>> diff --git a/arch/arm/mach-rockchip/platsmp.c b/arch/arm/mach-rockchip/platsmp.c
>> index 5b4ca3c..bd40852 100644
>> --- a/arch/arm/mach-rockchip/platsmp.c
>> +++ b/arch/arm/mach-rockchip/platsmp.c
>> @@ -72,6 +72,7 @@ static struct reset_control *rockchip_get_core_reset(int cpu)
>> static int pmu_set_power_domain(int pd, bool on)
>> {
>> u32 val = (on) ? 0 : BIT(pd);
>> + struct reset_control *rstc = rockchip_get_core_reset(pd);
>> int ret;
>>
>> /*
>> @@ -80,20 +81,15 @@ static int pmu_set_power_domain(int pd, bool on)
>> * processor is powered down.
>> */
>> if (read_cpuid_part() != ARM_CPU_PART_CORTEX_A9) {
>> - struct reset_control *rstc = rockchip_get_core_reset(pd);
>> -
>> + /* We only require the reset on the RK3288 at the moment */
>> if (IS_ERR(rstc)) {
>> pr_err("%s: could not get reset control for core %d\n",
>> __func__, pd);
>> return PTR_ERR(rstc);
>> }
>>
>> - if (on)
>> - reset_control_deassert(rstc);
>> - else
>> + if (!on)
>> reset_control_assert(rstc);
>> -
>> - reset_control_put(rstc);
>> }
> Do we need the CPU part number check for the assertion/deassertion of
> the reset control? Surely the DT provides this where appropriate and
> omits it where it's inappropriate?
>
> If so, I'd separate out the decision whether to error out from the
> decision whether to assert the reset control, like this:
>
> if (IS_ERR(rstc) && read_cpuid_part() != ARM_CPU_PART_CORTEX_A9) {
> pr_err("%s: could not get reset control for core %d\n",
> __func__, pd);
> return PTR_ERR(rstc);
> }
>
> if (!IS_ERR(rstc) && !on)
> reset_control_assert(rstc);
>
> or maybe:
>
> if (IS_ERR(rstc) && PTR_ERR(rstc) != -ENOENT) {
> pr_err("%s: could not get reset control for core %d: %d\n",
> __func__, pd, PTR_ERR(rstc));
> return PTR_ERR(rstc);
> }
>
> if (!IS_ERR(rstc) && !on)
> reset_control_assert(rstc);
>
> which lets you detect whether of_reset_control_get() failed because the
> reset control was not present (and thus not required) vs failed for some
> other reason - and this means that the issue of whether the reset
> control is used is entirely up to the supplied DT file.
Sound resonable for me.
I hope get the Heiko and Kever option.
After all the code is uploaded by Heiko and Kever.
>>
>> ret = regmap_update_bits(pmu, PMU_PWRDN_CON, BIT(pd), val);
>> @@ -112,6 +108,12 @@ static int pmu_set_power_domain(int pd, bool on)
>> }
>> }
>>
>> + if (read_cpuid_part() != ARM_CPU_PART_CORTEX_A9 && on)
>> + reset_control_deassert(rstc);
>> +
>> + if (!IS_ERR(rstc))
>> + reset_control_put(rstc);
>> +
> and here:
> if (!IS_ERR(rstc)) {
> if (on)
> reset_control_deassert(rstc);
> reset_control_put(rstc);
> }
Ditto.
--
Thanks,
- Caesar
next prev parent reply other threads:[~2015-06-09 0:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 7:11 [PATCH v5 0/3] ARM: rockchip: fix the SMP Caesar Wang
2015-06-08 7:11 ` Caesar Wang
2015-06-08 7:11 ` [PATCH v5 1/3] ARM: rockchip: fix the CPU soft reset Caesar Wang
2015-06-08 7:11 ` Caesar Wang
2015-06-08 7:51 ` Caesar Wang
2015-06-08 7:51 ` Caesar Wang
2015-06-08 9:24 ` Russell King - ARM Linux
2015-06-08 9:24 ` Russell King - ARM Linux
2015-06-08 21:54 ` Caesar Wang
2015-06-08 21:54 ` Caesar Wang
2015-06-09 9:55 ` Caesar Wang
2015-06-09 9:55 ` Caesar Wang
2015-06-08 9:43 ` Russell King - ARM Linux
2015-06-08 9:43 ` Russell King - ARM Linux
2015-06-09 0:43 ` Caesar Wang [this message]
2015-06-09 0:43 ` Caesar Wang
2015-06-09 7:46 ` Heiko Stübner
2015-06-09 7:46 ` Heiko Stübner
2015-06-08 7:11 ` [PATCH v5 2/3] ARM: rockchip: ensure CPU to enter WFI/WFE state Caesar Wang
2015-06-08 7:11 ` Caesar Wang
2015-06-08 9:28 ` Russell King - ARM Linux
2015-06-08 9:28 ` Russell King - ARM Linux
2015-06-09 0:40 ` Caesar Wang
2015-06-09 0:40 ` Caesar Wang
2015-06-08 7:11 ` [PATCH v5 3/3] ARM: rockchip: fix the SMP code style Caesar Wang
2015-06-08 7:11 ` Caesar Wang
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=557636CC.6010809@rock-chips.com \
--to=wxt@rock-chips.com \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=heiko@sntech.de \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
/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.