Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp1285113rwb; Thu, 15 Dec 2022 08:22:00 -0800 (PST) X-Google-Smtp-Source: AA0mqf4hhu/X9nvC+IHrf4NzD3QOHU8xFS6AGnnVggTyzV+C6hweQ5yED6Wjgef7BYGN2drOeWDa X-Received: by 2002:a05:6a21:328d:b0:a9:d06b:440b with SMTP id yt13-20020a056a21328d00b000a9d06b440bmr43740800pzb.30.1671121319997; Thu, 15 Dec 2022 08:21:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1671121319; cv=none; d=google.com; s=arc-20160816; b=nb6ZJbzXYis+Y2IppFPIfxAeyVPJGnDrispjucoaDIQBoo0gqciR93bFU/62q7UMcY 2JCWJeCu2ta5c+Cp2AYEI2dnrXPnj/4yX/7+wMh4s3rnca/qEu7SOwrr5dKvTI57v/bJ K4NAMkgxkS3o0FncTHjRRRa22Z7bODZwRifxjETVQe8BGWXAbuBje0wQ4JOxNB8EWfvb n2bgHPIWlRFZgnllkhs2v30sIyhh5FA9ZomRlPPeWSKVXbNPyKOdiyImGdv2SiO+/Mkt J53CGU0bLbToVNSmEn8hi2TAjsSgAW8QxyMcQSwZbqtlAi7+9ZsnmXijsHAHp/5atiCl Isqg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:subject:content-transfer-encoding:mime-version :message-id:date:cc:to:from:dkim-signature; bh=USYqznAH4SDqUevncPOHC9VofBQznPJDAAswThOanBE=; b=oXlxCtIlqiIM6duhULBHjlRpAqZJW7ycqBC2ph9a2n9QMXoFb5WDVualHFSsChZTQ5 uNrl1lnXhooiL01SK5jELWleAB2snWgLnnJJrV6Arie6bXFm3OpOmVzhcfRM9VmcR2v/ sWA2svvOhcfrvOI/mcJG41PBFz+0UpUcdgFEm2Wi3fZDSXE/j/AJf4zBvbKvUoaY1AvD VhXNCa0LtRPzt/uPTemKVEpDsksNKcgP11pTq7t/9cNQ1dHRQGx8hoqIXFdDZnt9DwI6 thdLM5BJKKpXvCgHRq3wbTVeO7yUWQJDhlQoqKY2TlcJaidwJTQFuvp5/giT7VIpS8T5 /G5w== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@hugovil.com header.s=x header.b=HLMplgt8; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id x123-20020a636381000000b0048118aa6359si3321142pgb.309.2022.12.15.08.21.50; Thu, 15 Dec 2022 08:21:59 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=fail header.i=@hugovil.com header.s=x header.b=HLMplgt8; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230280AbiLOPUh (ORCPT + 68 others); Thu, 15 Dec 2022 10:20:37 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48136 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230062AbiLOPTy (ORCPT ); Thu, 15 Dec 2022 10:19:54 -0500 Received: from mail.hugovil.com (mail.hugovil.com [162.243.120.170]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D26B032B8B; Thu, 15 Dec 2022 07:18:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=hugovil.com ; s=x; h=Subject:Content-Transfer-Encoding:MIME-Version:Message-Id:Date:Cc:To :From:Sender:Reply-To:Content-Type:Content-ID:Content-Description:Resent-Date :Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To: References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:List-Post: List-Owner:List-Archive; bh=USYqznAH4SDqUevncPOHC9VofBQznPJDAAswThOanBE=; b=H LMplgt81ZSsISkJ2Fta+lVkPgewzjrt6F/34vbmwcWgLOk9wRLhytxMBD2tNM4yv15XybMtglwjZx pqI7XYOejDOoYw7yFqLZ7f2OuBK8m8LYXHBqOI/gkTtGKruavQtN+wmICMQhqmDG8xkz5x/ib7+um 5gfftwAIZCTiYiB8=; Received: from modemcable168.174-80-70.mc.videotron.ca ([70.80.174.168]:48102 helo=pettiford.lan) by mail.hugovil.com with esmtpa (Exim 4.92) (envelope-from ) id 1p5pm2-0000EC-4n; Thu, 15 Dec 2022 10:03:50 -0500 From: Hugo Villeneuve To: a.zummo@towertech.it, alexandre.belloni@bootlin.com, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org Cc: linux-rtc@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, hugo@hugovil.com, Hugo Villeneuve Date: Thu, 15 Dec 2022 10:02:01 -0500 Message-Id: <20221215150214.1109074-1-hugo@hugovil.com> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SA-Exim-Connect-IP: 70.80.174.168 X-SA-Exim-Mail-From: hugo@hugovil.com X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 Subject: [PATCH v3 00/14] rtc: pcf2127: add PCF2131 driver X-SA-Exim-Version: 4.2.1 (built Wed, 08 May 2019 21:11:16 +0000) X-SA-Exim-Scanned: Yes (on mail.hugovil.com) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Hugo Villeneuve Hello, this patch series adds the driver for the PCF2131 real-time clock. This RTC is very similar in functionality to the PCF2127/29 with the following differences: -supports two new control registers at offsets 4 and 5 -supports a new reset register -supports 4 tamper detection functions instead of 1 -has no nvmem (like the PCF2129) -has two output interrupt pins instead of one -has 1/100th seconds capabilities (not supported in this driver) -pcf2127 has watchdog clock sources: 1/60, 1, 64 and 4096Hz pcf2131 has watchdog clock sources: 1/64, 1/4, 4 and 64Hz -watchdog value register cannot be read after being set Most of the register addresses are very different, although they still follow the same layout. For example, the time/date and tamper registers have a different base address, but the offsets are all the same. Consequently, the source code of the PCF2127 driver can be easily adapted to support this new device. Patches 1 to 6 modify the existing pcf2127 driver to make it more generic and able to support multiple variants, like the PCF2131. This is done mostly by using offsets instead of absolute hardcoded register addresses. Patch 7 add actual support for the PCF2131. Patch 8 configures all interrupt sources to go through the INT A pin. Patch 9 changes the PWRMNG bits to be the same with the PCF2131 as they are with the PCF2127/29 (different default values). Patch 10 allow to confirm PCF2131 device presence by reading the reset register fixed pattern. Patch 11 adapt the time/date registers write sequence for PCF2131 (STOP and CPR bits). Patch 12 add support for generic watchdog timing configuration. Patch 13 add a new flag to identify if device has read support for reading watchdog register value. Since the watchdog value register cannot be read on the PCF2131 after being set, it seems that we cannot detect if watchdog timer was started by bootloader. I am not sure what is the best way to handle this situation, suggestions are welcomed. Patch 14 add the dt-bindings for the PCF2131. I have tested the driver using a PCF2131-ARD evaluation board connected to an NXP imx8mp evaluation board: - Time get/set ok; - Alarms get/set ok - Timestamp 1 to 4 ok - IRQ alarm ok - Watchdog ok - Also tested successfully with "RTC Driver Test Example" from Documentation/rtc.txt I have also tested the driver on a custom PCF2129 adapter board connected to a beaglebone black. Thank you. Link: [v1] https://patchwork.ozlabs.org/project/rtc-linux/patch/20220125200009.900660-2-hugo@hugovil.com/ Link: [v2] https://patchwork.ozlabs.org/project/rtc-linux/list/?series=285734 Changes for V3: - Rebased for kernel v6.1 Changes for V2: - In general, fix and improvements after I have tested on real hardware - Fix alarm interrupt A/B mask setting for PCF2131: PCF2131_BIT_INT_AIE must be cleared, not set, to enable interrupt. - Remove low_reg validation: only check if TS interrupt flag is defined, as low_reg is defined at address 0 for PCF2127/29. - Change PWRMNG value for PCF2131: default is different than PCF2127/29. - Adapt time/date registers write sequence for PCF2131 (STOP and CPR bits). - Map all interrupt sources to INT A pin - Read and validate PCF2131 device presence from RESET register - Adapt watchdog configuration for PCF2131 Hugo Villeneuve (14): rtc: pcf2127: add variant-specific configuration structure rtc: pcf2127: adapt for time/date registers at any offset rtc: pcf2127: adapt for alarm registers at any offset rtc: pcf2127: adapt for WD registers at any offset rtc: pcf2127: adapt for CLKOUT register at any offset rtc: pcf2127: add support for multiple TS functions rtc: pcf2127: add support for PCF2131 RTC rtc: pcf2127: add support for PCF2131 interrupts on output INT_A rtc: pcf2127: set PWRMNG value for PCF2131 rtc: pcf2127: read and validate PCF2131 device signature rtc: pcf2127: adapt time/date registers write sequence for PCF2131 rtc: pcf2127: support generic watchdog timing configuration rtc: pcf2127: add flag for watchdog register value read support dt-bindings: rtc: pcf2127: add PCF2131 .../devicetree/bindings/rtc/nxp,pcf2127.yaml | 4 +- drivers/rtc/Kconfig | 4 +- drivers/rtc/rtc-pcf2127.c | 939 ++++++++++++++---- 3 files changed, 752 insertions(+), 195 deletions(-) -- 2.30.2