From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Eddie Huang <eddie.huang@mediatek.com>,
Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: linux-mediatek@lists.infradead.org, andrew-ct.chen@mediatek.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: NVMEM usage question
Date: Wed, 16 Mar 2016 06:50:45 +0000 [thread overview]
Message-ID: <56E90245.1040203@linaro.org> (raw)
In-Reply-To: <1457956899.20370.25.camel@mtksdaap41>
On 14/03/16 12:01, Eddie Huang wrote:
> Hi,
>
> Mediatek PMIC chip have some spare registers used to store information.
> The value of these registers will exist until user unplug battery or
> battery depletion. One of our usage example is store battery utilization
> in these spare registers. We want to implement NVMEM driver to
> read/write sparse registers, but binding document describe NVMEM is for
> "Non-volatile memory", and for hardware like eeprom, efuse. Since the
> usage here is some kind of "battery backup memory", but not real
> non-volatile memory, is NVMEM driver suitable for this case ?
If this battery usage information can be retrieved after full power
cycle, then there should be some sort of non volatile memory involved.
If that's the case then you can use the nvmem.
--srini
>
> Eddie
>
>
WARNING: multiple messages have this Message-ID (diff)
From: srinivas.kandagatla@linaro.org (Srinivas Kandagatla)
To: linux-arm-kernel@lists.infradead.org
Subject: NVMEM usage question
Date: Wed, 16 Mar 2016 06:50:45 +0000 [thread overview]
Message-ID: <56E90245.1040203@linaro.org> (raw)
In-Reply-To: <1457956899.20370.25.camel@mtksdaap41>
On 14/03/16 12:01, Eddie Huang wrote:
> Hi,
>
> Mediatek PMIC chip have some spare registers used to store information.
> The value of these registers will exist until user unplug battery or
> battery depletion. One of our usage example is store battery utilization
> in these spare registers. We want to implement NVMEM driver to
> read/write sparse registers, but binding document describe NVMEM is for
> "Non-volatile memory", and for hardware like eeprom, efuse. Since the
> usage here is some kind of "battery backup memory", but not real
> non-volatile memory, is NVMEM driver suitable for this case ?
If this battery usage information can be retrieved after full power
cycle, then there should be some sort of non volatile memory involved.
If that's the case then you can use the nvmem.
--srini
>
> Eddie
>
>
next prev parent reply other threads:[~2016-03-16 6:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 12:01 NVMEM usage question Eddie Huang
2016-03-14 12:01 ` Eddie Huang
2016-03-14 12:01 ` Eddie Huang
2016-03-16 6:50 ` Srinivas Kandagatla [this message]
2016-03-16 6:50 ` Srinivas Kandagatla
2016-03-17 16:14 ` Henrique de Moraes Holschuh
2016-03-17 16:14 ` Henrique de Moraes Holschuh
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=56E90245.1040203@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=andrew-ct.chen@mediatek.com \
--cc=eddie.huang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=maxime.ripard@free-electrons.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.