Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp800586ybl; Thu, 22 Aug 2019 05:12:23 -0700 (PDT) X-Google-Smtp-Source: APXvYqy05CyvgwXbjd/cFgDifAw078dLjq3nXzXWBE1JHJdBQUiv8EWb00eJ5ga7GGjvMdOdYl0u X-Received: by 2002:aa7:9719:: with SMTP id a25mr41868248pfg.2.1566475942997; Thu, 22 Aug 2019 05:12:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566475942; cv=none; d=google.com; s=arc-20160816; b=tpSgGCA9uVHgIM1XcWGit+tO9r1NlkGd5osP5J7AiVoYAg8mvfM11qxq0vZuuU+UkM AkVJ1evxOTMM2ZRW7Pzrbgj5p6C+Ipi4SdyIwrow1Puov3Ycl+z90AoBEj183gq3jCNS e8YxxK+jR0Gih5Q4HQGamZDm3FiZswjaOdJbF/VkF3Vme7LBf1jaHjxUqExne8zS+xrs 6DoJLruD94dgsnvc4Zag567AvSTEEc70Tic0y+GMjnwMxTnHohU0wbxlEk/1dTC7cBYn pMsbmiD2ehaACuudiR9/f/Atbgx1BR9ZWR/+wUQyB+5CmafTMCUVAJIIzdT6+Ba0+7w+ TTaA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=cRrXk0WJHYhhSEQe8VMKsPyqg+wqkCPcN1SylzUsneA=; b=v5Nkf7IWKpo6Fh4rqfaE2NyTFBYCDAEyRz2ZZgchFVaUXwmy7Tx4H2dpwNzSBmNJY7 nZP7tIW5Y7tO5KrU47EO11wlUnzF76YYCSLJXlCQyqCPLoIKsQ3cdJn7jYiTjyDA3xhv hslRl4gdF8YxipKVFPZdc4/2DnhYNWurQDysgLU8Uu5D0foMc1P+O51ZWN1egjoRJu5c eqZaKj0MBzJQpWbu5s1SPPY4C5Ogbyt46BElaR+yVXVQ/LWf16bL7CSpm5LaSaevw5Kn zWFjp4QZDpe86+60smg8J3W5NQwF7dIzXIUHCzmo+gCebnJrP0R9acrnrrmXsMnT5u1i uSsQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d9si16367267pgq.119.2019.08.22.05.12.05; Thu, 22 Aug 2019 05:12:22 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733172AbfHVJUO (ORCPT + 99 others); Thu, 22 Aug 2019 05:20:14 -0400 Received: from relay8-d.mail.gandi.net ([217.70.183.201]:55365 "EHLO relay8-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725873AbfHVJUO (ORCPT ); Thu, 22 Aug 2019 05:20:14 -0400 X-Originating-IP: 86.207.98.53 Received: from localhost (aclermont-ferrand-651-1-259-53.w86-207.abo.wanadoo.fr [86.207.98.53]) (Authenticated sender: alexandre.belloni@bootlin.com) by relay8-d.mail.gandi.net (Postfix) with ESMTPSA id A5BF61BF206; Thu, 22 Aug 2019 09:20:08 +0000 (UTC) Date: Thu, 22 Aug 2019 11:20:08 +0200 From: Alexandre Belloni To: Matthias Brugger Cc: Ran Bi , Rob Herring , Alessandro Zummo , Mark Rutland , Mauro Carvalho Chehab , "David S . Miller" , Greg Kroah-Hartman , Jonathan Cameron , Linus Walleij , Nicolas Ferre , linux-rtc@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, srv_heupstream@mediatek.com, YT Shen , Eddie Huang , Yingjoe Chen , Flora Fu , Sean Wang Subject: Re: [PATCH v2 2/4] rtc: Add support for the MediaTek MT2712 RTC Message-ID: <20190822092008.GR27031@piout.net> References: <20190801110122.26834-1-ran.bi@mediatek.com> <20190801110122.26834-3-ran.bi@mediatek.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 22/08/2019 11:12:29+0200, Matthias Brugger wrote: > > > On 01/08/2019 13:01, Ran Bi wrote: > > This add support for the MediaTek MT2712 RTC. It was SoC based RTC, but > > had different architecture compared with MT7622 RTC. > > > > Signed-off-by: Ran Bi > > --- > > drivers/rtc/Kconfig | 10 + > > drivers/rtc/Makefile | 1 + > > drivers/rtc/rtc-mt2712.c | 444 +++++++++++++++++++++++++++++++++++++++ > > Can't we just adjust rtc-mt7622.c (and rename it) to unify the source for both > devices. What is the difference that we need to write a driver of our own? > If they are compatible, this is the way to go but the file can't be renamed (and that is fine). -- Alexandre Belloni, Bootlin Embedded Linux and Kernel engineering https://bootlin.com