From: srinivas.kandagatla@linaro•org (Srinivas Kandagatla)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v8 1/9] nvmem: Add a simple NVMEM framework for nvmem providers
Date: Thu, 23 Jul 2015 16:50:26 +0100 [thread overview]
Message-ID: <55B10D42.1020803@linaro.org> (raw)
In-Reply-To: <55B107B0.5010706@i2se.com>
On 23/07/15 16:26, Stefan Wahren wrote:
> Hi Srinivas,
>
> Am 20.07.2015 um 16:43 schrieb Srinivas Kandagatla:
>> This patch adds just providers part of the framework just to enable easy
>> review.
>>
>> Up until now, NVMEM drivers like eeprom were stored in drivers/misc,
>> where they all had to duplicate pretty much the same code to register
>> a sysfs file, allow in-kernel users to access the content of the devices
>> they were driving, etc.
>>
>> This was also a problem as far as other in-kernel users were involved,
>> since the solutions used were pretty much different from on driver to
>> another, there was a rather big abstraction leak.
>>
>> This introduction of this framework aims at solving this. It also
>> introduces DT representation for consumer devices to go get the data
>> they require (MAC Addresses, SoC/Revision ID, part numbers, and so on)
>> from the nvmems.
>>
>> Having regmap interface to this framework would give much better
>> abstraction for nvmems on different buses.
>>
>> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons•com>
>> [Maxime Ripard: intial version of eeprom framework]
>> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro•org>
>> ---
>> drivers/Kconfig | 2 +
>> drivers/Makefile | 1 +
>> drivers/nvmem/Kconfig | 13 ++
>> drivers/nvmem/Makefile | 6 +
>> drivers/nvmem/core.c | 384 +++++++++++++++++++++++++++++++++++++++++
>> include/linux/nvmem-consumer.h | 23 +++
>> include/linux/nvmem-provider.h | 47 +++++
>> 7 files changed, 476 insertions(+)
>> create mode 100644 drivers/nvmem/Kconfig
>> create mode 100644 drivers/nvmem/Makefile
>> create mode 100644 drivers/nvmem/core.c
>> create mode 100644 include/linux/nvmem-consumer.h
>> create mode 100644 include/linux/nvmem-provider.h
>
> i've tested this patch with my mxs-ocotp driver [1].
>
> So you can add
>
> Tested-by: Stefan Wahren <stefan.wahren@i2se•com>
>
Thanks for tested-by, That helps.
--srini
> Regards
> Stefan
>
next prev parent reply other threads:[~2015-07-23 15:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 14:42 [PATCH v8 0/9] Add simple NVMEM Framework via regmap Srinivas Kandagatla
2015-07-20 14:43 ` [PATCH v8 1/9] nvmem: Add a simple NVMEM framework for nvmem providers Srinivas Kandagatla
2015-07-20 21:11 ` Stephen Boyd
2015-07-21 9:41 ` Srinivas Kandagatla
2015-07-21 9:54 ` Stefan Wahren
2015-07-21 10:31 ` Srinivas Kandagatla
2015-07-21 17:59 ` Stephen Boyd
2015-07-21 18:40 ` Srinivas Kandagatla
2015-07-21 18:51 ` Srinivas Kandagatla
2015-07-23 15:26 ` Stefan Wahren
2015-07-23 15:50 ` Srinivas Kandagatla [this message]
2015-07-20 14:43 ` [PATCH v8 2/9] nvmem: Add a simple NVMEM framework for consumers Srinivas Kandagatla
2015-07-21 16:25 ` Stefan Wahren
2015-07-22 7:26 ` Srinivas Kandagatla
2015-07-20 14:43 ` [PATCH v8 3/9] nvmem: Add nvmem_device based consumer apis Srinivas Kandagatla
2015-07-20 14:43 ` [PATCH v8 4/9] nvmem: Add bindings for simple nvmem framework Srinivas Kandagatla
2015-07-20 14:43 ` [PATCH v8 5/9] Documentation: nvmem: add nvmem api level and how-to doc Srinivas Kandagatla
2015-07-20 14:44 ` [PATCH v8 6/9] nvmem: qfprom: Add Qualcomm QFPROM support Srinivas Kandagatla
2015-07-20 21:20 ` Stephen Boyd
2015-07-21 9:42 ` Srinivas Kandagatla
2015-07-20 14:44 ` [PATCH v8 7/9] nvmem: qfprom: Add bindings for qfprom Srinivas Kandagatla
2015-07-20 14:44 ` [PATCH v8 8/9] nvmem: sunxi: Move the SID driver to the nvmem framework Srinivas Kandagatla
2015-07-21 16:38 ` Stefan Wahren
2015-07-23 15:48 ` Srinivas Kandagatla
2015-07-23 15:18 ` Stefan Wahren
2015-07-23 15:48 ` Srinivas Kandagatla
2015-07-20 14:44 ` [PATCH v8 9/9] nvmem: Add to MAINTAINERS for " Srinivas Kandagatla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55B10D42.1020803@linaro.org \
--to=srinivas.kandagatla@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox