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: Wed, 25 Feb 2015 13:12:01 +0000 From: James Hartley <James.Hartley@...tec.com> To: Ezequiel Garcia <Ezequiel.Garcia@...tec.com>, Maxime Ripard <maxime.ripard@...e-electrons.com> CC: Thierry Reding <thierry.reding@...il.com>, Stephen Warren <swarren@...dotorg.org>, Arnd Bergmann <arnd@...db.de>, Andrew Bresticker <abrestic@...omium.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: RE: [PATCH 0/7] New eFuse subsystem Hi Maxime, > -----Original Message----- > From: Ezequiel Garcia > Sent: 25 February 2015 12:30 > To: Maxime Ripard > Cc: Thierry Reding; Stephen Warren; Arnd Bergmann; Andrew Bresticker; > James Hartley; linux-arm-kernel@...ts.infradead.org; linux- > kernel@...r.kernel.org > Subject: Re: [PATCH 0/7] New eFuse subsystem > > > > On 02/25/2015 09:02 AM, Maxime Ripard wrote: > > Hi Ezequiel, > > > > On Wed, Feb 25, 2015 at 08:45:12AM -0300, Ezequiel Garcia wrote: > >> This patchset introduces a new driver subsystem, meant to support > >> eFuse (alias OTP, one-time-programmable) devices. > >> > >> The motivation behind this work is to have a common place for drivers > >> that are currently more or less scattered: the tegra efuses are in > >> drivers/soc/ and the sunxi efuses in drivers/misc/eeprom. > >> > >> For now, there's no proposal for a generic efuse API. Instead, we > >> simply group the drivers together. > >> > >> This patchset is the result of the initial submission for IMG > >> Pistachio eFuse support [1]. Our first proposal was to follow the > >> Tegra efuse, and put the Pistachio efuse in drivers/soc. After some > >> discussion we finally agreed [2] to first create an efuse directoy, > >> and then put all efuse drivers in it. > >> > >> As always, all comments are welcome! > >> > >> [1] http://www.spinics.net/lists/devicetree/msg59246.html > >> [2] http://www.spinics.net/lists/arm-kernel/msg389325.html > > > > Have you looked at the EEPROM framework currently in discussions? The > > two seems to be covering pretty much the same use cases. > > Shouldn't this be a PROM framework if it is going to support both EEPROM and EFUSE/QFPROM, or am I missing something here (since an eFuse is not eraseable)? > > Nope, I was obviously unaware of that. Guess we'll wait until the discussion is > settled and use that framework. > > Thanks! > -- > Ezequiel Thanks, James. -- 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