Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934221Ab1CXUip (ORCPT ); Thu, 24 Mar 2011 16:38:45 -0400 Received: from mail-wy0-f174.google.com ([74.125.82.174]:61240 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932184Ab1CXUil (ORCPT ); Thu, 24 Mar 2011 16:38:41 -0400 Date: Thu, 24 Mar 2011 20:38:22 +0000 From: Jamie Iles To: Mike Frysinger Cc: Jamie Iles , linux-kernel@vger.kernel.org, gregkh@suse.de Subject: Re: [RFC PATCHv2 0/4] Support for OTP memory Message-ID: <20110324203821.GL3130@pulham.picochip.com> References: <1300980071-24645-1-git-send-email-jamie@jamieiles.com> <20110324174722.GH3130@pulham.picochip.com> <20110324183205.GI3130@pulham.picochip.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: 1748 Lines: 33 On Thu, Mar 24, 2011 at 02:36:42PM -0400, Mike Frysinger wrote: > On Thu, Mar 24, 2011 at 14:32, Jamie Iles wrote: > > On Thu, Mar 24, 2011 at 01:56:17PM -0400, Mike Frysinger wrote: > >> just an overview note here ... the Blackfin OTP is actually IP we > >> bought from someone (not sure if i can say more, although i dont know > >> the details myself ... i'd have to go ask around), so much of the > >> feedback i give about the structure of it most likely (hopefully) be > >> applicable to other people who have purchased this IP. ?if/when anyone > >> who is also using this IP steps forward, we could even see about > >> generalizing the bfin-otp driver. > > > > Yes, we have a similar thing here - a block of OTP from an IP vendor and > > a wrapper to provide an AXI interface. ?As far as I know there are only > > a few OTP vendors so there may well be plenty of common code in > > different OTP implementations. > > do you guys wrap the interface ? the Blackfin processors have an > on-chip ROM which provides higher level functions like > read/write/lock/etc... the Linux driver uses those rather than > programming the memory mapped OTP interface itself since this > interface is not publicly documented. I'm not 100% on the exact details but I understand that the macro provides some non-AXI registers and signals that we wrap up into some AXI registers. The wrapper doesn't handle all of the nasties of the macro but it does handle some of the redundancy and region splitting. 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/