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: Mon, 21 Jan 2019 07:22:53 +0100 From: Lubomir Rintel <lkundrak@...sk> To: Dmitry Torokhov <dmitry.torokhov@...il.com>, Michael Turquette <mturquette@...libre.com> Cc: Stephen Boyd <sboyd@...nel.org>, Rob Herring <robh+dt@...nel.org>, Mark Rutland <mark.rutland@....com>, linux-input@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org Subject: [PATCH 0/3] Stop managing the SP clock Hi, Per discussion in [1] it seems that the kernel has no business managing this clock: once the SP clock is disabled, it's not sufficient to just enable it in order to bring the SP core back up. Just let the firmware keep it enabled and don't expose it to drivers. [1] https://lore.kernel.org/lkml/154783267051.169631.3197836544646625747@swboyd.mtv.corp.google.com/ The "secure processor" (SP) core runs the keyboard firmware on the OLPC XO 1.75 laptop. Lubo
Powered by blists - more mailing lists