Re: Conflict DS1307 and MAX77620
- Reply: 風來散人 : "Re: Conflict DS1307 and MAX77620"
- In reply to: 風來散人 : "Conflict DS1307 and MAX77620"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 13 Nov 2023 11:40:27 UTC
> On 12 Nov 2023, at 22:29, 風來散人 <furaisanjin@gmail.com> wrote: > > Hello all. > > I found that a similar discussion was done almost 2 years ago. > > https://lists.freebsd.org/archives/freebsd-arm/2021-November/000600.html > > I'm using the official FreeBSD 13.2 release. > > uname -a > FreeBSD macavity 13.2-RELEASE-p4 FreeBSD 13.2-RELEASE-p4 GENERIC arm64 > freebsd-version -kru > 13.2-RELEASE-p4 > 13.2-RELEASE-p4 > 13.2-RELEASE-p5 > > I created overlay dtb files for i2c and ds1307, and loaded them at boot. FreeBSD detected ds1360 as MAX77620 like below. > > Nov 12 16:17:18 localhost kernel: rtc1: <MAX77620 RTC> at addr 0xd0 on iicbus0 > Nov 12 16:17:18 localhost kernel: rtc1: registered as a time-of-day clock, resolution 1.000000s > > My SBC just has Allwinner H5 and nothing like tegra210. I created a custom kernel to remove tegra210. The custom kernel is fine and can detect ds1307 correctly. > > Nov 13 06:21:52 localhost kernel: ds13070: <Dallas DS1307> at addr 0xd0 on iicbus0 > Nov 13 06:21:52 localhost kernel: ds13070: registered as a time-of-day clock, resolution 1.000000s > > Is there any way to disable max77620 without creating a custom kernel? It looks like this might have been fixed in https://cgit.freebsd.org/src/commit/?id=a534b50e245d8, however this wasn’t MFCd to the stable/13 branch. You could try cherry-picking that patch, or test with 14-RELEASE when it’s released to see if it helps. Andrew