From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754971AbaGIUmt (ORCPT ); Wed, 9 Jul 2014 16:42:49 -0400 Received: from mail-wg0-f44.google.com ([74.125.82.44]:62664 "EHLO mail-wg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753413AbaGIUmr (ORCPT ); Wed, 9 Jul 2014 16:42:47 -0400 Message-ID: <53BDA931.5010600@gmail.com> Date: Wed, 09 Jul 2014 22:42:25 +0200 From: Tomasz Figa User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Stephen Boyd , "linux-arm-kernel@lists.infradead.org" CC: "devicetree@vger.kernel.org" , Stephen Warren , Arnd Bergmann , "linux-arm-msm@vger.kernel.org" , Peter De Schrijver , Linux Kernel Mailing List , Bjorn Andersson Subject: Re: a case for a common efuse API? References: <53BC4DD7.20906@codeaurora.org> In-Reply-To: <53BC4DD7.20906@codeaurora.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Stephen, On 08.07.2014 22:00, Stephen Boyd wrote: > Hi, > > On MSM chips we have some efuses (called qfprom) where we store things > like calibration data, speed bins, etc. We need to read out data from > the efuses in various drivers like the cpufreq, thermal, etc. This > essentially boils down to a bunch of readls on the efuse from a handful > of different drivers. We have similar thing on Exynos SoCs as well. If you're interested in looking at our use cases, then there was an RFC series posted quite a long time ago [1], but then things stalled. [1] https://lkml.org/lkml/2013/11/15/155 Best regards, Tomasz