Message ID | 20230913151606.69494-1-romain.perier@gmail.com |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:612c:172:b0:3f2:4152:657d with SMTP id h50csp76755vqi; Wed, 13 Sep 2023 20:05:55 -0700 (PDT) X-Google-Smtp-Source: AGHT+IEJnvC5AbA91cFWqA91bxx5iX+7jrTLYqcDU9celfChl6wN3iV1kvFP643e3F7+oDf84Kw2 X-Received: by 2002:a17:902:7789:b0:1c1:fa12:5c1 with SMTP id o9-20020a170902778900b001c1fa1205c1mr3781107pll.55.1694660755390; Wed, 13 Sep 2023 20:05:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1694660755; cv=none; d=google.com; s=arc-20160816; b=OvDNIN8w39obp5VrhjBXfLtb/drNUHnPcyrGS2rmvQ1goikRVKhG7VpNvTHnxOspId jo+T0UKUjKRxgfJMUut8i48gjtVSe/eBhFUvep5Eyu+Y8lD2Cd9aB32tTXgp1oNad1e+ 0yjfYTNGS+C+oNVt2fQOLq98THvqQUDqUbeWwgWSPVHGcrh7ahvcxPdNzdQOa1QdL6b7 SpHexfC31jSrhJkbOT8N8uk61JYPrDffujxlledTZhQDL1AvN8//y6iVh6TTEJdTMNES 2ZS2wCTw8hPVAPaXpkmZKgUrLQjZunNp1GKzxxvoNwi//Oa5Zwd4Qfa1bqkaxBaYvHVh vzxA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=+wHlb4TZdTg18dIQRSMHj1vLV5U+xhED8U8Tcp/nIAY=; fh=9MoheE0NAb45q+jah/qcGpTE04FXDc2965AiLxmpSAs=; b=B4l5koxpKgxSqaEryhtPYIGPl9MNomTHFItYaivJXSSNFTqO+7M74rwJuNLJy+DS3h wwUrL6QfNdPEBTjtpvlf63toA3gynzdJGb0L3+iT6cDEMQvllylpUpSv2aP42NavrIvE kJODdpJxmE2HSbzDiqv7JwmoDN/L4PzNW14fXSigUd1H5xyHJ9pLk7qKdM4njBljXyFr Vou+FrukjuZux7k0irKBEVMf4SPbXl81HVaRpTupt5eKH6IOOEzqDBy7Quj6lyazrEjS zYDh/fK15Mx1H3AWSD8CECt17JEKeWwBYXod3z7nxzn/JSqwmdfOXbPPtZjotiUYfhWx Fouw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b=pt7b3ELN; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from lipwig.vger.email (lipwig.vger.email. [23.128.96.33]) by mx.google.com with ESMTPS id b21-20020a170902ed1500b001bb7ee817d3si681751pld.48.2023.09.13.20.05.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 13 Sep 2023 20:05:55 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) client-ip=23.128.96.33; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b=pt7b3ELN; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by lipwig.vger.email (Postfix) with ESMTP id D49B98043EEE; Wed, 13 Sep 2023 08:17:08 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at lipwig.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241578AbjIMPQb (ORCPT <rfc822;pwkd43@gmail.com> + 36 others); Wed, 13 Sep 2023 11:16:31 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39208 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230254AbjIMPQ1 (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Wed, 13 Sep 2023 11:16:27 -0400 Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D96AEBD; Wed, 13 Sep 2023 08:16:22 -0700 (PDT) Received: by mail-wm1-x32b.google.com with SMTP id 5b1f17b1804b1-4018af1038cso75538515e9.0; Wed, 13 Sep 2023 08:16:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1694618181; x=1695222981; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=+wHlb4TZdTg18dIQRSMHj1vLV5U+xhED8U8Tcp/nIAY=; b=pt7b3ELNkFkWz/Qm60VgX2GufJFrwa1Jyfk1gf+5HWsmKazqN7WIGvCiZ1raeuVAN8 Y2KWvv6WcJMlEfeDBJ5jrPWWO4dnY5TuHhOw7eeuvk4kRHuVJX5nORLGO3K5UpsQyHRk P0CPOO6YOFFb2xx9Nyd7GakQJcomDstplGOjpRsyCqhsiNM7zfpXYIaO3ZcD30ttp8SX 4jtUiau8/f1QLnMk4dh7qveEC7WKyVtcwVuLCwdVl89fucfoSGyGzYT/BmU9IIhlJyYU YFK56r1QMn/cfPQydccLLSPtDSyzCdDyy69s6Eg/aKuzjXwdtluitiAI2L5nspydZt28 l5jA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694618181; x=1695222981; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=+wHlb4TZdTg18dIQRSMHj1vLV5U+xhED8U8Tcp/nIAY=; b=cFThWIVC+TgyDMp6FtCYpuoPw/M3Zr9nOnLXEEM45fHDhjcKWoMKm1PGvekPHsqiDb Df1e+IvUCO5ropQmq1X3VJJgFStKwwVI1W+M/QvGa1UyOyE+13ivSruq5dHWhzeG7NzB UgpUsNnqFIfKKKwl60YuI8GeS0DtA5zwXmbloes6ngqlvJZNGs+/ijx5IUZi38+zukcb 2g6lBWc5dj3phN4MZQJNffLira375LqxyInRXt8MoiKSEADLBFWpO62FpDGyrRC1SrUi 3jmriF2EojbLe8LZAYfAE2CclZzYl0YvmhcISwJpN0cwdJCNIJHmhFbRoTNYLlW93kQw xacw== X-Gm-Message-State: AOJu0YyG/DCBq6f04o3ReB6xrzSW5g24TFqvf+rccYmw+zCdkMLAZxSc K1PLu1LQBV5lmR6kxSLkDgzNz37LYIyIsw== X-Received: by 2002:a7b:c416:0:b0:403:bb04:2908 with SMTP id k22-20020a7bc416000000b00403bb042908mr2217447wmi.23.1694618180871; Wed, 13 Sep 2023 08:16:20 -0700 (PDT) Received: from debby ([2a01:e0a:a6d:a8d0:7ff4:8f61:5574:9f95]) by smtp.gmail.com with ESMTPSA id w18-20020a5d6092000000b0031c52e81490sm15886631wrt.72.2023.09.13.08.16.20 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 13 Sep 2023 08:16:20 -0700 (PDT) From: Romain Perier <romain.perier@gmail.com> To: Alessandro Zummo <a.zummo@towertech.it>, Alexandre Belloni <alexandre.belloni@bootlin.com>, Daniel Palmer <daniel@0x0f.com>, Romain Perier <romain.perier@gmail.com>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Conor Dooley <conor+dt@kernel.org> Cc: linux-rtc@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [PATCH v2 0/3] Add RTC for MStar SSD20xD SoCs Date: Wed, 13 Sep 2023 17:16:03 +0200 Message-Id: <20230913151606.69494-1-romain.perier@gmail.com> X-Mailer: git-send-email 2.39.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (lipwig.vger.email [0.0.0.0]); Wed, 13 Sep 2023 08:17:08 -0700 (PDT) X-Spam-Status: No, score=-0.6 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lipwig.vger.email X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1776980595923980470 X-GMAIL-MSGID: 1776980595923980470 |
Series |
Add RTC for MStar SSD20xD SoCs
|
|
Message
Romain Perier
Sept. 13, 2023, 3:16 p.m. UTC
This patches series adds a new driver for the RTC found in the Mstar SSD202D SoCs. It adds a basic rtc driver, the corresponding devicetree bindings. The rtctest (from selftests) has been passed on this driver, with the following output: # rtctest TAP version 13 1..8 # Starting 8 tests from 1 test cases. # RUN rtc.date_read ... # rtctest.c:52:date_read:Current RTC date/time is 17/05/2023 15:58:12. # OK rtc.date_read ok 1 rtc.date_read # RUN rtc.date_read_loop ... # rtctest.c:95:date_read_loop:Continuously reading RTC time for 30s (with 11ms breaks after every read). # rtctest.c:122:date_read_loop:Performed 888 RTC time reads. # OK rtc.date_read_loop ok 2 rtc.date_read_loop # RUN rtc.uie_read ... # rtctest.c:137:uie_read:skip update IRQs not supported. # OK rtc.uie_read ok 3 rtc.uie_read # RUN rtc.uie_select ... # rtctest.c:166:uie_select:skip update IRQs not supported. # OK rtc.uie_select ok 4 rtc.uie_select # RUN rtc.alarm_alm_set ... # rtctest.c:214:alarm_alm_set:skip alarms are not supported. # OK rtc.alarm_alm_set ok 5 rtc.alarm_alm_set # RUN rtc.alarm_wkalm_set ... # rtctest.c:274:alarm_wkalm_set:skip alarms are not supported. # OK rtc.alarm_wkalm_set ok 6 rtc.alarm_wkalm_set # RUN rtc.alarm_alm_set_minute ... # rtctest.c:324:alarm_alm_set_minute:skip alarms are not supported. # OK rtc.alarm_alm_set_minute ok 7 rtc.alarm_alm_set_minute # RUN rtc.alarm_wkalm_set_minute ... # rtctest.c:384:alarm_wkalm_set_minute:skip alarms are not supported. # OK rtc.alarm_wkalm_set_minute ok 8 rtc.alarm_wkalm_set_minute # PASSED: 8 / 8 tests passed. # Totals: pass:8 fail:0 xfail:0 xpass:0 skip:0 error:0 Changes since v1: - Changed the compatible from mstar,ssd20xd-rtc to mstar,ssd20d-rtc. So the driver, its documentation and the commit messages have been reworked accordingly. - Re-worked the dt-binding, I have also simplified the commit message - Re-worked the commit message for the driver - Remove redundant logging message for the user in the driver, as requested by the subsystem maintainer. As these messages are helpful for debugging purpose, I have switched these to dev_dbg(). - Updated the list of maintainers (sorry for that). Romain Perier (3): rtc: Add support for the SSD202D RTC dt-bindings: rtc: Add Mstar SSD202D RTC ARM: dts: mstar: Enable rtc for SSD202D .../bindings/rtc/mstar,ssd202d-rtc.yaml | 35 +++ .../boot/dts/sigmastar/mstar-infinity2m.dtsi | 5 + drivers/rtc/Kconfig | 11 + drivers/rtc/Makefile | 1 + drivers/rtc/rtc-ssd202d.c | 249 ++++++++++++++++++ 5 files changed, 301 insertions(+) create mode 100644 Documentation/devicetree/bindings/rtc/mstar,ssd202d-rtc.yaml create mode 100644 drivers/rtc/rtc-ssd202d.c
Comments
On Wed, 13 Sep 2023 17:16:03 +0200, Romain Perier wrote: > This patches series adds a new driver for the RTC found in the Mstar > SSD202D SoCs. It adds a basic rtc driver, the corresponding devicetree > bindings. > > The rtctest (from selftests) has been passed on this driver, with the > following output: > > [...] Applied, thanks! [1/3] rtc: Add support for the SSD202D RTC commit: ebf6255868e6141c737cacb8d62b0b347f344877 [2/3] dt-bindings: rtc: Add Mstar SSD202D RTC commit: cfb67623ce281e045ec11e3eddb1b68b879b53a1 Best regards,
Le lun. 16 oct. 2023 à 16:55, Alexandre Belloni <alexandre.belloni@bootlin.com> a écrit : > > > On Wed, 13 Sep 2023 17:16:03 +0200, Romain Perier wrote: > > This patches series adds a new driver for the RTC found in the Mstar > > SSD202D SoCs. It adds a basic rtc driver, the corresponding devicetree > > bindings. > > > > The rtctest (from selftests) has been passed on this driver, with the > > following output: > > > > [...] > > Applied, thanks! Hi, Thanks! > > [1/3] rtc: Add support for the SSD202D RTC > commit: ebf6255868e6141c737cacb8d62b0b347f344877 > [2/3] dt-bindings: rtc: Add Mstar SSD202D RTC > commit: cfb67623ce281e045ec11e3eddb1b68b879b53a1 > > Best regards, Ah , you also merged dt-bindings, Conor (from dt maintainers) prefers trivial-rtc.yaml, it makes sense with the current driver. I planned to make the change for trivial-rtc in v3, so I can adapt the commit and rename mstar,ssd202d-rtc.yaml to trivial-rtc.yaml, what do you think ? Regards, Romain > > -- > Alexandre Belloni, co-owner and COO, Bootlin > Embedded Linux and Kernel engineering > https://bootlin.com
On 17/10/2023 08:09:10+0200, Romain Perier wrote: > Le lun. 16 oct. 2023 à 16:55, Alexandre Belloni > <alexandre.belloni@bootlin.com> a écrit : > > > > > > On Wed, 13 Sep 2023 17:16:03 +0200, Romain Perier wrote: > > > This patches series adds a new driver for the RTC found in the Mstar > > > SSD202D SoCs. It adds a basic rtc driver, the corresponding devicetree > > > bindings. > > > > > > The rtctest (from selftests) has been passed on this driver, with the > > > following output: > > > > > > [...] > > > > Applied, thanks! > > Hi, > > Thanks! > > > > > [1/3] rtc: Add support for the SSD202D RTC > > commit: ebf6255868e6141c737cacb8d62b0b347f344877 > > [2/3] dt-bindings: rtc: Add Mstar SSD202D RTC > > commit: cfb67623ce281e045ec11e3eddb1b68b879b53a1 > > > > Best regards, > > Ah , you also merged dt-bindings, Conor (from dt maintainers) prefers > trivial-rtc.yaml, it makes sense with the current driver. > I planned to make the change for trivial-rtc in v3, so I can adapt the > commit and rename mstar,ssd202d-rtc.yaml to trivial-rtc.yaml, what do > you think ? > This is fine as-is.