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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:   Wed, 19 Dec 2018 02:12:59 +0000
From:   Peng Fan <peng.fan@....com>
To:     Jens Wiklander <jens.wiklander@...aro.org>,
        Ulf Hansson <ulf.hansson@...aro.org>,
        Jerome Forissier <jerome.forissier@...aro.org>
CC:     Linux PM <linux-pm@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: tee/optee driver pm question

Hi Jens, Ulf

We met an issue is OP-TEE is actively doing some DMA operations, such as CAAM DMA, while Linux is doing some ddr freq change and will let ddr into self-refresh state, this will cause issues.

On ARMv8 i.MX, we have code request_bus_freq/release_bus_freq to ask ATF to make ddr into/out self refresh state. On ARMv7, we use similar code, but the request/release will runs into OP-TEE to make ddr into/out self refresh state.

We have a RPC design, that is OP-TEE issue a RPC call to Linux, to ask Linux to not issue release bus freq, but this will introduce complexity and not aligned with other drivers in Linux Kernel. We are thinking to add pm call back to optee/tee drivers, but did not find a good method. Do you have any suggestions?

Thanks,
Peng.



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ