From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7C9A4C4338F for ; Tue, 10 Aug 2021 15:34:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 60E4161051 for ; Tue, 10 Aug 2021 15:34:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243345AbhHJPfQ (ORCPT ); Tue, 10 Aug 2021 11:35:16 -0400 Received: from mta-02.yadro.com ([89.207.88.252]:34968 "EHLO mta-01.yadro.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S243315AbhHJPfI (ORCPT ); Tue, 10 Aug 2021 11:35:08 -0400 Received: from localhost (unknown [127.0.0.1]) by mta-01.yadro.com (Postfix) with ESMTP id 1111E48A6C; Tue, 10 Aug 2021 15:34:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yadro.com; h= content-type:content-type:content-transfer-encoding:mime-version :x-mailer:message-id:date:date:subject:subject:from:from :received:received:received; s=mta-01; t=1628609683; x= 1630424084; bh=Cpz7STHdgDcx3h44+KtoM9BhcJjIzj3viQKNuLSI1cs=; b=X Kb/AQsBBfPD0Pkqdh5iCA3r0zmuSIPy595R9OYg6sBm72D7PkwtMLjefJhqvJWVT rBCcJg3bvxCYc5M9+NrjbWn/JP2TxGaF8w9EK+uzPFKywxo3U9kyYe0e4AoF5/Vl gyCko+Z3ZSAsHvi4MspDWDnO3m8J77nLcggwMYugA8= X-Virus-Scanned: amavisd-new at yadro.com Received: from mta-01.yadro.com ([127.0.0.1]) by localhost (mta-01.yadro.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QSU6vnUXcWCo; Tue, 10 Aug 2021 18:34:43 +0300 (MSK) Received: from T-EXCH-04.corp.yadro.com (t-exch-04.corp.yadro.com [172.17.100.104]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mta-01.yadro.com (Postfix) with ESMTPS id 3771A46796; Tue, 10 Aug 2021 18:34:40 +0300 (MSK) Received: from fedora.bbmc.yadro.com (10.199.0.188) by T-EXCH-04.corp.yadro.com (172.17.100.104) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.32; Tue, 10 Aug 2021 18:34:39 +0300 From: Ivan Mikhaylov To: Alessandro Zummo , Alexandre Belloni CC: Ivan Mikhaylov , , Subject: [PATCH 0/2] rtc: pch-rtc: add Intel Series PCH built-in read-only RTC Date: Tue, 10 Aug 2021 18:44:34 +0300 Message-ID: <20210810154436.125678-1-i.mikhaylov@yadro.com> X-Mailer: git-send-email 2.31.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Originating-IP: [10.199.0.188] X-ClientProxiedBy: T-EXCH-01.corp.yadro.com (172.17.10.101) To T-EXCH-04.corp.yadro.com (172.17.100.104) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Add RTC driver with dt binding tree document. Also this driver adds one sysfs attribute for host power control which I think is odd for RTC driver. Need I cut it off and use I2C_SLAVE_FORCE? I2C_SLAVE_FORCE is not good way too from my point of view. Is there any better approach? Ivan Mikhaylov (2): rtc: pch-rtc: add RTC driver for Intel Series PCH dt-bindings: rtc: provide RTC PCH device tree binding doc .../bindings/rtc/intel,pch-rtc.yaml | 39 +++++ drivers/rtc/Kconfig | 10 ++ drivers/rtc/Makefile | 1 + drivers/rtc/rtc-pch.c | 148 ++++++++++++++++++ 4 files changed, 198 insertions(+) create mode 100644 Documentation/devicetree/bindings/rtc/intel,pch-rtc.yaml create mode 100644 drivers/rtc/rtc-pch.c -- 2.31.1