From nobody Mon Aug 14 05:03:19 2023 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 4RPMjp67Jqz4mMWn for ; Mon, 14 Aug 2023 05:03:26 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RPMjp1Wv7z3NtB for ; Mon, 14 Aug 2023 05:03:26 +0000 (UTC) (envelope-from manu@bidouilliste.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1691989404; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ZOxD468em2RhjcHyXyqJGjCg32fsFFYTPeqlirQmSkg=; b=i/mcshBgsLGvJXKNOfn75OpBFcdoI3BAN2DlE/bASMb8ltf6og/Kg9cHzzDT0v6UWHQwIg U+QKkH8ws/DY1EL3gAKOOuwM0VFwNe+qYZnpoNiT01xp6CbgWKvX28mHDxE1hyU8eQjZ2q oAYhKkyCqB2/JIlDj55uS8QPlpo3X0g= Received: from skull.home.blih.net (lfbn-lyo-1-2174-135.w90-66.abo.wanadoo.fr [90.66.97.135]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 488638da (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Mon, 14 Aug 2023 05:03:22 +0000 (UTC) Date: Mon, 14 Aug 2023 07:03:19 +0200 From: Emmanuel Vadot To: Mike Karels Cc: freebsd-arm Subject: Re: ALPHA1 on Raspberry Pi 3B+ [added: and RPi4B] Message-Id: <20230814070319.1d04005ae92b8c0bc0ccf025@bidouilliste.com> In-Reply-To: References: <1C94FEAF-C616-498F-8562-2E99CF12417D@edc.ro> <4F7960AE-F607-4FEF-8A02-2013862A37E3@yahoo.com> <20230813191924.1b9b7927f0d98ce9937a571f@bidouilliste.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4RPMjp1Wv7z3NtB X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR] On Sun, 13 Aug 2023 12:35:31 -0500 Mike Karels wrote: > On 13 Aug 2023, at 12:19, Emmanuel Vadot wrote: > > > On Sun, 13 Aug 2023 11:25:25 -0500 > > Mike Karels wrote: > > > >> On 13 Aug 2023, at 11:10, Mark Millard wrote: > >> > >>> On Aug 13, 2023, at 08:17, Warner Losh wrote: > >>> > >>>> Manu just updated Linux DTS in the tree. Maybe see if you revert that if the problem persists. > >>> > >>> git: 69f8cc60aa1e - main - ofw_firmware: Only match if there is no compatible > >>> > >>> is the fix that Manu has committed: > >>> > >>> QUOTE > >>> ofw_firmware: Only match if there is no compatible > >>> > >>> If there is a compatible string it likely means that the firmware needs > >>> a dedicated driver (like on RPI*). > >>> > >>> PR: 273087 > >>> Tested-by: Mark Millard > >>> Sponsored by: Beckhoff Automation GmbH & Co. KG > >>> Fixes: fdfd3a90b6ce ("ofw: Add a ofw_firmware driver") > >>> END QUOTE > >> > >> Just for completeness: that change fixes the bcm2835_cpufreq0/powerd > >> problem and the gpioled0 problem, but not the clk_fixed2 problem > >> (clk_fixed4 on rpi4). Installing an msdos boot partition from the > >> 3 Aug image makes that problem disappear. > >> > >> Mike > > > > There is two fixed-clock in the DTB without clock-frequency property > > and with a status set to "disabled", this isn't conforming to the > > bindings > > (https://cgit.freebsd.org/src/tree/sys/contrib/device-tree/Bindings/clock/fixed-clock.yaml) > > so we complain on this, this is normal. > > Would it be possible to detect the disabled status to prevent the errors > (I'm guessing not) or to suppress the repeats? 150 lines of errors seems > like a lot for an out-of-spec DTB entry, and makes it hard to ignore. > > Mike Detecting the disabled status makes no sense, a fixed clock cannot be disable, it's always present and running. But I think that if we check that clock-frenquency isn't present in the probe function, print a message and bail we will not attempt to attach the driver at each pass. That's the only clean solution that I can see without making dirty hacks for some non-conforming DTB. -- Emmanuel Vadot