| 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
| ||
|
Message-ID: <53BDA931.5010600@gmail.com> Date: Wed, 09 Jul 2014 22:42:25 +0200 From: Tomasz Figa <tomasz.figa@...il.com> To: Stephen Boyd <sboyd@...eaurora.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org> CC: "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>, Stephen Warren <swarren@...dia.com>, Arnd Bergmann <arnd@...db.de>, "linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>, Peter De Schrijver <pdeschrijver@...dia.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Bjorn Andersson <bjorn.andersson@...ymobile.com> Subject: Re: a case for a common efuse API? Hi Stephen, On 08.07.2014 22:00, Stephen Boyd wrote: > Hi, > > On MSM chips we have some efuses (called qfprom) where we store things > like calibration data, speed bins, etc. We need to read out data from > the efuses in various drivers like the cpufreq, thermal, etc. This > essentially boils down to a bunch of readls on the efuse from a handful > of different drivers. We have similar thing on Exynos SoCs as well. If you're interested in looking at our use cases, then there was an RFC series posted quite a long time ago [1], but then things stalled. [1] https://lkml.org/lkml/2013/11/15/155 Best regards, Tomasz -- 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