Re: [RFC PATCHv2 1/4] drivers/otp: add initial support for OTP memory

Mike Frysinger
2011-03-25T22:36:48Z

[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]

On Fri, Mar 25, 2011 at 18:27, Jamie Iles wrote:
> On Fri, Mar 25, 2011 at 05:32:54PM -0400, Mike Frysinger wrote:
>> On Fri, Mar 25, 2011 at 06:08, Jamie Iles wrote:
>> > I guess in this framework we could make the OTP look like a single
>> > region of the 0x80 data pages concatenated or provide separate regions
>> > for each group of 0x80 pages but the control and ECC pages aren't
>> > directly accessible by the user.
>>
>> well, in the current driver, i let people dump the ECC.  for
>> debugging, i think that's valuable.
>
> Hmm, that does sound potentially useful.  In v3 I've created a single
> partition that excludes the control bits and the ecc.  How about I
> change that for the next spin so there are two partitions where the
> first contains the raw data and the second is all of the ECC lumped
> together.  It may also be useful to have a name attribute for each
> region to make this clear.

this does sound useful. on Blackfin parts, we've already dedicated
specific pages to specific functions. so if there was a name
attribute to each region, i could potentially make each one a region.
-mike

[-- Attachment #2: otp-map.png --]
[-- Type: image/png, Size: 159260 bytes --]