From: Caesar Wang <wxt@rock-chips.com> To: Heiko Stuebner <heiko@sntech.de> Cc: dianders@chromium.org, Dmitry Torokhov <dmitry.torokhov@gmail.com>, linux-rockchip@lists.infradead.org, Caesar Wang <wxt@rock-chips.com>, Russell King <linux@arm.linux.org.uk>, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH v6 0/3] ARM: rockchip: fix the SMP Date: Tue, 9 Jun 2015 17:49:56 +0800 [thread overview] Message-ID: <1433843400-24831-1-git-send-email-wxt@rock-chips.com> (raw) Verified on url = https://chromium.googlesource.com/chromiumos/third_party/kernel/+/chromeos-3.14 Tested by 179200 cycles are pass with CPU up/dowm test scripts. Changes in v6: - As Russell suggestion, detect whether of_reset_control_get() failed - add the comment for 1ms delay. Series-changes: 5 - back to v2 cpu on/off flow, As Heiko point out in patch v3. - delay more time in rockchip_boot_secondary(). From CPU up/down tests, Needed more time to complete CPU process. In order to ensure a more, Here that be delayed 1ms. Series-changes: 4 - Add reset_control_put(rstc) for the non-error case. Series-changes: 3 - FIx the PATCH v2, it doesn't work on chromium 3.14. Series-changes: 2 - As Heiko suggestion, re-adjust the cpu on/off flow. CPU off: reset_control_assert regmap_update_bits(pmu, PMU_PWRDN_CON, BIT(pd), BIT(pd)) wait_for_power_domain_to_turn_off CPU on: regmap_update_bits(pmu, PMU_PWRDN_CON, BIT(pd), 0) wait_for_power_domain_to_turn_on reset_control_deassert - Fix the delay 1ms describing. Series-changes: 5 - Fix the patch decription. - Add the changelog. Series-changes: 2 - As Kever points out, Fix the subject typo WFI/WFE. - fix the commnet Unified format. Series-changes: 5 - Add the changelog. Series-changes: 2 - Use the checkpatch.pl -f --subjective to check. Caesar Wang (3): ARM: rockchip: fix the CPU soft reset ARM: rockchip: ensure CPU to enter WFI/WFE state ARM: rockchip: fix the SMP code style arch/arm/mach-rockchip/platsmp.c | 58 ++++++++++++++++++++++++---------------- 1 file changed, 35 insertions(+), 23 deletions(-) -- 1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: wxt@rock-chips.com (Caesar Wang) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v6 0/3] ARM: rockchip: fix the SMP Date: Tue, 9 Jun 2015 17:49:56 +0800 [thread overview] Message-ID: <1433843400-24831-1-git-send-email-wxt@rock-chips.com> (raw) Verified on url = https://chromium.googlesource.com/chromiumos/third_party/kernel/+/chromeos-3.14 Tested by 179200 cycles are pass with CPU up/dowm test scripts. Changes in v6: - As Russell suggestion, detect whether of_reset_control_get() failed - add the comment for 1ms delay. Series-changes: 5 - back to v2 cpu on/off flow, As Heiko point out in patch v3. - delay more time in rockchip_boot_secondary(). From CPU up/down tests, Needed more time to complete CPU process. In order to ensure a more, Here that be delayed 1ms. Series-changes: 4 - Add reset_control_put(rstc) for the non-error case. Series-changes: 3 - FIx the PATCH v2, it doesn't work on chromium 3.14. Series-changes: 2 - As Heiko suggestion, re-adjust the cpu on/off flow. CPU off: reset_control_assert regmap_update_bits(pmu, PMU_PWRDN_CON, BIT(pd), BIT(pd)) wait_for_power_domain_to_turn_off CPU on: regmap_update_bits(pmu, PMU_PWRDN_CON, BIT(pd), 0) wait_for_power_domain_to_turn_on reset_control_deassert - Fix the delay 1ms describing. Series-changes: 5 - Fix the patch decription. - Add the changelog. Series-changes: 2 - As Kever points out, Fix the subject typo WFI/WFE. - fix the commnet Unified format. Series-changes: 5 - Add the changelog. Series-changes: 2 - Use the checkpatch.pl -f --subjective to check. Caesar Wang (3): ARM: rockchip: fix the CPU soft reset ARM: rockchip: ensure CPU to enter WFI/WFE state ARM: rockchip: fix the SMP code style arch/arm/mach-rockchip/platsmp.c | 58 ++++++++++++++++++++++++---------------- 1 file changed, 35 insertions(+), 23 deletions(-) -- 1.9.1
next reply other threads:[~2015-06-09 9:50 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-09 9:49 Caesar Wang [this message] 2015-06-09 9:49 ` [PATCH v6 0/3] ARM: rockchip: fix the SMP Caesar Wang 2015-06-09 9:49 ` [PATCH v6 1/3] ARM: rockchip: fix the CPU soft reset Caesar Wang 2015-06-09 9:49 ` Caesar Wang 2015-06-09 9:49 ` Caesar Wang 2015-06-09 18:16 ` Doug Anderson 2015-06-09 18:16 ` Doug Anderson 2015-06-09 18:16 ` Doug Anderson 2015-06-10 5:58 ` Kever Yang 2015-06-10 5:58 ` Kever Yang 2015-06-09 9:49 ` [PATCH v6 2/3] ARM: rockchip: ensure CPU to enter WFI/WFE state Caesar Wang 2015-06-09 9:49 ` Caesar Wang 2015-06-09 18:13 ` Doug Anderson 2015-06-09 18:13 ` Doug Anderson 2015-06-09 18:13 ` Doug Anderson 2015-06-10 5:59 ` Kever Yang 2015-06-10 5:59 ` Kever Yang 2015-06-09 9:49 ` [PATCH v6 3/3] ARM: rockchip: fix the SMP code style Caesar Wang 2015-06-09 9:49 ` Caesar Wang 2015-06-09 18:17 ` Doug Anderson 2015-06-09 18:17 ` Doug Anderson 2015-06-09 18:17 ` Doug Anderson 2015-06-10 5:59 ` Kever Yang 2015-06-10 5:59 ` Kever Yang 2015-06-09 20:04 ` [PATCH v6 0/3] ARM: rockchip: fix the SMP Heiko Stübner 2015-06-09 20:04 ` Heiko Stübner 2015-06-13 21:02 ` Heiko Stübner 2015-06-13 21:02 ` Heiko Stübner
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=1433843400-24831-1-git-send-email-wxt@rock-chips.com \ --to=wxt@rock-chips.com \ --cc=dianders@chromium.org \ --cc=dmitry.torokhov@gmail.com \ --cc=heiko@sntech.de \ --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: linkBe 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.