Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934225Ab1CXUkb (ORCPT ); Thu, 24 Mar 2011 16:40:31 -0400 Received: from mail-wy0-f174.google.com ([74.125.82.174]:58278 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932812Ab1CXUk3 (ORCPT ); Thu, 24 Mar 2011 16:40:29 -0400 Date: Thu, 24 Mar 2011 20:40:26 +0000 From: Jamie Iles To: Mike Frysinger Cc: Jamie Iles , linux-kernel@vger.kernel.org, gregkh@suse.de Subject: Re: [RFC PATCHv2 4/4] drivers/otp: convert bfin otp to generic OTP Message-ID: <20110324204026.GM3130@pulham.picochip.com> References: <1300980071-24645-1-git-send-email-jamie@jamieiles.com> <1300980071-24645-5-git-send-email-jamie@jamieiles.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1060 Lines: 24 On Thu, Mar 24, 2011 at 02:52:20PM -0400, Mike Frysinger wrote: > On Thu, Mar 24, 2011 at 11:21, Jamie Iles wrote: > > +config BFIN_OTP_WRITE_ENABLE > > + ? ? ? bool "Enable writing support of OTP pages" > > + ? ? ? depends on BFIN_OTP > > + ? ? ? default n > > + ? ? ? help > > + ? ? ? ? If you say Y here, you will enable support for writing of the > > + ? ? ? ? OTP pages. ?This is dangerous by nature as you can only program > > + ? ? ? ? the pages once, so only enable this option when you actually > > + ? ? ? ? need it so as to not inadvertently clobber data. > > if the generic layer is providing write enable access now, is this > still necessary ? we could have a common OTP Kconfig i think for > "enable OTP write support". Sounds like a good idea. I'll integrate this into the next revision. Jamie -- 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/