From mboxrd@z Thu Jan 1 00:00:00 1970 From: Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= Subject: Re: a case for a common efuse API? Date: Wed, 9 Jul 2014 09:24:20 +0200 Message-ID: <20140709072420.GI7827@pengutronix.de> References: <53BC4DD7.20906@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <53BC4DD7.20906-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Stephen Boyd Cc: "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Stephen Warren , Arnd Bergmann , "linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Peter De Schrijver , Linux Kernel Mailing List , Bjorn Andersson List-Id: devicetree@vger.kernel.org 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 thing= s > 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 --=20 Pengutronix e.K. | Uwe Kleine-K=F6nig = | Industrial Linux Solutions | http://www.pengutronix.de/= | -- To unsubscribe from this list: send the line "unsubscribe devicetree" i= n the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html