From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: a case for a common efuse API?
Date: Wed, 9 Jul 2014 10:35:09 +0200 [thread overview]
Message-ID: <20140709083509.GQ13423@lukather> (raw)
In-Reply-To: <53BC4DD7.20906@codeaurora.org>
Hi Stephen,
On Tue, Jul 08, 2014 at 01:00:23PM -0700, 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. In devicetree this looks a little odd because
> these drivers end up having an extra reg property (or two) that points
> to a register in the efuse and some length, i.e you see this:
>
> thermal-sensor at 34000 {
> compatible = "sensor";
> reg = <0x34000 0x1000>, <0x10018 0xc>;
> reg-names = "sensor", "efuse_calib";
> }
>
>
> I imagine in DT we want something more like this:
>
> efuse: efuse at 10000 {
> compatible = "efuse";
> reg = <0x10000 0x1000>;
> }
>
> thermal-sensor at 34000 {
> compatible = "sensor";
> reg = <0x34000 0x1000>;
> efuse = <&efuse 0x18>;
> }
We have pretty much the same things in the Allwinner SoCs. We have an
efuse directly mapped into memory, with a few informations like a MAC
address, the SoC ID, the serial number, some RSA keys for the device,
etc.
The thing is, some boards expose these informations in an external
EEPROM as well.
I started working and went quite far to create an "eeprom" framework
to handle these cases, with a dt representation similar to what you
were exposing.
https://github.com/mripard/linux/tree/eeprom-framework-at24
It was working quite well, I was about to send it, but was told that I
should all be moved to MTD, and given up on it.
Anyway, +1 for this :)
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140709/87e3b136/attachment.sig>
next prev parent reply other threads:[~2014-07-09 8:35 UTC|newest]
Thread overview: 16+ 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:26 ` Olof Johansson
2014-07-08 21:59 ` Bjorn Andersson
2014-07-09 7:24 ` Uwe Kleine-König
2014-07-09 7:50 ` Srinivas Kandagatla
2014-07-09 8:35 ` Maxime Ripard [this message]
2014-07-09 23:32 ` Stephen Boyd
2014-07-10 14:26 ` Maxime Ripard
2014-07-10 15:18 ` Alexandre Belloni
2014-07-10 15:41 ` Grygorii Strashko
2014-07-10 15:09 ` Maxime Ripard
2014-09-11 21:59 ` Stephen Boyd
2014-09-16 10:16 ` Maxime Ripard
2014-07-09 11:49 ` Peter De Schrijver
2014-07-21 15:51 ` Stephen Warren
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=20140709083509.GQ13423@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).