From owner-freebsd-arm@FreeBSD.ORG Sun Feb 9 21:18:30 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C4589D8A; Sun, 9 Feb 2014 21:18:30 +0000 (UTC) Received: from homiemail-a1.g.dreamhost.com (caiajhbdcbhh.dreamhost.com [208.97.132.177]) by mx1.freebsd.org (Postfix) with ESMTP id A2E45183E; Sun, 9 Feb 2014 21:18:30 +0000 (UTC) Received: from homiemail-a1.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a1.g.dreamhost.com (Postfix) with ESMTP id D76B8348073; Sun, 9 Feb 2014 13:18:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=koffein.net; h= content-type:from:to:cc:subject:in-reply-to:references:date :message-id:content-transfer-encoding; s=koffein.net; bh=gMpR0xU wTq3ip2tkzCycLHFb314=; b=ZPn3EOo/W/MJdbCqmLouTqxRB5aLsFhja76s0pC pqbKIOh2d0nb5p9MriCUo4wCe4l34+p33F9SBL6FCTQHGXj/YAWXzpNXjPPNBA5P +H0FZ54rZjdBWnsUtLweUklkm2XrlhcXpfxFXxJjGsojBpVxwiDDrYCj8P3ALm4X pqOA= Received: from localhost (unknown [77.109.124.99]) (Authenticated sender: stl@koffein.net) by homiemail-a1.g.dreamhost.com (Postfix) with ESMTPA id 7AD2734806E; Sun, 9 Feb 2014 13:18:29 -0800 (PST) Content-Type: text/plain; charset=UTF-8 From: Steven Lawrance To: Ian Lepore Subject: Re: i.MX6 on-die temperature sensor In-reply-to: <1391897489.1196.60.camel@revolution.hippie.lan> References: <1391893231-sup-6174@luwak.koffein.net> <1391897489.1196.60.camel@revolution.hippie.lan> Date: Sun, 09 Feb 2014 22:17:23 +0100 Message-Id: <1391979228-sup-7658@luwak.koffein.net> User-Agent: Sup/git Content-Transfer-Encoding: quoted-printable Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Feb 2014 21:18:30 -0000 Excerpts from Ian Lepore's message of 2014-02-08 23:11:29 +0100: > On Sat, 2014-02-08 at 22:32 +0100, Steven Lawrance wrote: > > For the OCOTP (on-chip one-time-programmable memory) side of things, = I > > just followed the pattern in imx6_anatop.c, which is to provide publi= c > > methods for accessing its memory space. But it feels a bit dirty -- = I > > imagine there could be cases where you would have two similar blocks > > and things would fall apart. >=20 > The thing I did with anatop was a quick hack to get things going becaus= e > I have no idea what services that conglomeration of hardware needs to > provide to other entities (yet). ocotp is another thing I haven't > looked at much, but it might be easier to come up with a clean API it > can provide for other imx drivers. Well, without actually developing a product based on this SoC, I can't really foresee a need to write anything to the OTP memory, and, according to the docs, "all shadow registers are always readable through the APB bus except some secret keys regions" so there's probably no real urgency to implement reading directly from the fuses, either. I haven't had a good look to see if anything else interesting is written in there in production. --=20 Steven Lawrance stl@koffein.net