From owner-freebsd-arm@freebsd.org Thu Nov 3 11:35:02 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4CA74C2DCF4 for ; Thu, 3 Nov 2016 11:35:02 +0000 (UTC) (envelope-from freebsd-arm@dino.sk) Received: from mailhost.netlabit.sk (mailhost.netlabit.sk [84.245.65.72]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 96AD512F7 for ; Thu, 3 Nov 2016 11:35:00 +0000 (UTC) (envelope-from freebsd-arm@dino.sk) Received: from zeta.dino.sk (fw3.dino.sk [84.245.95.254]) (AUTH: LOGIN milan) by mailhost.netlabit.sk with ESMTPA; Thu, 03 Nov 2016 12:34:51 +0100 id 00E88480.581B20DB.00015D1C Date: Thu, 3 Nov 2016 12:34:45 +0100 From: Milan Obuch To: Jared McNeill Cc: freebsd-arm@freebsd.org Subject: Re: aw_thermal breakage on Allwinner H3 SoC Message-ID: <20161103123445.6bcc4799@zeta.dino.sk> In-Reply-To: References: <20161024165820.16e6dd6f@zeta.dino.sk> <20161025180314.38ea1e96@zeta.dino.sk> <20161025202609.0958c55d@zeta.dino.sk> <20161025213913.310b502e@zeta.dino.sk> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.29; i386-portbld-freebsd10.3) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2016 11:35:02 -0000 On Tue, 25 Oct 2016 17:38:55 -0300 (ADT) Jared McNeill wrote: > On Tue, 25 Oct 2016, Milan Obuch wrote: > > > One more observation: booting verbose shows following > > aw_thermal0: mem > > 0x1c25000-0x1c253ff irq 29 on simplebus0 aw_thermal0: #0: alarm 42C > > hyst 15C shut 65C > > > > which is for me wrong - shutdown temperature 65 degrees is > > unacceptably low. > > Agreed. Those numbers are the SoC default values. > > It looks like the thresholds should be defined in a thermal-zones > node in the dts, but there is none defined in sun8i-h3.dtsi. We'll > have to come up with some reasonable defaults, add them to our dts, > and then add support for reading the trip points to the aw_thermal > driver. > > Cheers, > Jared How could this get done? Do we have any example (in some other dts) how this definition should look like? Where do these vaules got read from? Regards, Milan