[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <558A7C92.2040102@linaro.org>
Date: Wed, 24 Jun 2015 10:46:58 +0100
From: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To: Stefan Wahren <stefan.wahren@...e.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-arm-kernel@...ts.infradead.org
CC: wxt@...k-chips.com, linux-api@...r.kernel.org,
Kumar Gala <galak@...eaurora.org>,
Rob Herring <robh+dt@...nel.org>, sboyd@...eaurora.org,
arnd@...db.de, s.hauer@...gutronix.de,
linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
mporter@...sulko.com,
Maxime Ripard <maxime.ripard@...e-electrons.com>,
pantelis.antoniou@...sulko.com, devicetree@...r.kernel.org,
Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH v6 0/9] Add simple NVMEM Framework via regmap.
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-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