Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp2890687ybc; Mon, 18 Nov 2019 06:21:55 -0800 (PST) X-Google-Smtp-Source: APXvYqw3bK0UgYjhl3xC+J8FkDyJvrvXnl8XJVYKsdVAXwZg1kw+cLi4p7OUKQvNzv3BThsPacyQ X-Received: by 2002:a1c:8086:: with SMTP id b128mr29125172wmd.104.1574086915650; Mon, 18 Nov 2019 06:21:55 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574086915; cv=none; d=google.com; s=arc-20160816; b=Tyn/6O7+KMkLIatSCJkLWN00up9Pltlo4vLmXxh6WYnS8dU8U2oGXAmdi6srTmJRYx HM0TewDe+r5lLHcb8fmNka/co+6jSMVWrKg9zBt68LQnPO2pz45QCapziNGtcxQ1gxNH pbTozpA2aEkbG/q96jWK0BKbG2c/X2XRZVDhp+QIZjaiDkafyjBsTKtruykzHAWyWTFU GpGG5z59kngMZ6xGDu6D+yoTRyvaOuUkzHmlHq/w1YyrCaiVo+jsUdh4wFkubWP9aCc6 JPvAr8V6h+47DTk987i/edi8KU1eOKZLjBo1wLv/UI/B4YHefnRFfkJzMshdcr5OhNk0 cTig== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version; bh=LlbnYe+LYNl3bzTxxtCJWfnFvfltP+wo9WgZRAXweTU=; b=ZBsK/sp3Yjir6t72II5+ZiFiovMK0WL6oiBaQOdb2d5UMlQaze3PhOtTtKlJzWyN7X GmhwaktpecgSnSAd3MXwhfNrZlg+gf5jR9e0O5q0zMseusF4GmFdYtApaG15qV6oYPLb orD6VtGAjftmPUwwz/dVcu8x8ZDcCWFBfd+0Af8SpPvUAH23QkCjfPJJtB+yMotmTUCg /WIewTpK9IQWLt6HkH3bt+0s37qmfMOrEZnktInCUA+2SqItFzl7XQRLIYp4Ji+NGxtq iCQgndnfx0Sfl/xlGvjVCOiHmP2GBL+twdDaltnTxcaGmq3J4/m1GCBr6jvt8jd/1LEx lyOQ== 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 m33si12990266edc.126.2019.11.18.06.21.31; Mon, 18 Nov 2019 06:21:55 -0800 (PST) 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 S1727216AbfKROT7 (ORCPT + 99 others); Mon, 18 Nov 2019 09:19:59 -0500 Received: from mail-oi1-f193.google.com ([209.85.167.193]:40457 "EHLO mail-oi1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726704AbfKROT7 (ORCPT ); Mon, 18 Nov 2019 09:19:59 -0500 Received: by mail-oi1-f193.google.com with SMTP id d22so8479467oic.7; Mon, 18 Nov 2019 06:19:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LlbnYe+LYNl3bzTxxtCJWfnFvfltP+wo9WgZRAXweTU=; b=uXx/gcPpWxfGdjOTpd2TZvBPmVJKN3iKQX72vyb4Vpkss6UnYHPBfNPSQpCae2kF/1 d6jPwmlI0hdKMBxqDsoAO6bzUi/vwZD7W1+gcEPOodBb9keL1cRICkTRWkGDNid2BBhZ ogVYrEcRHCqQ8OG5tpbhmwL2Mr/4mgTGtm2ZAR+ks354hFxTQtK7zmku7pXvw0frVt+c NWB9bs0+Tix04h8WuQ0P8FUqN+/WxThfHHUxw3NCOFNoJfSg23/xqjdMCojQu3XxSKf8 S1G5hilFeB5FgLSpPnUlSrKheLf1JB5f97ID0bjcDxJvsiNEGjhKzbf3dUrFppjOmaEs u+AQ== X-Gm-Message-State: APjAAAVVaEMgs09kVaYSwMJeNOX7SOGSb9oa5/lgU6ifg4OFRMbny37g oS9oMpo06LyBzaKy0rv8qjkDkXfPlsztoNSUFEI= X-Received: by 2002:aca:fc92:: with SMTP id a140mr19658524oii.153.1574086797989; Mon, 18 Nov 2019 06:19:57 -0800 (PST) MIME-Version: 1.0 References: <20191116114620.9193-1-jongk@linux-m68k.org> In-Reply-To: <20191116114620.9193-1-jongk@linux-m68k.org> From: Geert Uytterhoeven Date: Mon, 18 Nov 2019 15:19:47 +0100 Message-ID: Subject: Re: [PATCH] rtc: msm6242: Remove unneeded msm6242_set()/msm6242_clear() functions To: Kars de Jong Cc: Alessandro Zummo , Alexandre Belloni , linux-rtc@vger.kernel.org, Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Nov 16, 2019 at 12:46 PM Kars de Jong wrote: > The msm6242_set()/msm6242_clear() functions are used when writing to Control > Register D to set or clear the HOLD bit when reading the current time from > the RTC. > > Doing this with a read-modify-write cycle will potentially clear an > interrupt condition which occurs between the read and the write. > > The datasheet states the following about this: > > When writing the HOLD or 30 second adjust bits of register D, it is > necessary to write the IRQ FLAG bit to a "1". > > Since the only other bits in the register are the 30 second adjust bit > (which is not used) and the BUSY bit (which is read-only), the > read-modify-write cycle can be replaced by a simple write with the IRQ FLAG > bit set to 1 and the other bits (except HOLD) set to 0. > > Cc: Geert Uytterhoeven > Tested-by: Kars de Jong > Signed-off-by: Kars de Jong Reviewed-by: Geert Uytterhoeven Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds