Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752676AbbBYNMG (ORCPT ); Wed, 25 Feb 2015 08:12:06 -0500 Received: from mailapp01.imgtec.com ([195.59.15.196]:65343 "EHLO mailapp01.imgtec.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752345AbbBYNME convert rfc822-to-8bit (ORCPT ); Wed, 25 Feb 2015 08:12:04 -0500 From: James Hartley To: Ezequiel Garcia , Maxime Ripard CC: Thierry Reding , Stephen Warren , Arnd Bergmann , Andrew Bresticker , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" Subject: RE: [PATCH 0/7] New eFuse subsystem Thread-Topic: [PATCH 0/7] New eFuse subsystem Thread-Index: AQHQUPDhgPbtHSURHkqrOQ3uOvpzPp0BQ/8AgAAHsQCAAAuDsA== Date: Wed, 25 Feb 2015 13:12:01 +0000 Message-ID: <72BC0C8BD7BB6F45988A99382E5FBAE5444505E9@hhmail02.hh.imgtec.org> References: <1424864719-3390-1-git-send-email-ezequiel.garcia@imgtec.com> <20150225120234.GB5062@lukather> <54EDC04E.1050107@imgtec.com> In-Reply-To: <54EDC04E.1050107@imgtec.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.167.65] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2150 Lines: 59 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@lists.infradead.org; linux- > kernel@vger.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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/