Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp869524ybg; Fri, 18 Oct 2019 08:34:09 -0700 (PDT) X-Google-Smtp-Source: APXvYqxoStYl80idoq2V0x2426za+eNshcvEIsSxzflE2racPqEM+w1PsgJTr1YbIOin/EkNy5Vi X-Received: by 2002:a17:906:3751:: with SMTP id e17mr9462458ejc.269.1571412849678; Fri, 18 Oct 2019 08:34:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571412849; cv=none; d=google.com; s=arc-20160816; b=C70WxoGriLQl2Z6FmGpypB10cOMOHGCE9ygf30BiM8ayoIhr5nGqYy50M0LR2Wdx52 UYB1MJAGD2IlsdrwqaaQc2osXxf3dOosq0wgZpLQ58t/FELSq0PrV2Kq7FXa3HaE8Zuq JzeBJzmcWjLkutRrGjmCtJG7DndU82w39wdrcEUw+q47tFsHoISasUkbbahzxUeN/Xdl XZwxBlbYlJ+kykbyOq0k2+sg6ZPj/hHR1zdIL8T/OPBLgHGNgYjDiEJdFpS5oNyGaVlV i9BhPnNrJRtcWT8QT5e0LTq3bRmDJtaWqLGf+MywtKWzBsDX62mWav9wd/NCL3Vn+2ab dfsg== 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=vDlokkN7r9m+7seb+7+PSxUhrL0LR4LdrOQAjWVCxC4=; b=KBFkCAx0/0PhYGTiUFHH+8jfEbFVHUs7c5xplQcM3dIM0sojGHkU+pV236BoUdfFCk e/7ZXPfgdunEOjYqhtMnXMJDevXorI6PTy+FdIpIdYMIFiW8XmORgZ6nSgueX9RzEsaU 5rLfWrAia1JMQZnXwlZzm7txt/qfRorVLDtxPn6Rj58z0F4ccG9AdNXq8g/G6Imp9kvp OaIqw9iprF1zdcUab3qXgAMZVbxIA620WxAnn+swuPq2RINV4x7LUhQJMdc9FiUbgrSp Llu/cQ/jQpOTTCb8sDV6RQr1p1p8dObps06+7mw/m802pzk7o8fqJnZ1M+ra5hSrk1fE 0yZw== 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 i23si3830291edr.191.2019.10.18.08.33.46; Fri, 18 Oct 2019 08:34:09 -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 S2408987AbfJQKtE (ORCPT + 99 others); Thu, 17 Oct 2019 06:49:04 -0400 Received: from relay3-d.mail.gandi.net ([217.70.183.195]:40285 "EHLO relay3-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404935AbfJQKtD (ORCPT ); Thu, 17 Oct 2019 06:49:03 -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 relay3-d.mail.gandi.net (Postfix) with ESMTPSA id 57C6360007; Thu, 17 Oct 2019 10:49:00 +0000 (UTC) Date: Thu, 17 Oct 2019 12:48:59 +0200 From: Alexandre Belloni To: "Vaittinen, Matti" Cc: "dmurphy@ti.com" , "linux-leds@vger.kernel.org" , "linux-rtc@vger.kernel.org" , "linux-gpio@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "mturquette@baylibre.com" , "mazziesaccount@gmail.com" , "devicetree@vger.kernel.org" , "jacek.anaszewski@gmail.com" , "a.zummo@towertech.it" , "linus.walleij@linaro.org" , "lgirdwood@gmail.com" , "mark.rutland@arm.com" , "robh+dt@kernel.org" , "bgolaszewski@baylibre.com" , "linux-clk@vger.kernel.org" , "pavel@ucw.cz" , "sboyd@kernel.org" , "broonie@kernel.org" , "lee.jones@linaro.org" Subject: Re: [RFC PATCH 09/13] mfd: rtc: support RTC on ROHM BD71828 with BD70528 driver Message-ID: <20191017104859.GC3125@piout.net> References: <9ccc83f3dfd0fd0dc8178adf41b52115f960c45a.1571302099.git.matti.vaittinen@fi.rohmeurope.com> <20191017101225.GB3125@piout.net> 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 17/10/2019 10:36:44+0000, Vaittinen, Matti wrote: > Hello Alexandre, > > Thanks for quick check! I'll be off for the rest of the week but I will > re-work this patch at next week :) I agree with you regarding most of > the comments. > > > > + > > > + > > > +/* > > > + * RTC definitions shared between > > > + * > > > + * BD70528 > > > + * and BD71828 > > > + */ > > > + > > > +#define ROHM_BD1_MASK_RTC_SEC 0x7f > > > +#define ROHM_BD1_MASK_RTC_MINUTE 0x7f > > > +#define ROHM_BD1_MASK_RTC_HOUR_24H 0x80 > > > +#define ROHM_BD1_MASK_RTC_HOUR_PM 0x20 > > > +#define ROHM_BD1_MASK_RTC_HOUR 0x3f > > > +#define ROHM_BD1_MASK_RTC_DAY 0x3f > > > +#define ROHM_BD1_MASK_RTC_WEEK 0x07 > > > +#define ROHM_BD1_MASK_RTC_MONTH 0x1f > > > +#define ROHM_BD1_MASK_RTC_YEAR 0xff > > > +#define ROHM_BD1_MASK_ALM_EN 0x7 > > > + > > > > All that renaming is distracting and useless. Please resubmit without > > renaming defines, structs and functions to make it easier to review. > > I would prefer renaming because it makes it clearly visible which > defines/structs/functions are common for both PMICs and which are PMIC > specific. But I really understand the problem of spotting real changes. > Would it be Ok if I did renaming in separate patch which does not bring > in any other changes - and then the functional changes in separate > patch? > No, unless you can guarantee that all future PMICs from rohm matching the wildcard will use this driver. -- Alexandre Belloni, Bootlin Embedded Linux and Kernel engineering https://bootlin.com