| 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: Tue, 8 Jul 2014 13:26:34 -0700 From: Olof Johansson <olof@...om.net> To: Stephen Boyd <sboyd@...eaurora.org> Cc: "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Bjorn Andersson <bjorn.andersson@...ymobile.com>, Stephen Warren <swarren@...dia.com>, Peter De Schrijver <pdeschrijver@...dia.com>, Arnd Bergmann <arnd@...db.de>, "linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>, "devicetree@...r.kernel.org" <devicetree@...r.kernel.org> Subject: Re: a case for a common efuse API? On Tue, Jul 8, 2014 at 1:00 PM, Stephen Boyd <sboyd@...eaurora.org> wrote: > I added Tegra folks because I see that on Tegra this hardware is exposed > via an SoC specific API, tegra_fuse_readl(), and an associated driver in > drivers/misc/fuse/tegra/. Unfortunately I don't see any users of the API > outside of the speedo code in the same directory and the sysfs bin > attribute that may or may not be in use by some userspace code. Note that I also turned down the pull request that houses the code under drivers/misc. This is the type of stuff we've been talking about needing a home for somewhere, and drivers/soc was one of the ones mentioned for that. I really don't like adding dependencies on a random driver from platform code, for example. -Olof -- 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