From mboxrd@z Thu Jan 1 00:00:00 1970 From: santosh.shilimkar@ti.com (Santosh Shilimkar) Date: Thu, 20 Dec 2012 17:36:35 +0530 Subject: [PATCH V3 1/5] ARM: tegra: add pending SGI checking API In-Reply-To: <20121220111409.GH19258@tbergstrom-lnx.Nvidia.com> References: <1355797861-12759-1-git-send-email-josephl@nvidia.com> <1355797861-12759-2-git-send-email-josephl@nvidia.com> <20121218101548.GO19258@tbergstrom-lnx.Nvidia.com> <50D2BB51.9000109@ti.com> <20121220093412.GE19258@tbergstrom-lnx.Nvidia.com> <50D2DF45.1000305@ti.com> <20121220095951.GG19258@tbergstrom-lnx.Nvidia.com> <50D2E76C.7050309@ti.com> <20121220111409.GH19258@tbergstrom-lnx.Nvidia.com> Message-ID: <50D2FF4B.5010401@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thursday 20 December 2012 04:44 PM, Peter De Schrijver wrote: >>> >>> So why does OMAP4 have working coupled idle without the SGI check then? >>> >> Because whenever the OMAP4 CPUs enter into any power states apart from >> ON, clock-domain force wakeup method us being used to wakeup >> secondary CPUs. And secondly CPU RET is not supported on purpose because >> of some known IP block issues. >> > > Aha. That explains indeed why you don't need the check. > Just for the information on OMAP5 SOC, CPU RET is supported and the couple idle works on it without IPI. As I mentioned, we do use clock-domain force wakeup method for wakeup. Code is out of the tree hence i didn't mention that in first place. Regards Santosh