| Message ID | 1372152475-18617-10-git-send-email-josephl@nvidia.com |
|---|---|
| State | Superseded, archived |
| Headers | show |
There's a typo in the subject, it should be prefixed with "ARM: tegra:". Thierry
On Wed, 2013-06-26 at 18:48 +0800, Thierry Reding wrote: > * PGP Signed by an unknown key > > There's a typo in the subject, it should be prefixed with "ARM: tegra:". > Thanks for review. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 06/26/2013 04:48 AM, Thierry Reding wrote: > There's a typo in the subject, it should be prefixed with "ARM: > tegra:". Assuming there are no other issues, I can fix this up when applying. If the series gets reposted, please do fix it. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 06/25/2013 03:27 AM, Joseph Lo wrote:
> The Tegra114 can support suspend function now, removing the limitation.
OK, so this is the first point at which system suspend is enabled on
Tegra114. However, some of the changes in earlier patches sounded like
the might affect, or be required by, cpuidle too. Is that the case? If
so, can you assure me that bisectability of Tegra114 cpuidle is
maintained across this whole series?
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, 2013-06-27 at 03:40 +0800, Stephen Warren wrote: > On 06/25/2013 03:27 AM, Joseph Lo wrote: > > The Tegra114 can support suspend function now, removing the limitation. > > OK, so this is the first point at which system suspend is enabled on > Tegra114. However, some of the changes in earlier patches sounded like > the might affect, or be required by, cpuidle too. Is that the case? If > so, can you assure me that bisectability of Tegra114 cpuidle is > maintained across this whole series? I think you mean one of the patches I changed the init sequence of CPU idle driver and hook the "tegra_tear_down_cpu" in tegra_init_suspend (under pm.c). I did that was for fixing the dependence of CPU idle and suspend driver. Because we upstreamed the CPU idle "powered-down" support first then system suspend. So we hook the "tegra_tear_down_cpu" in CPU idle driver. But it would cause the system suspend function fail when disabling CPU_IDLE. After reorganizing the sequence, the system suspend is still working after disabling CPU_IDLE. If the PM is disabled, the CPU idle driver still supports at least WFI state. So this series is OK with cpuidle driver. I had tested the previous series (already merged in the branch for 3.11) is ok for Tegra20/30 as well. Thanks for take care. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/arch/arm/mach-tegra/pm.c b/arch/arm/mach-tegra/pm.c index a0668a2..94b1ee9 100644 --- a/arch/arm/mach-tegra/pm.c +++ b/arch/arm/mach-tegra/pm.c @@ -172,10 +172,6 @@ void tegra_idle_lp2_last(void) enum tegra_suspend_mode tegra_pm_validate_suspend_mode( enum tegra_suspend_mode mode) { - /* Tegra114 didn't support any suspending mode yet. */ - if (tegra_chip_id == TEGRA114) - return TEGRA_SUSPEND_NONE; - /* * The Tegra devices only support suspending to LP2 currently. */
The Tegra114 can support suspend function now, removing the limitation. Signed-off-by: Joseph Lo <josephl@nvidia.com> --- arch/arm/mach-tegra/pm.c | 4 ---- 1 file changed, 4 deletions(-)