From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
Cc: Mathieu Malaterre <malat@debian.org>,
Marcin Nowakowski <marcin.nowakowski@mips.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Zubair.Kakakhel@mips.com, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Ralf Baechle <ralf@linux-mips.org>,
open list <linux-kernel@vger.kernel.org>,
devicetree@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: [PATCH v2 0/2] Add efuse driver for Ingenic JZ4780 SoC
Date: Tue, 2 Jan 2018 17:58:00 +0000 [thread overview]
Message-ID: <11f64a94-2500-6c5f-d6f9-2db68fcf9c58@linaro.org> (raw)
In-Reply-To: <CANc+2y5cEoqEkqEr9b-APApd42HXQczFWJfGv+MWPNRdWpQr7Q@mail.gmail.com>
On 02/01/18 16:17, PrasannaKumar Muralidharan wrote:
> Hi Srinivas,
>
> On 2 January 2018 at 17:31, Srinivas Kandagatla
> <srinivas.kandagatla@linaro.org> wrote:
>>
>>
>> On 28/12/17 21:29, Mathieu Malaterre wrote:
>>>
>>> This patchset bring support for read-only access to the JZ4780 efuse as
>>> found
>>> on MIPS Creator CI20.
>>>
>>> To keep the driver as simple as possible, it was not possible to re-use
>>> most of
>>> the nvmem core functionalities. This driver is not compatible with the
>>> original
>>
>> Can you explain a bit more on not able to re-use nvmem core?
>>
>> If you are referring to adding nvmem cell entires in sysfs, This should
>> probably go in to nvmem core, rather that in individual providers.
>> This is one of the feature my todo list, will try to come up with some thing
>> soon.
>
> We could not find a way to expose different sized segments using nvmem
> framework. Do you have any pointers for this?
This does not exist at the moment, but it should be very much doable to
add this functionality to nvmem core.
I will keep you loop if I manage to post this patch soon.
--srini
> We were not aware of the fact that nvmem does not expose individual
> cell entries in sysfs.
>
> Regards,
> PrasannaKumar
>
prev parent reply other threads:[~2018-01-02 17:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 21:29 [PATCH v2 0/2] Add efuse driver for Ingenic JZ4780 SoC Mathieu Malaterre
2017-12-28 21:29 ` [PATCH v2 1/2] nvmem: add driver for JZ4780 efuse Mathieu Malaterre
2017-12-29 12:35 ` Marcin Nowakowski
2018-01-02 12:02 ` Srinivas Kandagatla
2018-01-02 16:17 ` PrasannaKumar Muralidharan
2018-01-03 20:02 ` Rob Herring
2018-01-06 12:43 ` PrasannaKumar Muralidharan
2018-01-11 15:08 ` Rob Herring
2018-01-17 17:31 ` PrasannaKumar Muralidharan
2018-01-18 1:59 ` Rob Herring
2018-01-20 8:11 ` PrasannaKumar Muralidharan
2017-12-28 21:29 ` [PATCH v2 2/2] dts: Probe efuse for CI20 Mathieu Malaterre
2018-01-03 20:04 ` Rob Herring
2018-01-17 20:54 ` James Hogan
2018-01-02 12:01 ` [PATCH v2 0/2] Add efuse driver for Ingenic JZ4780 SoC Srinivas Kandagatla
2018-01-02 16:17 ` PrasannaKumar Muralidharan
2018-01-02 17:58 ` Srinivas Kandagatla [this message]
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=11f64a94-2500-6c5f-d6f9-2db68fcf9c58@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=Zubair.Kakakhel@mips.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=malat@debian.org \
--cc=marcin.nowakowski@mips.com \
--cc=mark.rutland@arm.com \
--cc=prasannatsmkumar@gmail.com \
--cc=ralf@linux-mips.org \
--cc=robh+dt@kernel.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).