Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755707AbcCNMCA (ORCPT ); Mon, 14 Mar 2016 08:02:00 -0400 Received: from mailgw02.mediatek.com ([210.61.82.184]:24162 "EHLO mailgw02.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1754141AbcCNMBv (ORCPT ); Mon, 14 Mar 2016 08:01:51 -0400 Message-ID: <1457956899.20370.25.camel@mtksdaap41> Subject: NVMEM usage question From: Eddie Huang To: Srinivas Kandagatla , Maxime Ripard CC: , , , Date: Mon, 14 Mar 2016 20:01:39 +0800 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-MTK: N Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 559 Lines: 13 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 ? Eddie