lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 16 Mar 2016 06:50:45 +0000
From:	Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To:	Eddie Huang <eddie.huang@...iatek.com>,
	Maxime Ripard <maxime.ripard@...e-electrons.com>
Cc:	linux-mediatek@...ts.infradead.org, andrew-ct.chen@...iatek.com,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: NVMEM usage question



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
>
>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ