Received: by 10.192.165.148 with SMTP id m20csp468624imm; Fri, 4 May 2018 00:41:38 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqtVrpytfIxZT/quGCOrSpNCABbLhPyT3T6q8YMOOmkaUCAoScdAqgLZGzEV/Ks32VQb5ZS X-Received: by 10.98.80.80 with SMTP id e77mr26188923pfb.16.1525419698717; Fri, 04 May 2018 00:41:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525419698; cv=none; d=google.com; s=arc-20160816; b=DWGeiwJXeBfNYc7wbUDEOaFFfCsOCCI7xqJraQXPBIemLnQmOBRhcdPD2kz2nzWKKA qFiEMJopPkf4otCOLVaM835ULs53mYmrBR7Ba46a7ID92SFZqQ63bxrLbm7WhCUbvxZA UJoWLnhE781oM8VXqA6sxrYPeXMYB1z9NUuhf2y3L4dnXuRAu2eT+qEKafHPKie7pfv4 5tdqhWm+KdWAKL4LnOAkSJIDzVl7SZdaClK0BQTnq7YpZGC9G9ovQZ6GOE7e0WyrPwPp Wl8fEMGVMRmEhQH+7Vq1QHIry+q4Ch4MgSdGJChTU2EC1dT9tVtzFlDZJQtvcMs6s7hW Z8ew== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=bgT7dorUxnvKbYbHN2KzgNmHWHYQ0UMvRLM/ms3BIKg=; b=bvI35a5j5/P/x7bXn1wOxXN3PAjR7gqpvH1GIrVZ0TzdIThjyHM4eg9xgut14PioXC lO10edmyv3Ah24aeWx1l0zGKkumt124halff+viIPt07gVsgLLThMGke4HT/zYgcTY5s u4AXK+NRHq13gcNk2MH2DNzxnes26iCc9NDemRwKf7idsmEwn64xVNysphnf6Un9hPsZ 2r8dTR7yY6Kgbk1vk/M5C2oJpOsUWJX+j+ax3FX6nynb16Obi5xe5iyBVc1GjD17RqgP oGYJqVXigC5fL5NFPVRNwP1AUGWl+bfNrmhaqxk+xLohB/cZoiji/+X39uOqJLRCcsWY Be+A== 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 17-v6si12619878pgh.114.2018.05.04.00.41.24; Fri, 04 May 2018 00:41:38 -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 S1751598AbeEDHlM (ORCPT + 99 others); Fri, 4 May 2018 03:41:12 -0400 Received: from mx08-00178001.pphosted.com ([91.207.212.93]:42932 "EHLO mx07-00178001.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751199AbeEDHlI (ORCPT ); Fri, 4 May 2018 03:41:08 -0400 Received: from pps.filterd (m0046661.ppops.net [127.0.0.1]) by mx08-.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id w447cncI005674; Fri, 4 May 2018 09:40:32 +0200 Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by mx08-00178001.pphosted.com with ESMTP id 2hqd1k1xjt-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 04 May 2018 09:40:32 +0200 Received: from zeta.dmz-eu.st.com (zeta.dmz-eu.st.com [164.129.230.9]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 10DFA41; Fri, 4 May 2018 07:40:29 +0000 (GMT) Received: from Webmail-eu.st.com (sfhdag3node2.st.com [10.75.127.8]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id A54A8167C; Fri, 4 May 2018 07:40:29 +0000 (GMT) Received: from [10.201.21.58] (10.75.127.45) by SFHDAG3NODE2.st.com (10.75.127.8) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Fri, 4 May 2018 09:40:27 +0200 Subject: Re: [PATCH 3/4] dt-bindings: rtc: update stm32-rtc documentation for st,syscfg property To: Alexandre Belloni , Rob Herring CC: Amelie Delaunay , Alessandro Zummo , Mark Rutland , Maxime Coquelin , , , , References: <1524144103-21432-1-git-send-email-amelie.delaunay@st.com> <1524144103-21432-4-git-send-email-amelie.delaunay@st.com> <20180427025803.mn32y5xle2p6knn6@rob-hp-laptop> <20180503205351.GE10960@piout.net> From: Alexandre Torgue Message-ID: Date: Fri, 4 May 2018 09:40:16 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180503205351.GE10960@piout.net> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.75.127.45] X-ClientProxiedBy: SFHDAG6NODE2.st.com (10.75.127.17) To SFHDAG3NODE2.st.com (10.75.127.8) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-05-04_02:,, signatures=0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Alexandre, On 05/03/2018 10:53 PM, Alexandre Belloni wrote: > Amelie, > > On 26/04/2018 21:58:03-0500, Rob Herring wrote: >> On Thu, Apr 19, 2018 at 03:21:42PM +0200, Amelie Delaunay wrote: >>> RTC driver should not be aware of the PWR registers offset and bits >>> position. Furthermore, we can imagine that Disable Backup Protection (DBP) >>> relative register and bit mask could change depending on the SoC. So this >>> patch moves st,syscfg property from single pwrcfg phandle to pwrcfg >>> phandle/offset/mask triplet. >>> >>> Signed-off-by: Amelie Delaunay >>> --- >>> Documentation/devicetree/bindings/rtc/st,stm32-rtc.txt | 10 ++++++---- >>> 1 file changed, 6 insertions(+), 4 deletions(-) >>> >>> diff --git a/Documentation/devicetree/bindings/rtc/st,stm32-rtc.txt b/Documentation/devicetree/bindings/rtc/st,stm32-rtc.txt >>> index a66692a..00f8b5d 100644 >>> --- a/Documentation/devicetree/bindings/rtc/st,stm32-rtc.txt >>> +++ b/Documentation/devicetree/bindings/rtc/st,stm32-rtc.txt >>> @@ -14,8 +14,10 @@ Required properties: >>> It is required only on stm32h7. >>> - interrupt-parent: phandle for the interrupt controller. >>> - interrupts: rtc alarm interrupt. >>> -- st,syscfg: phandle for pwrcfg, mandatory to disable/enable backup domain >>> - (RTC registers) write protection. >>> +- st,syscfg: phandle/offset/mask triplet. The phandle to pwrcfg used to >>> + access control register at offset, and change the dbp (Disable Backup >>> + Protection) bit represented by the mask, mandatory to disable/enable backup >>> + domain (RTC registers) write protection. >> >> It's fine to add this, but you are breaking compatibility in the driver >> with existing DTBs by requiring these new fields. >> > > I'm fine with that change but I would like confirmation that this has > been well thought. Maybe Maxime or Alexandre could give their ack. > It's a good thing to remove PWR registers information from RTC driver. My only concern was the compatibility with old DT but we can accept it. Indeed, Kernel will continue to boot fine, only RTC will not probe if we use old DT. Acked-by: Alexandre TORGUE Regards alex