Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp4418971ybl; Tue, 20 Aug 2019 11:34:50 -0700 (PDT) X-Google-Smtp-Source: APXvYqwWSSKAMIRY+zuBEgq+WKpqHWNy8BiWMCPapaoz0cdrLnZ7K0xcwcrf/CCDao9/WkGN6QhF X-Received: by 2002:a65:4844:: with SMTP id i4mr26184814pgs.113.1566326090586; Tue, 20 Aug 2019 11:34:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566326090; cv=none; d=google.com; s=arc-20160816; b=uHUFNubJz67wX8BUfA1aAOq/cq5sHEhgNHFIUZYAew1KeTzmadr3eVK3mgnh/sWcQU 532W7exTPOSnOmqkarOAHfxDVot6SePma9OkSoXyXhUS60DbTXzEArMWlUD5hDE9hoDU ycCJxZhY1+TeKIVPAKxSrho23Gwda4jhcusCNu5mIqi3F5dsfGOXcaoRjjT4alKbMAya OSb6bGMNcRQ03lsFYZTnxMqi/85YcTnzwf8cdQ35O0xYs/OmhYZvCWV2Y9agsUFXBFfr qhkk/hB+W258ZKEE3R2Xw4+SZLAXRKbWqgIznvKXeLFac2QQRfRzHajDPq/vhQiS6bWN hkwg== 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=nqYFWFK/ADw0LWhiUiVtqIu4MsMiNN1qpQeUvKdTaHc=; b=K1S/uk9fAA225rhppMr8gRv2sexs0XOiDd90zX8OureVgh40NnITrdOXyAJVG2b0Iq 74GsBTSRFkD3J2bREEV91MbhhbRHZ2F1oqYCSlT7DJEb7/pGcCVVcJD5QeCqDD4RMUVr kjnvhQSbGkbyCCsrJ/L3velzf4tDWDOmaGBSAtYzjDh+1zSRvAKrNC50uvcoaGmdzKY8 FBwZDSX5OnWJ898+Bx/cidfwpRA/VC0+6cFW4cXEVghsaA65WVMChJmKcv/QJ8oBTlKE vTQjngGSYLkEdgq9nJ9QFOFISzuJXPa1DoW2dUvCqmVo7rJ79YWr1oqk4WezkPnyDyPp rNQA== 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 s18si9008460pgq.177.2019.08.20.11.34.34; Tue, 20 Aug 2019 11:34:50 -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 S1730374AbfHTSd2 (ORCPT + 99 others); Tue, 20 Aug 2019 14:33:28 -0400 Received: from mail-oi1-f176.google.com ([209.85.167.176]:46539 "EHLO mail-oi1-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730006AbfHTSd2 (ORCPT ); Tue, 20 Aug 2019 14:33:28 -0400 Received: by mail-oi1-f176.google.com with SMTP id t24so4864492oij.13; Tue, 20 Aug 2019 11:33:27 -0700 (PDT) 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=nqYFWFK/ADw0LWhiUiVtqIu4MsMiNN1qpQeUvKdTaHc=; b=H/2HKzsl85NFkv/EJOLn7i5cOVzNjyBl1CX3elN8kJkS1ociXgufl3S6tRiP5tOC6V Nc9NI05xq9fHOsqo+KYK1zLw/+OHPelRI0wnKQgTaUnv6mKcD+Ic4+KaVfrVuAwFXdRs 6Ny8mYV3BThdOHrQgnhbvFRPR/2vVbioHGz9kuBKDynLlfrYn4mh8kCDDqMPWVI2xzE3 1i02e7bfaoLHOsxpDNtFG/u8N/yP297jUuqYBvPDWySayJ9davQTE11GRge0zZxoN7mb gIi0pp4U0Q4Dwog3/bzC2Rby/Lpn9q4LPoGqfa0xrck63MumfeaV//8QqSH2TigoCXJ+ o5iw== X-Gm-Message-State: APjAAAXfcDSuaQ4bOusptzuE1tjmfyvvR/MHm7PsvJZMP1+TMWLCH4sE 6vut8lgT0N2zxanumCySjanm9K42 X-Received: by 2002:a54:441a:: with SMTP id k26mr1020271oiw.78.1566326006743; Tue, 20 Aug 2019 11:33:26 -0700 (PDT) Received: from mail-ot1-f51.google.com (mail-ot1-f51.google.com. [209.85.210.51]) by smtp.gmail.com with ESMTPSA id h25sm4180532oih.22.2019.08.20.11.33.25 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 20 Aug 2019 11:33:26 -0700 (PDT) Received: by mail-ot1-f51.google.com with SMTP id r20so5966940ota.5; Tue, 20 Aug 2019 11:33:25 -0700 (PDT) X-Received: by 2002:a9d:6a94:: with SMTP id l20mr812157otq.221.1566326005853; Tue, 20 Aug 2019 11:33:25 -0700 (PDT) MIME-Version: 1.0 References: <20190816024636.34738-1-biwen.li@nxp.com> <20190816080417.GB3545@piout.net> <20190816162825.GE3545@piout.net> <20190820182224.GI4738@sirena.co.uk> In-Reply-To: <20190820182224.GI4738@sirena.co.uk> From: Li Yang Date: Tue, 20 Aug 2019 13:33:14 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [v2] rtc: pcf85363/pcf85263: fix error that failed to run hwclock -w To: Mark Brown Cc: Alexandre Belloni , nandor.han@vaisala.com, Biwen Li , a.zummo@towertech.it, linux-rtc@vger.kernel.org, lkml 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 Tue, Aug 20, 2019 at 1:24 PM Mark Brown wrote: > > On Fri, Aug 16, 2019 at 02:40:47PM -0500, Li Yang wrote: > > On Fri, Aug 16, 2019 at 11:30 AM Alexandre Belloni > > > > Most of the i2c RTCs do address wrapping which is sometimes the only way > > > to properly set the time. > > > Adding Mark and Nandor to the loop. > > Is there a specific question or something here? Some of the RTC hardware has the capability of address wrapping which means if you access a continuous address range across a certain boundary(could be the boundary of a regmap region) the hardware actually wrap the access to a lower address. But the address violation check of regmap rejects such access. According to Alexcandre, the address wrapping is essential to the functionality of some RTC devices and can improve performance for some others. We are wondering if it is reasonable to have regmap support this address wrapping. Regards, Leo