From: Tomasz Figa <tomasz.figa@gmail.com>
To: Stephen Boyd <sboyd@codeaurora.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Stephen Warren <swarren@nvidia.com>,
Arnd Bergmann <arnd@arndb.de>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@sonymobile.com>
Subject: Re: a case for a common efuse API?
Date: Wed, 09 Jul 2014 22:42:25 +0200 [thread overview]
Message-ID: <53BDA931.5010600@gmail.com> (raw)
In-Reply-To: <53BC4DD7.20906@codeaurora.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
WARNING: multiple messages have this Message-ID (diff)
From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: a case for a common efuse API?
Date: Wed, 09 Jul 2014 22:42:25 +0200 [thread overview]
Message-ID: <53BDA931.5010600@gmail.com> (raw)
In-Reply-To: <53BC4DD7.20906@codeaurora.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
next prev parent reply other threads:[~2014-07-09 20:42 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 20:00 a case for a common efuse API? Stephen Boyd
2014-07-08 20:00 ` Stephen Boyd
2014-07-08 20:26 ` Olof Johansson
2014-07-08 20:26 ` Olof Johansson
2014-07-08 21:59 ` Bjorn Andersson
2014-07-08 21:59 ` Bjorn Andersson
[not found] ` <53BC4DD7.20906-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-07-09 7:24 ` Uwe Kleine-König
2014-07-09 7:24 ` Uwe Kleine-König
2014-07-09 7:24 ` Uwe Kleine-König
2014-07-09 7:50 ` Srinivas Kandagatla
2014-07-09 7:50 ` Srinivas Kandagatla
2014-07-09 8:35 ` Maxime Ripard
2014-07-09 8:35 ` Maxime Ripard
2014-07-09 23:32 ` Stephen Boyd
2014-07-09 23:32 ` Stephen Boyd
2014-07-10 14:26 ` Maxime Ripard
2014-07-10 14:26 ` Maxime Ripard
2014-07-10 15:18 ` Alexandre Belloni
2014-07-10 15:18 ` Alexandre Belloni
2014-07-10 15:41 ` Grygorii Strashko
2014-07-10 15:41 ` Grygorii Strashko
[not found] ` <53BEB443.9000606-l0cyMroinI0@public.gmane.org>
2014-07-10 15:09 ` Maxime Ripard
2014-07-10 15:09 ` Maxime Ripard
2014-07-10 15:09 ` Maxime Ripard
2014-09-11 21:59 ` Stephen Boyd
2014-09-11 21:59 ` Stephen Boyd
2014-09-16 10:16 ` Maxime Ripard
2014-09-16 10:16 ` Maxime Ripard
2014-07-09 11:49 ` Peter De Schrijver
2014-07-09 11:49 ` Peter De Schrijver
[not found] ` <20140709114907.GI23218-Rysk9IDjsxmJz7etNGeUX8VPkgjIgRvpAL8bYrjMMd8@public.gmane.org>
2014-07-21 15:51 ` Stephen Warren
2014-07-21 15:51 ` Stephen Warren
2014-07-21 15:51 ` Stephen Warren
2014-07-09 20:42 ` Tomasz Figa [this message]
2014-07-09 20:42 ` Tomasz Figa
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=53BDA931.5010600@gmail.com \
--to=tomasz.figa@gmail.com \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@sonymobile.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pdeschrijver@nvidia.com \
--cc=sboyd@codeaurora.org \
--cc=swarren@nvidia.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.