From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Wahren Subject: Re: [PATCH v6 0/9] Add simple NVMEM Framework via regmap. Date: Tue, 30 Jun 2015 19:47:09 +0200 (CEST) Message-ID: <1183639717.72990.1435686429623.JavaMail.open-xchange@oxbsltgw03.schlund.de> References: <1435014459-26138-1-git-send-email-srinivas.kandagatla@linaro.org> <235181230.251177.1435088854197.JavaMail.open-xchange@oxbsltgw00.schlund.de> <558A7C92.2040102@linaro.org> <558AA2E2.1010606@i2se.com> <558AAA8D.8030209@linaro.org> <1641569650.41238.1435168054323.JavaMail.open-xchange@oxbsltgw35.schlund.de> <558AFC0B.1050400@linaro.org> Reply-To: Stefan Wahren Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <558AFC0B.1050400-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Srinivas Kandagatla , linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org Cc: wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org, linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Kumar Gala , Rob Herring , arnd-r2nGTMty4D4@public.gmane.org, sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org, s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org, Greg Kroah-Hartman , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, mporter-OWPKS81ov/FWk0Htik3J/w@public.gmane.org, linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Maxime Ripard , pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Mark Brown List-Id: linux-arm-msm@vger.kernel.org Hi Srinivas, > Srinivas Kandagatla hat am 24. Juni 2015 um > 20:50 geschrieben: > > > > > On 24/06/15 18:47, Stefan Wahren wrote: > > Hi Srinivas, > > > >> Srinivas Kandagatla 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 example it is the context variable. Now i've successful tested my first version of the OCOTP driver based on NVMEM framework [1]. 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() . Regards Stefan [1] - https://github.com/lategoodbye/fsl_ocotp/commit/7c98e19755b69f761885b0e1ceb2c258a7c47ade -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html