Thread (16 messages) 16 messages, 11 authors, 2014-09-16

Re: a case for a common efuse API?

From: Uwe Kleine-König <hidden>
Date: 2014-07-09 07:24:36
Also in: linux-arm-kernel, linux-arm-msm, lkml

Hi,

On Tue, Jul 08, 2014 at 01:00:23PM -0700, Stephen Boyd wrote:
On MSM chips we have some efuses (called qfprom) where we store things
like calibration data, speed bins, etc.
I don't have something constructive to say here, just want to point out
that on efm32 there is something similar. It's called "Device
Information (DI) Page" and contains "calibration values, a
unique identification number and other useful data".

Currently it is unused in mainline, but in my tree I access it directly
to determine cpu type (part number, part family number and Production
ID), flash and ram size, and the calibration settings for the ADC.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help