From nobody Sun Jan 07 17:26:40 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T7PJ54n6gz55TjZ for ; Sun, 7 Jan 2024 17:26:45 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4T7PJ44d0nz4JcY for ; Sun, 7 Jan 2024 17:26:44 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm2 header.b=Et4rQpS4; dkim=pass header.d=messagingengine.com header.s=fm2 header.b="W cQiNE8"; dmarc=pass (policy=none) header.from=f-m.fm; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.25 as permitted sender) smtp.mailfrom=void@f-m.fm Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 3873C3200A76 for ; Sun, 7 Jan 2024 12:26:43 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Sun, 07 Jan 2024 12:26:43 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1704648402; x=1704734802; bh=eYpzBqNAnzGnpWVksQh4E8tOXd+GMea6eGQpucj+YpY=; b= Et4rQpS4kgV1ktWO20KOIpRBEqQeIhLrbuHuUKhYE5Mwn/FBRrU0Khy44nIVbuZh Y7NyesTwDU6PNwhCyv3yxZke6ZQhRWgUuNk4pAsW24UZk2QbDJ3Ov/vnos9koa0l dJxntOReh2/OiTqRB1M7MXM6CkWIshiFNxHBAp6zJzp25Z9eBvaqCXCnPgZtIxdk fJTUibacLbrE+/OYz4FXbQTreT8ARtduXU2w8wRRWx32TZuunAl/XDk7ADN7KhWA KnHtZL7nnX7D0s4mGN5PPOIVcDRhw6Bs/C36yn40qf7BDcVSyZSBBfr5VUI5quGR BisettFLSn8q2kUwP+27+w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1704648402; x= 1704734802; bh=eYpzBqNAnzGnpWVksQh4E8tOXd+GMea6eGQpucj+YpY=; b=W cQiNE8FAgtl7k5LlhzeFWBL9D4Y/ojTBD9ZTxtIJsS3AcN1e6h1m738OZfpiJ9m+ LRzl9qaPlNoI2zZjisQkPVAgs22j1yKP+BpZWEe124AywzG6giJNm8JKNaBEcxSg dYFBstawRqtdUkrHv5h+i1tUY0dB42CifPTkidxIZ3UklYelQaD9wdq+JCCsoX/c bUPzzaeeuO5BQm1BL56gbMmlmmGfL2IYsw/RHLWn1mncFrKh4typzo8eu1GST4r/ +URHq8DlUJ4XyGsViKSFWyZ0hOzL8gEvYsD80js1FS5o0p19YW5GRLAKoht4SGcz NYE2UJtVFUjH4YgBdcqHA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdehgedggedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggugfgjsehtqh ertddttddvnecuhfhrohhmpehvohhiugcuoehvohhiugesfhdqmhdrfhhmqeenucggtffr rghtthgvrhhnpefgvefhudejgfefledtgedvtdekudeltdeftdeugedtlefgvdffteevff etueevgfenucffohhmrghinhepfhhrvggvsghsugdrohhrghenucevlhhushhtvghrufhi iigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehvohhiugesfhdqmhdrfhhm X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sun, 7 Jan 2024 12:26:42 -0500 (EST) Date: Sun, 7 Jan 2024 17:26:40 +0000 From: void To: freebsd-arm@freebsd.org Subject: Re: enabling powerd on RPi Message-ID: Mail-Followup-To: freebsd-arm@freebsd.org References: <136EA428-CC30-4CF4-BE65-30B0CC8656AF@karels.net> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <136EA428-CC30-4CF4-BE65-30B0CC8656AF@karels.net> X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.60 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm2,messagingengine.com:s=fm2]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.25:c]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.25:from]; FREEMAIL_FROM(0.00)[f-m.fm]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_THREE(0.00)[3]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; MISSING_XM_UA(0.00)[]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim] X-Rspamd-Queue-Id: 4T7PJ44d0nz4JcY On Thu, Jan 04, 2024 at 07:53:12AM -0600, Mike Karels wrote: >On 28 Dec 2023, at 13:11, Mike Karels wrote: > >> I am looking at enabling powerd by default on the Raspberry Pi 4 and may= be >> others. There is a bug from 2021 on the subject which has gotten some r= ecent >> discussion, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256836. = Also, >> problems come up from time to time about performance problems because pe= ople >> don't know to enable powerd. It makes FreeBSD look much slower than Lin= ux. >> >> The simplest action is to enable powerd by default on the arm64-aarch64-= RPI >> images. This would affect RPi 4 and variants, also RPI 3* and later RPi= 2. >> I enabled powerd on an RPi 3B+, and it seems to have no issues; it seems >> to work. Does anyone know of a disadvantage of enabling powerd on RPI >> images for all targets? The alternative would be to configure at the fi= rst >> boot, although I'm not positive of a definitive way to identify the RPi >> variants. Maybe just looking for a dev.cpu.0.freq sysctl node would >> suffice. >> >> If no one objects, I will make changes to enable powerd on RPI snapshots >> for 15-current, and we can see what happens. > >My change to enable powerd for all 64-bit Raspberry Pi systems using the >arm64-aarch64-RPI image is in https://reviews.freebsd.org/D43296. There is >also a review that splits RPi4 from RPi3 (etc); it is >https://reviews.freebsd.org/D43141. Comments welcome. I think powerd by default would be advantageous in most use cases.=20 It would be particularly useful in a battery-powered context. I used to use powerd a lot, but it's not needed for my own uses right now,= =20 so it's disabled and i overclock by firstly having really efficient cooling= =20 and then setting config.txt like this hdmi_safe=3D0 armstub=3Darmstub8-gic.bin gpu_mem=3D16 over_voltage=3D6 arm_freq=3D2147 gpu_freq=3D750 force_turbo=3D1 # sysctl dev.cpu.0 dev.cpu.0.temperature: 51.0C dev.cpu.0.freq_levels: 2147/-1 dev.cpu.0.freq: 2147 dev.cpu.0.%parent: cpulist0 dev.cpu.0.%pnpinfo: name=3Dcpu@0 compat=3Darm,cortex-a72=20 dev.cpu.0.%location:=20 dev.cpu.0.%driver: cpu dev.cpu.0.%desc: Open Firmware CPU My context here is permanently connected to the recommended PSU, headless w= ith serial console and UPS, and it needs to be responsive, which it is with this overclock. If I were to use powerd in this context, it would never realise the full ov= erclock and shows dev.cpu.0.freq_levels: 2100/600. Connected to it is a usb<>ttl serial cable on the rpi4's pins which is conn= ected to a rpi2b+ running 12.2-RELEASE which is used as a "console server". There is no conso= le scrambling. Console is invoked on the rpi2b+ with 'cu -l cuaU1 -s 115200' =7F --=20