[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTimP7_ADTd+9Wyc4tLtsXVnS=1EwTac1Z8CtgHV2@mail.gmail.com>
Date: Thu, 24 Mar 2011 14:36:42 -0400
From: Mike Frysinger <vapier@...too.org>
To: Jamie Iles <jamie@...ieiles.com>
Cc: linux-kernel@...r.kernel.org, gregkh@...e.de
Subject: Re: [RFC PATCHv2 0/4] Support for OTP memory
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.
-mike
--
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