Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp5057359ybl; Mon, 26 Aug 2019 21:50:06 -0700 (PDT) X-Google-Smtp-Source: APXvYqwOveARc/VsEifIr+BHJS205bCjymvPVYHrx3miNbzj71mZJnDxU5NQnCUoEV9xpnraAroX X-Received: by 2002:a63:8ac3:: with SMTP id y186mr19540937pgd.13.1566881405953; Mon, 26 Aug 2019 21:50:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566881405; cv=none; d=google.com; s=arc-20160816; b=kUbDsE8HlakdCkTpjxk2B5WlQwBAEAIfgBB9XhFOLsZrNAnhrGi5yCjErsxAX3LD3K LPYRN8p+9yefEDbYSLJoH2DahrePQ7HU/KBl/7h727d40FcBSAlrCvUdCF2nXGiYy/k8 p/fMI0zMZY9e4ZHQpJt/5WbgQEnYpLDf8NxpFQWuiIHDGdCUPhE7N/92hnrQsJcze11t AtX0LtL6mui1iqUCWrb70RyCMpJIUQ1XL501/FVpSA2pxq+5IGb45F7WinHxMy+kDVcp xCdylxJR1TXTukMvzRIBxC0/qer8GdIRy884J8ehZ/lDziKbJmPLAo5VQiF+az1bQ0gU YpFw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=Fb2R69QiGstbZB6wTRVqACHRqHXe6e908DaIvHW8AUg=; b=RNBYol1I1CiA1NYcZGvT4gy1Gbgin2MO6Mwr+hsarajkQ8RMoLUnBTxfUOAo1HRg6I sCmQ3h1Aj+hL1nWan+zFgsDtCGeEWispLImdsjcuAb2ZzVfztFi/yT6MGq/Nh26VuH2D 4DjjZlFE24RN+RxU+1qQAMQ42cA7mrEJpYp4pXznDC/9CJmOhn+Z521ZUc3n6tlmxG4R fLWLbPyEiSfi/b8+wEgcQvbzv/K+H5lt75IUKI6FAZ+RtfvIfTfFxCRuaPMaXKaymHe1 rl43WUrTCpb2wREHhpaZ8tWpNN0icYwS19lND8K2wUsNN0X9SgZkaI4LpnxLnUb8ZoEb lhMw== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=nxp.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g2si13231626pfq.160.2019.08.26.21.49.49; Mon, 26 Aug 2019 21:50:05 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=nxp.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729249AbfH0Erm (ORCPT + 99 others); Tue, 27 Aug 2019 00:47:42 -0400 Received: from inva020.nxp.com ([92.121.34.13]:48216 "EHLO inva020.nxp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725795AbfH0Erm (ORCPT ); Tue, 27 Aug 2019 00:47:42 -0400 Received: from inva020.nxp.com (localhost [127.0.0.1]) by inva020.eu-rdc02.nxp.com (Postfix) with ESMTP id 17B3A1A0586; Tue, 27 Aug 2019 06:47:40 +0200 (CEST) Received: from invc005.ap-rdc01.nxp.com (invc005.ap-rdc01.nxp.com [165.114.16.14]) by inva020.eu-rdc02.nxp.com (Postfix) with ESMTP id DCEDB1A0203; Tue, 27 Aug 2019 06:47:35 +0200 (CEST) Received: from titan.ap.freescale.net (TITAN.ap.freescale.net [10.192.208.233]) by invc005.ap-rdc01.nxp.com (Postfix) with ESMTP id 74616402BF; Tue, 27 Aug 2019 12:47:30 +0800 (SGT) From: Biwen Li To: a.zummo@towertech.it, alexandre.belloni@bootlin.com, leoyang.li@nxp.com, broonie@kernel.org, nandor.han@vaisala.com Cc: linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org, Biwen Li Subject: [v4] rtc: pcf85363/pcf85263: fix error that failed to run hwclock -w Date: Tue, 27 Aug 2019 12:37:35 +0800 Message-Id: <20190827043735.31231-1-biwen.li@nxp.com> X-Mailer: git-send-email 2.9.5 X-Virus-Scanned: ClamAV using ClamSMTP Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Issue: - # hwclock -w hwclock: RTC_SET_TIME: Invalid argument Why: - Relative commit: 8b9f9d4dc511309918c4f6793bae7387c0c638af, this patch will always check for unwritable registers, it will compare reg with max_register in regmap_writeable. - In drivers/rtc/rtc-pcf85363.c, CTRL_STOP_EN is 0x2e, but DT_100THS is 0, max_regiter is 0x2f, then reg will be equal to 0x30, '0x30 < 0x2f' is false,so regmap_writeable will return false. - The pcf85363/pcf85263 has the capability of address wrapping which means if you access a continuous address range across a certain boundary(max_register of struct regmap_config) the hardware actually wraps the access to a lower address. But the address violation check of regmap rejects such access. How: - Split of writing regs to two parts, first part writes control registers about stop_enable and resets, second part writes RTC time and date registers. Signed-off-by: Biwen Li --- Change in v4: - use old scheme - replace link to lkml.org with commit - add proper explanation Change in v3: - replace old scheme with new scheme: increase max_register. Change in v2: - add Why and How into commit message. drivers/rtc/rtc-pcf85363.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/drivers/rtc/rtc-pcf85363.c b/drivers/rtc/rtc-pcf85363.c index a075e77617dc..3450d615974d 100644 --- a/drivers/rtc/rtc-pcf85363.c +++ b/drivers/rtc/rtc-pcf85363.c @@ -166,7 +166,12 @@ static int pcf85363_rtc_set_time(struct device *dev, struct rtc_time *tm) buf[DT_YEARS] = bin2bcd(tm->tm_year % 100); ret = regmap_bulk_write(pcf85363->regmap, CTRL_STOP_EN, - tmp, sizeof(tmp)); + tmp, 2); + if (ret) + return ret; + + ret = regmap_bulk_write(pcf85363->regmap, DT_100THS, + buf, sizeof(tmp) - 2); if (ret) return ret; -- 2.17.1