| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 07 Aug 2014 19:18:43 +0200
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
To: Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: Kukjin Kim <kgene.kim@...sung.com>,
Tomasz Figa <t.figa@...sung.com>,
Sachin Kamat <sachin.kamat@...aro.org>,
Viresh Kumar <viresh.kumar@...aro.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Kyungmin Park <kyungmin.park@...sung.com>,
linux-samsung-soc@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, linaro-kernel@...ts.linaro.org
Subject: Re: [PATCH v5 0/5] ARM: EXYNOS: cpuidle: fix AFTR mode on boards with
secure firmware enabled
On Tuesday, August 05, 2014 03:50:54 PM Daniel Lezcano wrote:
> On 08/05/2014 03:34 PM, Bartlomiej Zolnierkiewicz wrote:
> > Hi,
> >
> > This patch series adds support for AFTR idle mode on boards with
> > secure firmware enabled and allows EXYNOS cpuidle driver usage on
> > Exynos4x12 SoCs.
> >
> > It has been tested on Trats2 board (using Exynos4412 SoC with secure
> > firmware enabled) on which AFTR mode reduces power consumption by ~12%
> > when EXYNOS cpuidle driver is enabled (in both cases the default
> > exynos_defconfig config is used and CPU1-3 are offlined).
>
> Hi Bartlomiej,
Hi Daniel,
> I tested your patchset on an odroid-u2. When the cpuidle driver is
> enabled and the cpu1-3 are offlined, the kernel hangs.
>
> If I disable the AFTR state on cpuidle, and offline the 1-3, it works as
> expected. So there is something wrong with the AFTR on the odroid board.
Thanks for testing. I reproduced the problem on ODROID-U3 board. I also
tested Exynos4412 based Origen board and it also has problem with AFTR mode.
We did some debugging but nothing specific has came up yet (we suspect that
the issue may be caused by incompatibilities of bootloader firmware of
ODROID-U2/U3 and Origen4412 boards). We will keep investigating this but
in the meantime I would like to have this patchset acked/merged if possible
(with Exynos4412 support limited to Trats2 target currently [*]) as:
- it contains mostly fundamental changes for all secure firmware enabled
boards (which would be needed also on ODROID/Origen4412 boards if we get
AFTR mode working on them)
- it adds working AFTR mode support for Exynos4412 Trats2 target
- it prepares support for Exynos4212 and Exynos3250 targets which are
working fine with AFTR mode in our internal kernels and which are not
yet upstreamed
[*] In the future it should be possible to enable AFTR mode support per
board using DT (basing on patches from Lorenzo), for now it should be
fine to check for Trats2 target directly while registering cpuidle
platform device. I will post v6 soon.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
> > Depends on:
> > - next-20140804 branch of linux-next kernel tree
> > - [PATCH v5][next-20140804] ARM: EXYNOS: Fix suspend/resume sequences
> > (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg35262.html)
> > - [PATCH v2 0/2] Firmware-assisted suspend/resume of Exynos SoCs
> > (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg34282.html)
> >
> > Changes since v4:
> > - rebased on top of next-20140804 +
> > [PATCH v5][next-20140804] ARM: EXYNOS: Fix suspend/resume sequences
> > (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg35262.html)
> > [PATCH v2 0/2] Firmware-assisted suspend/resume of Exynos SoCs
> > (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg34282.html)
> > - call exynos_save_cp15() only on A9 type core (this is needed for the future
> > Exynos3250 SoC support)
> >
> > Changes since v3:
> > - rebased on top of next-20140804 +
> > [PATCH v4][next-20140804] ARM: EXYNOS: Fix suspend/resume sequences
> > (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg35192.html)
> > [PATCH v2 0/2] Firmware-assisted suspend/resume of Exynos SoCs
> > (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg34282.html)
> > - (re-)added patch fixing S5P_CENTRAL_SEQ_OPTION register setup
> >
> > Changes since v2:
> > - rebased on top of next-20140708 +
> > [PATCH 5/6] ARM: EXYNOS: Fix suspend/resume sequencies
> > (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg32809.html)
> > [with rejects fixed]
> > [PATCH 6/6] ARM: EXYNOS: Register cpuidle device only on Exynos4210 and 5250
> > (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg32808.html)
> > [PATCH 0/2] Firmware-assisted suspend/resume of Exynos SoCs
> > (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg32991.html)
> > [with rejects fixed in patch #2]
> > - addressed review comments from Tomasz Figa and Daniel Lezcano
> >
> > Changes since v1:
> > - synced against next-20140602
> > - added missing Acked-by-s
> >
> > Best regards,
> > --
> > Bartlomiej Zolnierkiewicz
> > Samsung R&D Institute Poland
> > Samsung Electronics
> >
> >
> > Bartlomiej Zolnierkiewicz (5):
> > ARM: EXYNOS: PM: replace EXYNOS_BOOT_VECTOR_* macros by static inlines
> > ARM: EXYNOS: add AFTR mode support to firmware do_idle method
> > ARM: EXYNOS: cpuidle: add secure firmware support to AFTR mode code
> > ARM: EXYNOS: PM: fix register setup for AFTR mode code
> > ARM: EXYNOS: cpuidle: allow driver usage on Exynos4x12 SoCs
> >
> > arch/arm/include/asm/firmware.h | 2 +-
> > arch/arm/mach-exynos/common.h | 5 ++++
> > arch/arm/mach-exynos/exynos.c | 4 ++-
> > arch/arm/mach-exynos/firmware.c | 34 ++++++++++++++++-------
> > arch/arm/mach-exynos/pm.c | 60 ++++++++++++++++++++++++-----------------
> > 5 files changed, 70 insertions(+), 35 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists