Re: [PATCH v6 0/9] Add simple NVMEM Framework via regmap.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 23/06/15 20:47, Stefan Wahren wrote:
0001000
>
i want to port OCOTP driver for MXS, which hasn't MMIO. From my understanding
That's cool.

hexdump would readout the complete register range defined in provider DT node.

How can i achieve that hexdump only reads the data area within the register
range?

If the question is just about hexdump, then hexdump itself can read file from given offset and size.

But I believe the real question is "How can we dump each nvmem cell independently"

In one of my replies I mentioned that am planning to add sysfs entries under /sys/class/nvmem/<provider>/cells/

ex:
for qfprom tsens calibration it would look like:

$ hexdump /sys/class/nvmem/qfprom0/cells/tsens_calibration

0000000 e000 0c00 0c00 0000 0c00
...

Is that what you guys are looking for?

--srini

Stefan
--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [Linux for Sparc]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux