From: srinivas.kandagatla@linaro.org (Srinivas Kandagatla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 1/9] nvmem: Add a simple NVMEM framework for nvmem providers
Date: Wed, 24 Jun 2015 10:56:11 +0100 [thread overview]
Message-ID: <558A7EBB.6000304@linaro.org> (raw)
In-Reply-To: <7BE8C921-180A-411D-A3C0-5D2A7AE3AB6A@konsulko.com>
On 23/06/15 10:26, Pantelis Antoniou wrote:
> Hi Joe,
>
>> >On Jun 23, 2015, at 05:52 , Joe Perches<joe@perches.com> wrote:
>> >
>> >On Tue, 2015-06-23 at 00:08 +0100, Srinivas Kandagatla wrote:
>>> >>This patch adds just providers part of the framework just to enable easy
>>> >>review.
>> >[]
>>> >>include/linux/nvmem-provider.h | 54 ++++++
>> >
>> >Unless there are going to be users of nvmem-provider.h
>> >outside of the drivers/nvmem directory, perhaps that
>> >file (and nvmem-consumer.h) should be in drivers/nvmem/
>> >
>> >
> nvmem-consumer.h should be accessible from any driver, no?
>
> And unfortunately nvmem-provider should be accessible too.
> There are already eeprom drivers in the eeprom/misc directory that
> cannot be moved yet to drivers/nvmem (like at24).
>
> They need the provider definitions while they provide both the old
> style interface, and the new NVMEM based one.
>
> When we move them to the drivers/nvmem directory, then yes the
> provider header file should move there.
Yep, that's the plan.
---srini
>
> Regards
>
> ? Pantelis
>
next prev parent reply other threads:[~2015-06-24 9:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 23:07 [PATCH v6 0/9] Add simple NVMEM Framework via regmap Srinivas Kandagatla
2015-06-22 23:08 ` [PATCH v6 1/9] nvmem: Add a simple NVMEM framework for nvmem providers Srinivas Kandagatla
2015-06-23 4:52 ` Joe Perches
2015-06-23 9:26 ` Pantelis Antoniou
2015-06-24 9:56 ` Srinivas Kandagatla [this message]
2015-06-23 20:10 ` Stefan Wahren
2015-06-24 9:54 ` Srinivas Kandagatla
2015-06-22 23:08 ` [PATCH v6 2/9] nvmem: Add a simple NVMEM framework for consumers Srinivas Kandagatla
2015-06-23 20:16 ` Stefan Wahren
2015-06-24 9:53 ` Srinivas Kandagatla
2015-06-22 23:08 ` [PATCH v6 3/9] nvmem: Add nvmem_device based consumer apis Srinivas Kandagatla
2015-06-23 20:28 ` Stefan Wahren
2015-06-24 9:52 ` Srinivas Kandagatla
2015-06-22 23:08 ` [PATCH v6 4/9] nvmem: Add bindings for simple nvmem framework Srinivas Kandagatla
2015-06-23 20:35 ` Stefan Wahren
2015-06-24 9:51 ` Srinivas Kandagatla
2015-06-22 23:09 ` [PATCH v6 5/9] Documentation: nvmem: add nvmem api level and how-to doc Srinivas Kandagatla
2015-06-22 23:09 ` [PATCH v6 6/9] nvmem: qfprom: Add Qualcomm QFPROM support Srinivas Kandagatla
2015-06-24 22:07 ` Stephen Boyd
2015-06-22 23:09 ` [PATCH v6 7/9] nvmem: qfprom: Add bindings for qfprom Srinivas Kandagatla
2015-06-23 9:25 ` Rajendra Nayak
2015-06-24 9:49 ` Srinivas Kandagatla
2015-06-22 23:09 ` [PATCH v6 8/9] nvmem: sunxi: Move the SID driver to the nvmem framework Srinivas Kandagatla
2015-06-23 20:44 ` Stefan Wahren
2015-06-24 9:48 ` Srinivas Kandagatla
2015-06-22 23:15 ` [PATCH v6 9/9] nvmem: Add to MAINTAINERS for " Srinivas Kandagatla
2015-06-23 19:47 ` [PATCH v6 0/9] Add simple NVMEM Framework via regmap Stefan Wahren
2015-06-24 5:54 ` Sanchayan Maity
2015-06-24 9:46 ` Srinivas Kandagatla
2015-06-24 12:30 ` Stefan Wahren
2015-06-24 13:03 ` Srinivas Kandagatla
2015-06-24 17:47 ` Stefan Wahren
2015-06-24 18:50 ` Srinivas Kandagatla
2015-06-30 17:47 ` Stefan Wahren
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=558A7EBB.6000304@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).