From owner-freebsd-arm@freebsd.org Wed Jul 12 03:11:49 2017 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 3702DDB1975 for ; Wed, 12 Jul 2017 03:11:49 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1CB537686B for ; Wed, 12 Jul 2017 03:11:48 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: c98d5838-66af-11e7-a4a1-c9e62e5d9688 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id c98d5838-66af-11e7-a4a1-c9e62e5d9688; Wed, 12 Jul 2017 03:11:24 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v6C3Bduh044681 for ; Tue, 11 Jul 2017 21:11:39 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1499829099.45330.36.camel@freebsd.org> Subject: i2c realtime clocks now work From: Ian Lepore To: "freebsd-arm@FreeBSD.org" Date: Tue, 11 Jul 2017 21:11:39 -0600 Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit 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: Wed, 12 Jul 2017 03:11:49 -0000 In the past it wasn't possible to use i2c rtc chips/modules on some arm boards because the i2c driver would trigger a witness assertion about sleeping while holding locks.  The only option was to use sysctl to set machdep.disable_rtc_set=1 if your board had an i2c clock. As of r320902 that restriction is removed and i2c clocks should work on all systems. -- Ian