From nobody Mon Nov 13 12:18:21 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 4STT4P6mVbz50Pfc for ; Mon, 13 Nov 2023 12:19:01 +0000 (UTC) (envelope-from furaisanjin@gmail.com) Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4STT4P4kV1z4WVC for ; Mon, 13 Nov 2023 12:19:01 +0000 (UTC) (envelope-from furaisanjin@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x52c.google.com with SMTP id 4fb4d7f45d1cf-5441305cbd1so6733028a12.2 for ; Mon, 13 Nov 2023 04:19:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699877939; x=1700482739; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=7/SGgoARbo+1bT24kEUZnaK6A4tht47N2UZDE5COnBg=; b=RYVf9WYPm3mz1UlLHgOS+gLp4yrxADR008WccOi56gNdfCBcG+sWYYBRiW9sYBBwLQ 4U9v6HJz1eBq/7SMd7EupoMgoh7KuHv3qZrx1h4JFrquh1w1bi7zxx9leeJkjm8WbcKY 674YR9yWDHOLavyleKROrtlNfAAjm4n6sbb7ZZIWuYp+kVsZsUbCZezu+2Oo6VnwsQzZ 86tjA17PtrGZ+Z/ZHrNO+I9kl9wP55h0s3+h3L8rtgYQx154RzW9iX3yfJgFvYv8DRnH P0dFhCqEGcg7+NlhCRUJoYQUgUi7CjA+JHMj/O9TCIwp1mHgntmyEJ0LvLx2dFE1/mKO b3ZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699877939; x=1700482739; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=7/SGgoARbo+1bT24kEUZnaK6A4tht47N2UZDE5COnBg=; b=g2bkdDYfWA7I9L8GJIJ9AvLEry09GeEuDqsr6ufvOcVjNP1sfeaMdPbVs3eFl9Zq38 FLzA1sRFNozMGxXgl9AAvlItdCrIpTAdVrfPb6u38fm3mVc5Dhnilc3DwqRMic7o0nEY 7qnUmT80QHd9AEMwtYHUaAD29US7oxkTybXOLNlNIO+PK/tJzjL/6Ax5QsWzmulIOfrv MSFGMvSYXm1GxVS+/NKXPFaDbfhZg7fFhhLgqoyU2FQF0z5fuiy82xJ9RScII7FdtdVu v0ycKRoUPeC1RhOrdeWJbfj2FeoHaZuiB3Tas/DhltyenM02T2jQJChhJWkjetGOJV8q l+KA== X-Gm-Message-State: AOJu0Ywk8gYd38E8cMxcciHVh3tqhraWGscVUeOWYIW01sHnl4hml1Kk +TnDm8A4T51bO2sq3BIFmIKc5ppgb/8nvHtEqYE+KuTZ+r5myA== X-Google-Smtp-Source: AGHT+IG/PVc49i8+EdlTnbWicwv/a2ZAK3HOKK4XcU5Ay/rhvxwnYO/IRzjhjEQSus0HHKI9Ym2t8tKP1mlVDJvycoY= X-Received: by 2002:aa7:d84a:0:b0:53e:4762:9373 with SMTP id f10-20020aa7d84a000000b0053e47629373mr4068092eds.18.1699877939107; Mon, 13 Nov 2023 04:18:59 -0800 (PST) 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 References: <44B013F8-F710-4CD7-82ED-71B413186346@fubar.geek.nz> In-Reply-To: <44B013F8-F710-4CD7-82ED-71B413186346@fubar.geek.nz> From: =?UTF-8?B?6aKo5L6G5pWj5Lq6?= Date: Mon, 13 Nov 2023 21:18:21 +0900 Message-ID: Subject: Re: Conflict DS1307 and MAX77620 To: Andrew Turner Cc: FreeBSD ARM List Content-Type: multipart/alternative; boundary="000000000000b8dbeb060a07ac53" 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:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4STT4P4kV1z4WVC --000000000000b8dbeb060a07ac53 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello all. Thank you for the comments. I tried 14,0-RC4 and it worked as expected. I will switch to 14.0 once it is released. Best regards, furaisanjin 2023=E5=B9=B411=E6=9C=8813=E6=97=A5(=E6=9C=88) 20:40 Andrew Turner : > > On 12 Nov 2023, at 22:29, =E9=A2=A8=E4=BE=86=E6=95=A3=E4=BA=BA 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: 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 custo= m > kernel to remove tegra210. The custom kernel is fine and can detect ds130= 7 > correctly. > > Nov 13 06:21:52 localhost kernel: ds13070: at addr 0xd0 o= n > 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=3Da534b50e245d8, however this > wasn=E2=80=99t MFCd to the stable/13 branch. You could try cherry-picking= that > patch, or test with 14-RELEASE when it=E2=80=99s released to see if it he= lps. > > Andrew > > --000000000000b8dbeb060a07ac53 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello all.

Thank you for the= comments. I tried 14,0-RC4 and it worked as expected. I will switch to 14.= 0 once it is released.

Best regards,
fur= aisanjin

2023=E5=B9=B411=E6=9C=8813=E6=97=A5(=E6=9C=88) 20:40 Andr= ew Turner <andrew@fubar.geek.nz<= /a>>:

Hello all.

I found that a similar di= scussion was done almost 2 years ago.


I'm using the official FreeB= SD 13.2 release.

uname -a
FreeBSD macavity 13.2= -RELEASE-p4 FreeBSD 13.2-RELEASE-p4 GENERIC arm64
freebsd-version -kru13.2-RELEASE-p4
13.2-RELEASE-p4
13.2-RELEASE-p5

I created overlay dtb files for i2c and ds1307, and loaded them at bo= ot. 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 ha= s=20 Allwinner H5 and nothing like tegra210. I created a custom kernel to remov= e tegra210. The custom kernel is fine and can detect ds1307 correctly.

Nov 13 06:21:52 localhost kernel: ds13070: <Dallas DS130= 7> at addr 0xd0 on iicbus0
Nov 13 06:21:52 localhost kernel: ds1= 3070: 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 mig= ht have been fixed in=C2=A0https://cgit.freebsd.org/src/commit/?= id=3Da534b50e245d8, however this wasn=E2=80=99t MFCd to the stable/13 b= ranch. You could try cherry-picking that patch, or test with 14-RELEASE whe= n it=E2=80=99s released to see if it helps.

Andrew=

--000000000000b8dbeb060a07ac53--