[PATCH v6 0/9] Add simple NVMEM Framework via regmap.
stefan.wahren at i2se.com
Tue Jun 30 10:47:09 PDT 2015
> Srinivas Kandagatla <srinivas.kandagatla at linaro.org> hat am 24. Juni 2015 um
> 20:50 geschrieben:
> On 24/06/15 18:47, Stefan Wahren wrote:
> > Hi Srinivas,
> >> Srinivas Kandagatla <srinivas.kandagatla at linaro.org> hat am 24. Juni 2015
> >> um
> >> 15:03 geschrieben:
> >> On 24/06/15 13:30, Stefan Wahren wrote:
> >>>>> If the question is just about hexdump, then hexdump itself can read
> >>>>> file from given offset and size.
> >>> yes, this is my question at first. Let me show the difference between
> >>> the current implementation and my expectations as a user.
> >>> $ hexdump /sys/class/nvmem/mxs-ocotp/nvmem
> >>> Current implementation: dump the complete register range defined in DT
> >> Its dumping the range which is specified in the provider regmap. If the
> >> requirement is to dump only particular range, this has to be made
> >> explicit while creating regmap, which is to specify the base address to
> >> start from "First data register" and max_register to be "Last data
> >> register "- "First data register"
> > i know about max_register, but i can't find the base address in
> > regmap_config.
> Base is not in the regmap config, its the value which you pass to the
thanks for you explanation. I was confused by the word base because in your
it is the context variable.
Now i've successful tested my first version of the OCOTP driver based on NVMEM
Currently only the raw sysfs access is working. So i have another question:
How do i get the cell info from the devicetree for the nvmem_config?
I expected a function like of_nvmem_cell_info_get() .
More information about the linux-arm-kernel