Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751537AbeABR6H (ORCPT + 1 other); Tue, 2 Jan 2018 12:58:07 -0500 Received: from mail-wm0-f67.google.com ([74.125.82.67]:33394 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751059AbeABR6D (ORCPT ); Tue, 2 Jan 2018 12:58:03 -0500 X-Google-Smtp-Source: ACJfBos0mBZWRoi7UaSF0sECTa1dYYi8TVU3w3pT8xEgWZXJSB0EKD2UvBx4RZU+jv+F5z2UYVt/Ew== Subject: Re: [PATCH v2 0/2] Add efuse driver for Ingenic JZ4780 SoC To: PrasannaKumar Muralidharan Cc: Mathieu Malaterre , Marcin Nowakowski , Greg Kroah-Hartman , Zubair.Kakakhel@mips.com, Rob Herring , Mark Rutland , Ralf Baechle , open list , devicetree@vger.kernel.org, linux-mips@linux-mips.org References: <20171228212954.2922-1-malat@debian.org> <828981e5-c23c-8dc4-55e4-23b65b33908b@linaro.org> From: Srinivas Kandagatla Message-ID: <11f64a94-2500-6c5f-d6f9-2db68fcf9c58@linaro.org> Date: Tue, 2 Jan 2018 17:58:00 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On 02/01/18 16:17, PrasannaKumar Muralidharan wrote: > Hi Srinivas, > > On 2 January 2018 at 17:31, Srinivas Kandagatla > 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 >